Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[stable2407] Backport Fix parity-publish (#5670) #6019

Merged
merged 1 commit into from
Oct 10, 2024

Conversation

EgorPopelyaev
Copy link
Contributor

No description provided.

Install with `--locked` to try to fix the CI.

Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io>
@EgorPopelyaev EgorPopelyaev added R0-silent Changes should not be mentioned in any release notes A3-backport Pull request is already reviewed well in another branch. labels Oct 10, 2024
@EgorPopelyaev EgorPopelyaev requested review from a team as code owners October 10, 2024 17:20
Copy link

This pull request is amending an existing release. Please proceed with extreme caution,
as to not impact downstream teams that rely on the stability of it. Some things to consider:

  • Backports are only for 'patch' or 'minor' changes. No 'major' or other breaking change.
  • Should be a legit fix for some bug, not adding tons of new features.
  • Must either be already audited or trivial (not sure audit).
Emergency Bypass

If you really need to bypass this check: add validate: false to each crate
in the Prdoc where a breaking change is introduced. This will release a new major
version of that crate and all its reverse dependencies and basically break the release.

@paritytech-cicd-pr
Copy link

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable 1/3
Logs: https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/7555505

@EgorPopelyaev EgorPopelyaev merged commit f72fe54 into stable2407 Oct 10, 2024
118 of 170 checks passed
@EgorPopelyaev EgorPopelyaev deleted the ep-backport-parity-publish-fix branch October 10, 2024 17:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A3-backport Pull request is already reviewed well in another branch. R0-silent Changes should not be mentioned in any release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants