Repository navigation
fix(deps): hotfix 0.7.1 with the emSign advisory bumps from #2466 - #2471
Merged
Merged
Conversation
Contributor
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
|
|
Contributor
|
Approved: no findings at Nothing to do. Clobber: none. |
…dvisories (#2466) RUSTSEC-2026-0382 (rustls-webpki 0.103.15) and RUSTSEC-2026-0383 (webpki-root-certs 1.0.9), both published 2026-10-20, red cargo-deny on every PR. rustls-webpki 0.103.16 rejects paths through the distrusted emSign intermediates, and webpki-root-certs 1.0.10 drops the emSign ECC Root CA - G3. Lockfile-only change. (cherry picked from commit c0ac8c5)
Hotfix release carrying the rustls-webpki and webpki-root-certs bumps from #2466 (RUSTSEC-2026-0382, RUSTSEC-2026-0383) onto 0.7.0. Claude-Session: https://claude.ai/code/session_01FnY4WzhrnmSEByMntmqsVF
norrietaylor
force-pushed
the
fix/hotfix-0.7.1
branch
from
October 21, 2026 00:13
c9fb868 to
1b26891
Compare
jtnkminimal
approved these changes
Oct 21, 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
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.
Summary
Emergency hotfix for 0.7.0. It cherry-picks #2466 onto
release/0.7.0and cuts it as 0.7.1.rustls-webpki0.103.15 → 0.103.16. The old version can accept certificate paths through the distrusted emSign intermediates.webpki-root-certs1.0.9 → 1.0.10. The old version bundlesemSign ECC Root CA - G3.release/0.7.0isv0.7.0plus #2220 (thepromote.ymldraft-release fix).Commits:
cherry-pick -xof c0ac8c5 (fix(deps): bump rustls-webpki and webpki-root-certs past the emSign advisories #2466). OnlyCargo.lockchanges. One hunk of fix(deps): bump rustls-webpki and webpki-root-certs past the emSign advisories #2466 doesn't apply to 0.7.0 and is left out: it changes thegetrandomversion thattempfiledepends on, which exists only in main's lockfile. The two advisory bumps are byte-identical to fix(deps): bump rustls-webpki and webpki-root-certs past the emSign advisories #2466.package.version0.7.0 → 0.7.1. Version 0.7.0 is already staged and can't be reused.cargo update -wchanges only the workspace crate entries inCargo.lock.Merge with "Create a merge commit" or "Rebase and merge", not squash. Keeping the cherry-pick as its own commit lets
git cherrymatch it to #2466 when the tag is merged back into main (release-pipeline.md step 7).Testing
just check-version:package.version 0.7.1 satisfies the 3 commit(s) since v0.7.0 (patch bump, at least 0.7.1) and is greater than the newest tag v0.7.0just deny:advisories ok, bans ok, licenses ok, sources okRelease steps after merge (docs/internal/release-pipeline.md)
gh workflow run release.yml --ref release/0.7.0 -f versioned=true -f dry_run=true gh workflow run release.yml --ref release/0.7.0 -f versioned=true -f dry_run=false gh workflow run promote.yml -f target=stable -f version=0.7.1 -f dry_run=true gh workflow run promote.yml -f target=stable -f version=0.7.1 # second approver comments `approved`Then merge
v0.7.1back into main with-s ours(step 7). #2220 isn't on main yet, sogit cherrywill list it. Land it on main first.Checklist
BREAKING CHANGE:footer present if this is a breaking change (not breaking)🤖 Generated with Claude Code
https://claude.ai/code/session_01FnY4WzhrnmSEByMntmqsVF