Skip to content

Chore remove stable2603 upgrade working doc - #3809

Merged
manuelmauro merged 1 commit into
masterfrom
chore-remove-stable2603-upgrade-doc
Jul 9, 2026
Merged

manuelmauro merged 1 commit into
masterfrom
chore-remove-stable2603-upgrade-doc

Conversation

@manuelmauro

@manuelmauro manuelmauro commented Jul 9, 2026 •

Copy link
Copy Markdown
Contributor

What does it do?

Deletes docs/cherry-picks/UPGRADE-stable2603.md.

This was a temporary working doc tracking the polkadot-sdk upgrade from stable2512 to stable2603. That upgrade shipped in #3746, and the doc's own header says to delete it once the upgrade lands.

What stays

Per the doc's drop checklist:

  • polkadot-sdk-stable2603.md — the cherry-pick tracker for this cycle.
  • polkadot-sdk-stable2512.md and polkadot-sdk-stable2506.md — kept for historical reference.

Notes

Docs-only change; nothing in the repo links to the deleted file.

Phase 5 (bridge maintenance: rebuild substrate-relay against stable2603, regenerate zombienet relay chain specs, run bridge integration tests) was still unchecked in the doc and is not carried over anywhere.


View with Codesmith Autofix with Codesmith
Need help on this PR? Tag /codesmith with what you need. Autofix is disabled.

The polkadot-sdk stable2603 upgrade shipped in #3746, so the temporary
working doc it introduced has served its purpose. The cherry-pick tracker
polkadot-sdk-stable2603.md stays, alongside the stable2512 and stable2506
trackers kept for historical reference.
@coderabbitai

coderabbitai Bot commented Jul 9, 2026 •

Copy link
Copy Markdown
Contributor

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 3ecafe22-6c44-4463-8cd6-3ee7fe308a3f

📥 Commits

Reviewing files that changed from the base of the PR and between e991ea1 and c3c40f3.

📒 Files selected for processing (1)
  • docs/cherry-picks/UPGRADE-stable2603.md
💤 Files with no reviewable changes (1)
  • docs/cherry-picks/UPGRADE-stable2603.md

📝 Walkthrough

Walkthrough

The pull request removes the file docs/cherry-picks/UPGRADE-stable2603.md, deleting the WIP upgrade plan document that tracked phases, branch/cherry-pick instructions, verification steps, and open risks for the polkadot-sdk to stable2603-1 upgrade.

Changes

Cohort / File(s) Summary
Documentation removal
docs/cherry-picks/UPGRADE-stable2603.md
Deleted the entire upgrade planning document, removing all tracked content.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly describes removing the stable2603 upgrade working doc.
Description check ✅ Passed The description is directly related to deleting the upgrade doc and explains the scope correctly.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore-remove-stable2603-upgrade-doc

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.

@manuelmauro manuelmauro added D2-notlive PR doesn't change runtime code (so can't be audited) not-breaking Does not need to be mentioned in breaking changes B0-silent Changes should not be mentioned in any release notes labels Jul 9, 2026
@manuelmauro
manuelmauro merged commit 38fae69 into master Jul 9, 2026
81 of 131 checks passed
@manuelmauro
manuelmauro deleted the chore-remove-stable2603-upgrade-doc branch July 9, 2026 08:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

B0-silent Changes should not be mentioned in any release notes D2-notlive PR doesn't change runtime code (so can't be audited) not-breaking Does not need to be mentioned in breaking changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant