Skip to content

Conversation

@thomas-nguy
Copy link
Collaborator

@thomas-nguy thomas-nguy commented Sep 4, 2025

👮🏻👮🏻👮🏻 !!!! REFERENCE THE PROBLEM YOUR ARE SOLVING IN THE PR TITLE AND DESCRIBE YOUR SOLUTION HERE !!!! DO NOT FORGET !!!! 👮🏻👮🏻👮🏻

PR Checklist:

  • Have you read the CONTRIBUTING.md?
  • Does your PR follow the C4 patch requirements?
  • Have you rebased your work on top of the latest master?
  • Have you checked your code compiles? (make)
  • Have you included tests for any non-trivial functionality?
  • Have you checked your code passes the unit tests? (make test)
  • Have you checked your code formatting is correct? (go fmt)
  • Have you checked your basic code style is fine? (golangci-lint run)
  • If you added any dependencies, have you checked they do not contain any known vulnerabilities? (go list -json -m all | nancy sleuth)
  • If your changes affect the client infrastructure, have you run the integration test?
  • If your changes affect public APIs, does your PR follow the C4 evolution of public contracts?
  • If your code changes public APIs, have you incremented the crate version numbers and documented your changes in the CHANGELOG.md?
  • If you are contributing for the first time, please read the agreement in CONTRIBUTING.md now and add a comment to this pull request stating that your PR is in accordance with the Developer's Certificate of Origin.

Thank you for your code, it's appreciated! :)

Summary by CodeRabbit

  • Documentation
    • Added an UNRELEASED v1.5.0 changelog entry (Sep 4, 2025) noting a State Machine Breaking item related to upgrading ibc-go to v10.1.1 (PR Problem: ibc-go v10 is not used #1731).
    • This is a documentation-only update; no functional or public API changes were made.
    • All other changelog entries remain unchanged.

@thomas-nguy thomas-nguy requested a review from a team as a code owner September 4, 2025 02:12
@thomas-nguy thomas-nguy requested review from XinyuCRO and randy-cro and removed request for a team September 4, 2025 02:12
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Sep 4, 2025

Walkthrough

Added an UNRELEASED v1.5.0 entry to CHANGELOG.md dated Sep 4, 2025, noting a State Machine Breaking change referencing an ibc-go upgrade to v10.1.1 (PR #1731). No code or API changes.

Changes

Cohort / File(s) Summary
Documentation — Changelog
CHANGELOG.md
Added UNRELEASED v1.5.0 entry with a State Machine Breaking note referencing ibc-go v10.1.1 (PR #1731); documentation-only change, no code or public API changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested reviewers

  • randy-cro

Pre-merge checks (3 passed)

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check ✅ Passed The title "release: v1.5.0" is short, specific, and directly reflects the primary intent of the changeset (a v1.5.0 release/changelog update), so it clearly summarizes the main change for reviewers scanning history.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.

Poem

I hop through lines with ink-stained paw,
A changelog blossom I gently saw.
No code to chew, no tests to mend,
Just a dotted carrot at doc's end. 🥕

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

  • Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
  • Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

✨ Finishing touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions
Copy link

github-actions bot commented Sep 4, 2025

Hey there and thank you for opening this pull request! 👋🏼

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.

Details:

Unknown release type "release" found in pull request title "release: v1.5.0". 

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
CHANGELOG.md (1)

24-24: Fix incorrect PR URL

Label is “#1851” but URL ends with “/pull/1850”. Likely a copy-paste error.

Apply this correction:

-* [#1851](https://github.com/crypto-org-chain/cronos/pull/1850) Add default value of CancunTime and PragueTime in chain config.
+* [#1851](https://github.com/crypto-org-chain/cronos/pull/1851) Add default value of CancunTime and PragueTime in chain config.
🧹 Nitpick comments (3)
CHANGELOG.md (3)

5-5: Silence markdownlint MD036 for date line

markdownlint flags the italicized date as “emphasis used instead of a heading.” This formatting is consistent with the rest of the changelog. Either disable the rule for this line or adjust tooling.

Apply this local, non-invasive fix:

+# markdownlint-disable-next-line MD036
 *Sep 4, 2025*

14-14: Grammar fix in state machine breaking note

“Tense/wording reads off.”

-* [#1846](https://github.com/crypto-org-chain/cronos/pull/1846) Enforce app creator returning application implement AppWithPendingTxStream during compilation phase 
+* [#1846](https://github.com/crypto-org-chain/cronos/pull/1846) Enforce the app creator to return an application that implements AppWithPendingTxStream during the compilation phase.

18-22: Minor copy edits for consistency and capitalization

Align with common casing used elsewhere in the changelog.

-* [#1841](https://github.com/crypto-org-chain/cronos/pull/1841) Ci: use `golangci-lint run --fix`.
+* [#1841](https://github.com/crypto-org-chain/cronos/pull/1841) CI: use `golangci-lint run --fix`.
-* [#1824](https://github.com/crypto-org-chain/cronos/pull/1824) Rework on github actions.
+* [#1824](https://github.com/crypto-org-chain/cronos/pull/1824) Rework GitHub Actions.
-* [#1826](https://github.com/crypto-org-chain/cronos/pull/1826) Update linter and tidy up code.
+* [#1826](https://github.com/crypto-org-chain/cronos/pull/1826) Update linters and tidy up code.
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 750d141 and 1dba60e.

📒 Files selected for processing (1)
  • CHANGELOG.md (1 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
CHANGELOG.md

5-5: Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: semgrep-cloud-platform/scan
🔇 Additional comments (1)
CHANGELOG.md (1)

7-8: v1.5.0 section header LGTM

Structure matches existing conventions (date line preceding version header).

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
CHANGELOG.md (1)

25-25: Another PR number/URL mismatch.

Label #1851 links to /pull/1850. Align them.

Pick the correct one:

- * [#1851](https://github.com/crypto-org-chain/cronos/pull/1850) Add default value of CancunTime and PragueTime in chain config.
+ * [#1850](https://github.com/crypto-org-chain/cronos/pull/1850) Add default value of CancunTime and PragueTime in chain config.

or

- * [#1851](https://github.com/crypto-org-chain/cronos/pull/1850) Add default value of CancunTime and PragueTime in chain config.
+ * [#1851](https://github.com/crypto-org-chain/cronos/pull/1851) Add default value of CancunTime and PragueTime in chain config.
♻️ Duplicate comments (1)
CHANGELOG.md (1)

11-11: Fix PR number/URL mismatch (label vs link).

Label shows #1731 but URL points to /pull/1804. Make them consistent.

Apply one of the following, whichever is correct:

- * [#1731](https://github.com/crypto-org-chain/cronos/pull/1804) Upgrade to ibc-go v10.1.1
+ * [#1804](https://github.com/crypto-org-chain/cronos/pull/1804) Upgrade to ibc-go v10.1.1

or

- * [#1731](https://github.com/crypto-org-chain/cronos/pull/1804) Upgrade to ibc-go v10.1.1
+ * [#1731](https://github.com/crypto-org-chain/cronos/pull/1731) Upgrade to ibc-go v10.1.1
🧹 Nitpick comments (5)
CHANGELOG.md (5)

5-8: Clarify release state: UNRELEASED header with a concrete date is confusing.

Either keep UNRELEASED without a date until tagging, or finalize the section (drop UNRELEASED and keep the date).

Options:

  • Pre-release style:
-## UNRELEASED
-
-*Sep 4, 2025*
-
-## v1.5.0
+## UNRELEASED
+
+<!-- Placeholder for future changes -->
+
+## v1.5.0
+*Sep 4, 2025*
  • Post-release style (once tagged):
-## UNRELEASED
-
-*Sep 4, 2025*
-
-## v1.5.0
+## v1.5.0
+*Sep 4, 2025*
+
+## UNRELEASED
+<!-- Placeholder for future changes -->

13-13: Trim trailing whitespace.

-* [#1846](https://github.com/crypto-org-chain/cronos/pull/1846) Enforce app creator returning application implement AppWithPendingTxStream during compilation phase 
+* [#1846](https://github.com/crypto-org-chain/cronos/pull/1846) Enforce app creator returning application implement AppWithPendingTxStream during compilation phase

28-28: Normalize heading capitalization (“Bug fixes” → “Bug Fixes”).

Matches prior sections (e.g., Lines 44, 53, 66). Consistency helps scanning.

-### Bug fixes
+### Bug Fixes

18-18: Capitalize “CI” acronym.

-* [#1841](https://github.com/crypto-org-chain/cronos/pull/1841) Ci: use `golangci-lint run --fix`.
+* [#1841](https://github.com/crypto-org-chain/cronos/pull/1841) CI: use `golangci-lint run --fix`.

5-5: markdownlint MD036 (emphasis used as heading).

House style uses italicized dates throughout. Either disable MD036 for date lines or convert dates to subheadings project-wide.

Minimal suppression (preferred to preserve style):

- *Sep 4, 2025*
+<!-- markdownlint-disable-next-line MD036 -->
+*Sep 4, 2025*
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1dba60e and 311f11f.

📒 Files selected for processing (1)
  • CHANGELOG.md (1 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
CHANGELOG.md

5-5: Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (7)
  • GitHub Check: integration_tests (ica)
  • GitHub Check: integration_tests (slow)
  • GitHub Check: integration_tests (gov)
  • GitHub Check: build (macos-latest)
  • GitHub Check: integration_tests (unmarked)
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: semgrep-cloud-platform/scan

@thomas-nguy thomas-nguy added this pull request to the merge queue Sep 12, 2025
Merged via the queue into crypto-org-chain:main with commit b952195 Sep 12, 2025
35 of 37 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants