Skip to content

Comments

Release v2.0.7 (do not merge, just to see the diff)#1074

Closed
bkontur wants to merge 1 commit intorelease-v2.0.6from
release-v2.0.7
Closed

Release v2.0.7 (do not merge, just to see the diff)#1074
bkontur wants to merge 1 commit intorelease-v2.0.6from
release-v2.0.7

Conversation

@bkontur
Copy link
Contributor

@bkontur bkontur commented Feb 16, 2026

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

Found changelog formatting issues (whitespace/blank lines) and a potential mismatch between the release notes and the actual changes in this diff. Also, this diff bumps spec_version across multiple runtimes with no other runtime logic changes shown—confirm this is intentional to avoid triggering unnecessary upgrades.

Comment on lines +7 to +12
## [2.0.7] 16.02.2026

### Added

- Add hyperbridge to parachains header root ([#1073](https://github.com/polkadot-fellows/runtimes/pull/1073))

Choose a reason for hiding this comment

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

The new 2.0.7 section includes blank lines that appear to contain a single space (see the added empty-looking lines at [Line 8], [Line 10], [Line 12]). This introduces trailing whitespace and can break strict markdown/changelog tooling (and makes diffs noisy). Remove the whitespace-only lines (use truly empty lines) and keep formatting consistent with surrounding entries.


### Added

- Add hyperbridge to parachains header root ([#1073](https://github.com/polkadot-fellows/runtimes/pull/1073))

Choose a reason for hiding this comment

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

The changelog claims “Add hyperbridge to parachains header root (#1073)”, but within this reviewed commit range the only code changes are spec_version bumps. If PR #1073 is not actually included in the release branch history, this entry is misleading. Either ensure the backport is included in this release branch/PR, or adjust the 2.0.7 notes to reflect the actual included changes.

impl_name: alloc::borrow::Cow::Borrowed("parity-kusama"),
authoring_version: 2,
spec_version: 2_000_006,
spec_version: 2_000_007,

Choose a reason for hiding this comment

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

spec_version is bumped to 2_000_007. In this diff, no other runtime logic changes are shown; bumping spec_version alone will still force a runtime upgrade. Confirm that (a) an upgrade is intended for Kusama relay in v2.0.7, and (b) this bump aligns with the actual set of runtime changes included in the release branch.

impl_name: alloc::borrow::Cow::Borrowed("parity-polkadot"),
authoring_version: 0,
spec_version: 2_000_006,
spec_version: 2_000_007,

Choose a reason for hiding this comment

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

spec_version is bumped to 2_000_007 with no other runtime logic changes shown in this diff. Confirm Polkadot relay is intended to be upgraded in this release; otherwise consider avoiding a spec_version bump here to prevent an unnecessary on-chain upgrade.

impl_name: Cow::Borrowed("statemine"),
authoring_version: 1,
spec_version: 2_000_006,
spec_version: 2_000_007,

Choose a reason for hiding this comment

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

spec_version is bumped to 2_000_007. Given the diff only changes the version constant, confirm an Asset Hub Kusama runtime upgrade is intended for v2.0.7; otherwise this may trigger unnecessary governance/upgrade operations.

impl_name: Cow::Borrowed("coretime-polkadot"),
authoring_version: 1,
spec_version: 2_000_006,
spec_version: 2_000_007,

Choose a reason for hiding this comment

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

spec_version is bumped to 2_000_007 with no other changes shown. Confirm Coretime Polkadot runtime upgrade is intended for v2.0.7; otherwise avoid bumping spec_version.

impl_name: Cow::Borrowed("encointer-parachain"),
authoring_version: 1,
spec_version: 2_000_006,
spec_version: 2_000_007,

Choose a reason for hiding this comment

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

spec_version is bumped to 2_000_007 with no other runtime changes shown in this diff. Confirm Encointer runtime upgrade is intended for this release; otherwise avoid the bump to reduce operational overhead.

impl_name: Cow::Borrowed("glutton"),
authoring_version: 1,
spec_version: 2_000_006,
spec_version: 2_000_007,

Choose a reason for hiding this comment

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

spec_version is bumped to 2_000_007 with no other shown runtime changes. Confirm Glutton Kusama runtime upgrade is intended for v2.0.7; otherwise avoid bumping spec_version.

impl_name: Cow::Borrowed("people-kusama"),
authoring_version: 1,
spec_version: 2_000_006,
spec_version: 2_000_007,

Choose a reason for hiding this comment

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

spec_version is bumped to 2_000_007 with no other shown runtime changes. Confirm People Kusama runtime upgrade is intended for v2.0.7; otherwise avoid bumping spec_version.

impl_name: Cow::Borrowed("people-polkadot"),
authoring_version: 1,
spec_version: 2_000_006,
spec_version: 2_000_007,

Choose a reason for hiding this comment

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

spec_version is bumped to 2_000_007 with no other shown runtime changes. Confirm People Polkadot runtime upgrade is intended for v2.0.7; otherwise avoid bumping spec_version.

@github-actions
Copy link

Review required! Latest push from author must always be reviewed

@kianenigma
Copy link
Contributor

Why are we doing this release (seems to be the same for 2.0.6) without merging to main?

@kianenigma kianenigma mentioned this pull request Feb 16, 2026
2 tasks
@sigurpol
Copy link
Contributor

Why are we doing this release (seems to be the same for 2.0.6) without merging to main?

That was a bit surprising to me too, is this what we do for hot-fix only? I believe that for 2.0.6 and 2.0.7 we could have released from main directly, right? That said, I can import CHANGELOG changes in #1065 for 2.1.0 easily - so that's not an issue

@bkontur
Copy link
Contributor Author

bkontur commented Feb 16, 2026

Why are we doing this release (seems to be the same for 2.0.6) without merging to main?

@kianenigma I don't exactly know what was the situation with 2.0.6, but 2.0.7 was discussed around: https://matrix.to/#/!bMWYTUFeSoYacMOlpS:matrix.parity.io/$cL8r8kjlGsIs7oKXLHlO5MTm5eYv2KN1m4NOyJW0tLE?via=parity.io&via=matrix.org&via=matrix.parity.io

This release is intended to ensure that Hyperbridge continues to work in the near future after it is downgraded to a "parathread".
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

4 participants