Skip to content

chore: v10 upgrade#22

Merged
johnletey merged 2 commits intomainfrom
dan/v10-upgrade
Sep 10, 2025
Merged

chore: v10 upgrade#22
johnletey merged 2 commits intomainfrom
dan/v10-upgrade

Conversation

@boojamya
Copy link
Copy Markdown
Contributor

@boojamya boojamya commented Sep 9, 2025

Summary by CodeRabbit

  • Documentation
    • Reformatted the mainnet chain upgrades table for improved readability and alignment.
    • Increased the Tag column width and updated separators to match the new layout.
    • Standardized spacing for clearer scanning and visual consistency across entries.
    • Appended a new release row: v10.1.1 Ember (Start Height 28613000).
    • No other content, links, or values were changed; purely presentational.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Sep 9, 2025

Walkthrough

Reflowed the Markdown table in docs/chain-upgrades/mainnet.mdx: adjusted the Tag column width, updated the separator line and row spacing/alignment, and appended a new row for v10.1.1 Ember (Start Height 28613000). No other data or links were changed.

Changes

Cohort / File(s) Summary
Docs table reformatting
docs/chain-upgrades/mainnet.mdx
Reformatted the Markdown table: widened the Tag header, updated separator dashes, realigned row spacing/indentation, and added a new row v10.1.1 Ember (Start Height 28613000). No content, links, or existing values were modified.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I hopped through the rows with a twitch and a cheer,
Straightened the dashes, made columns more clear.
Added one Ember, tucked neatly in line—
A tidy small change, like a fresh carrot vine. 🥕

Pre-merge checks (1 passed, 2 inconclusive)

❌ Failed checks (2 inconclusive)
Check name Status Explanation Resolution
Title Check ❓ Inconclusive The current title “chore: v10 upgrade” refers only broadly to a version bump and does not clearly summarize that this PR reformats the chain-upgrades documentation table and appends a new v10.1.1 Ember entry, making it too vague to confirm it covers the main change. Please update the PR title to specifically reflect the documentation change, for example “docs(chain-upgrades): reformat table and add v10.1.1 Ember entry.”
Description Check ❓ Inconclusive There is no visible PR description provided, so it is unclear whether the description relates to the table reformat and the new version row, making it impossible to verify that it addresses the actual changes. Please add or update the PR description to briefly summarize the formatting adjustments to docs/chain-upgrades/mainnet.mdx and the addition of the v10.1.1 Ember row.
✅ Passed checks (1 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch dan/v10-upgrade

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.

Copy link
Copy Markdown
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

🧹 Nitpick comments (2)
docs/chain-upgrades/mainnet.mdx (2)

19-19: Make table delimiters consistent (add trailing pipes).

Markdown is lenient, but inconsistent trailing pipes can cause layout drift in some renderers.

-| Tag                                                                     | Name       | Start Height                                            | Notes 
+| Tag                                                                     | Name       | Start Height                                            | Notes |
...
-| [`v1.0.0`](https://github.com/noble-assets/noble/releases/tag/v1.0.0)   |            | [0](https://www.mintscan.io/noble/blocks/1)             | Genesis Version
+| [`v1.0.0`](https://github.com/noble-assets/noble/releases/tag/v1.0.0)   |            | [0](https://www.mintscan.io/noble/blocks/1)             | Genesis Version |
...
-| [`v10.1.0`](https://github.com/noble-assets/noble/releases/tag/v10.1.0) | Ember      | [28613000](https://www.mintscan.io/noble/block/28613000)| Upgrading to `v10.0.0` is OK but you must be upgraded to `v10.1.0` before the block that occurred at 11:59 UTC on August 1st 2025.
+| [`v10.1.0`](https://github.com/noble-assets/noble/releases/tag/v10.1.0) | Ember      | [28613000](https://www.mintscan.io/noble/blocks/28613000)| Upgrading to `v10.0.0` is OK but you must be upgraded to `v10.1.0` before the block that occurred at 11:59 UTC on August 1st 2025. |

Also applies to: 21-21, 37-37


24-24: Normalize “Name” and notes style for consistency.

  • Row v3.1.0 uses a version string in the Name column while others use codenames or blank. Pick one convention.
  • Consider clarifying the v8.0.1 “panic expected” note with a brief reason (link to release notes).
  • For v10.1.0, include the exact block height that corresponds to “11:59 UTC on August 1, 2025” to avoid ambiguity.

Also applies to: 33-34, 37-37

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6a65477 and 972cb0f.

📒 Files selected for processing (1)
  • docs/chain-upgrades/mainnet.mdx (1 hunks)
🔇 Additional comments (1)
docs/chain-upgrades/mainnet.mdx (1)

21-21: Fix genesis height/link mismatch
docs/chain-upgrades/mainnet.mdx:21
The table shows height 0 but links to /blocks/1. Confirm whether Mintscan’s canonical genesis block is at /blocks/0 or /blocks/1 and update either the label or the URL accordingly.

Comment on lines +24 to +29
| [`v3.1.0`](https://github.com/noble-assets/noble/releases/tag/v3.1.0) | v3.1.0 | [2672000](https://www.mintscan.io/noble/block/2672000) |
| [`v4.0.2`](https://github.com/noble-assets/noble/releases/tag/v4.0.2) | Argon | [3408600](https://www.mintscan.io/noble/block/3377500) | must set `--halt-height 5262000` to upgrade to next version
| [`v4.0.3`](https://github.com/noble-assets/noble/releases/tag/v4.0.3) | | [5262000](https://www.mintscan.io/noble/block/5262000) |
| [`v4.1.1`](https://github.com/noble-assets/noble/releases/tag/v4.1.1) | Fusion | [5797500](https://www.mintscan.io/noble/block/5797500) | must set `--halt-height 6022000` to upgrade to next version
| [`v4.1.2`](https://github.com/noble-assets/noble/releases/tag/v4.1.2) | | [6022000](https://www.mintscan.io/noble/block/5797500) | must set `--halt-height 6139500` to upgrade to next version
| [`v4.1.3`](https://github.com/noble-assets/noble/releases/tag/v4.1.3) | | [6139500](https://www.mintscan.io/noble/block/5797500) |
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Fix Mintscan block links (heights mismatch and singular path).

Several Start Height URLs don’t match the displayed heights and use /block/ instead of /blocks/. This is a user-facing correctness issue.

Apply this diff:

-| [`v3.1.0`](https://github.com/noble-assets/noble/releases/tag/v3.1.0)   | v3.1.0     | [2672000](https://www.mintscan.io/noble/block/2672000)  |
+| [`v3.1.0`](https://github.com/noble-assets/noble/releases/tag/v3.1.0)   | v3.1.0     | [2672000](https://www.mintscan.io/noble/blocks/2672000) |

-| [`v4.0.2`](https://github.com/noble-assets/noble/releases/tag/v4.0.2)   | Argon      | [3408600](https://www.mintscan.io/noble/block/3377500)  | must set `--halt-height 5262000` to upgrade to next version
+| [`v4.0.2`](https://github.com/noble-assets/noble/releases/tag/v4.0.2)   | Argon      | [3408600](https://www.mintscan.io/noble/blocks/3408600) | must set `--halt-height 5262000` to upgrade to next version

-| [`v4.1.2`](https://github.com/noble-assets/noble/releases/tag/v4.1.2)   |            | [6022000](https://www.mintscan.io/noble/block/5797500)  | must set `--halt-height 6139500` to upgrade to next version
+| [`v4.1.2`](https://github.com/noble-assets/noble/releases/tag/v4.1.2)   |            | [6022000](https://www.mintscan.io/noble/blocks/6022000) | must set `--halt-height 6139500` to upgrade to next version

-| [`v4.1.3`](https://github.com/noble-assets/noble/releases/tag/v4.1.3)   |            | [6139500](https://www.mintscan.io/noble/block/5797500)  | 
+| [`v4.1.3`](https://github.com/noble-assets/noble/releases/tag/v4.1.3)   |            | [6139500](https://www.mintscan.io/noble/blocks/6139500) |

Committable suggestion skipped: line range outside the PR's diff.

🤖 Prompt for AI Agents
In docs/chain-upgrades/mainnet.mdx around lines 24-29, several Mintscan Start
Height links use the singular path (/block/) and have mismatched block numbers;
update each URL to use the plural path (/blocks/) and ensure the numeric ID in
the URL matches the displayed Start Height: v3.1.0 stays /blocks/2672000, change
v4.0.2 to /blocks/3408600, change v4.0.3 to /blocks/5262000 (already correct
path/number if needed), change v4.1.1 to /blocks/5797500, change v4.1.2 to
/blocks/6022000, and change v4.1.3 to /blocks/6139500 so every link points to
/blocks/<displayed-height>.

Comment thread docs/chain-upgrades/mainnet.mdx Outdated
Co-authored-by: John Letey <john@nobleassets.xyz>
Copy link
Copy Markdown
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

♻️ Duplicate comments (1)
docs/chain-upgrades/mainnet.mdx (1)

24-29: Fix Mintscan links and height mismatches (/block → /blocks; correct IDs).

Several rows still use the singular path and have mismatched block IDs vs displayed Start Height. This is a user-facing correctness issue.

Apply this diff:

-| [`v3.1.0`](https://github.com/noble-assets/noble/releases/tag/v3.1.0)   | v3.1.0     | [2672000](https://www.mintscan.io/noble/block/2672000)  |
+| [`v3.1.0`](https://github.com/noble-assets/noble/releases/tag/v3.1.0)   | v3.1.0     | [2672000](https://www.mintscan.io/noble/blocks/2672000) |

-| [`v4.0.2`](https://github.com/noble-assets/noble/releases/tag/v4.0.2)   | Argon      | [3408600](https://www.mintscan.io/noble/block/3377500)  | must set `--halt-height 5262000` to upgrade to next version
+| [`v4.0.2`](https://github.com/noble-assets/noble/releases/tag/v4.0.2)   | Argon      | [3408600](https://www.mintscan.io/noble/blocks/3408600) | must set `--halt-height 5262000` to upgrade to next version

-| [`v4.0.3`](https://github.com/noble-assets/noble/releases/tag/v4.0.3)   |            | [5262000](https://www.mintscan.io/noble/block/5262000)  | 
+| [`v4.0.3`](https://github.com/noble-assets/noble/releases/tag/v4.0.3)   |            | [5262000](https://www.mintscan.io/noble/blocks/5262000) |

-| [`v4.1.1`](https://github.com/noble-assets/noble/releases/tag/v4.1.1)   | Fusion     | [5797500](https://www.mintscan.io/noble/block/5797500)  | must set `--halt-height 6022000` to upgrade to next version
+| [`v4.1.1`](https://github.com/noble-assets/noble/releases/tag/v4.1.1)   | Fusion     | [5797500](https://www.mintscan.io/noble/blocks/5797500) | must set `--halt-height 6022000` to upgrade to next version

-| [`v4.1.2`](https://github.com/noble-assets/noble/releases/tag/v4.1.2)   |            | [6022000](https://www.mintscan.io/noble/block/5797500)  | must set `--halt-height 6139500` to upgrade to next version
+| [`v4.1.2`](https://github.com/noble-assets/noble/releases/tag/v4.1.2)   |            | [6022000](https://www.mintscan.io/noble/blocks/6022000) | must set `--halt-height 6139500` to upgrade to next version

-| [`v4.1.3`](https://github.com/noble-assets/noble/releases/tag/v4.1.3)   |            | [6139500](https://www.mintscan.io/noble/block/5797500)  | 
+| [`v4.1.3`](https://github.com/noble-assets/noble/releases/tag/v4.1.3)   |            | [6139500](https://www.mintscan.io/noble/blocks/6139500) |
🧹 Nitpick comments (1)
docs/chain-upgrades/mainnet.mdx (1)

21-21: Genesis height label/link mismatch (0 vs 1).

Displayed Start Height is 0 but the link points to block 1. Consider aligning the label to 1 or removing the link on genesis if Mintscan has no page for height 0.

Option A:

-| [`v1.0.0`](https://github.com/noble-assets/noble/releases/tag/v1.0.0)   |            | [0](https://www.mintscan.io/noble/blocks/1)             | Genesis Version
+| [`v1.0.0`](https://github.com/noble-assets/noble/releases/tag/v1.0.0)   |            | [1](https://www.mintscan.io/noble/blocks/1)             | Genesis Version

Option B:

-| [`v1.0.0`](https://github.com/noble-assets/noble/releases/tag/v1.0.0)   |            | [0](https://www.mintscan.io/noble/blocks/1)             | Genesis Version
+| [`v1.0.0`](https://github.com/noble-assets/noble/releases/tag/v1.0.0)   |            | 0                                                       | Genesis Version
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7c4a50c and 7ae8385.

📒 Files selected for processing (1)
  • docs/chain-upgrades/mainnet.mdx (1 hunks)
🔇 Additional comments (1)
docs/chain-upgrades/mainnet.mdx (1)

37-37: Add “recommended” note for Ember (v10.1.1) upgrade

In docs/chain-upgrades/mainnet.mdx, update the Ember row to include the “recommended” label and keep the singular /block URL:

-| [`v10.1.1`](https://github.com/noble-assets/noble/releases/tag/v10.1.1) | Ember      | [28613000](https://www.mintscan.io/noble/block/28613000)|
+| [`v10.1.1`](https://github.com/noble-assets/noble/releases/tag/v10.1.1) | Ember      | [28613000](https://www.mintscan.io/noble/block/28613000)| recommended |

Please verify that 28613000 is the correct start height for v10.1.1.

Comment thread docs/chain-upgrades/mainnet.mdx
@johnletey johnletey merged commit 5c24618 into main Sep 10, 2025
3 checks passed
@johnletey johnletey deleted the dan/v10-upgrade branch September 10, 2025 07:42
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