[Release|CI/CD] Fixes for release flows#11578
Merged
EgorPopelyaev merged 11 commits intomasterfrom Apr 1, 2026
Merged
Conversation
## Summary - Bumps `parity-publish` from `0.10.12` to `0.10.13` in the release publish crates workflow - Increases wait time between crate releases from 15s to 60s because of the 429 response after making release process faster
## Summary - Moves the "Validate resume preconditions" step after the "Checkout stable branch" step so `git ls-remote` runs in an initialized git repo - Fixes the failed publish crates workflow resume: https://github.com/paritytech-release/polkadot-sdk/actions/runs/23620337279/job/68797902086#step:25:20 ## Test plan - Resume the publish crates workflow from the release org after this is merged and synced
## Summary - Fix resume validation in publish crates workflow by using local ref check (`git branch -r`) instead of `git ls-remote`, which fails because `persist-credentials: false` prevents remote access ## Context - Failed run: https://github.com/paritytech-release/polkadot-sdk/actions/runs/236 20337279/job/68797902086#step:25:20
## Summary - Moves the "Validate resume preconditions" step after "Configure git" so that `safe.directory` is set before any git commands run - Uses `git branch -r` instead of `git ls-remote` since `persist-credentials: false` prevents remote access ## Context - Previous fix moved the step after checkout, but it still ran before `safe.directory` was configured, causing `dubious ownership` errors
EgorPopelyaev
added
the
R0-no-crate-publish-required
BDevParity
approved these changes
Mar 31, 2026
Contributor
|
Review required! Latest push from author must always be reviewed |
EgorPopelyaev
added
R0-no-crate-publish-required
AndWeHaveAPlan
approved these changes
Apr 1, 2026
bkontur
approved these changes
Apr 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR backports few fixes for soem release flows, that were made in stable2603 branch. In particular: