Repository navigation
chore: finalize v0.20.9 release preparation - #966
Merged
Merged
Conversation
Member
|
Since #965 landed, the v0.20.9 plan would ship |
Member
|
Now that #964 has landed, the v0.20.9 plan would ship |
Xuanwo
approved these changes
Nov 20, 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.
Service-account token caching removed
UnwindSafeandRefUnwindSafefrom Google'sRequestSigner, breaking downstream code that captures a signer incatch_unwind. Protect the bounded, synchronous cache operations withstd::sync::Mutex, recover poisoned locks consistently with the refresh-lock registry, and retain the asynchronous locks around per-partition token exchanges. A compile-time assertion guards both public auto-trait implementations.Assign minor versions to crates with new public capabilities and align the root workspace dependency requirements:
reqsign-aws-corereqsign-aws-v4reqsign-aws-v4areqsign-googlereqsign-huaweicloud-obsreqsign-oraclereqsign-tencent-cosGetFederationTokengranterreqsign-volcengine-tosAssumeRolegranter and credential expiry#954's SSO assume-role profile-chain resolution lands in the
reqsign-aws-coreandreqsign-aws-v4minors above. The remaining crates keep the patch bumps from #947, and the release remainsreqsign 0.20.9withreqsign-core 3.3.4.Validation
cargo fmt --all -- --checkand strict workspace Clippy with all targets and features.cargo test --no-fail-fast: 811 passed, 6 ignored.cargo test --doc --workspace --all-features: 76 passed, 6 ignored.cargo semver-checksagainstv0.20.8: the other 14 crates pass patch-level checks. TOS and OBS report onlyconstructible_struct_adds_fieldforCredential.expires_at, the intentional struct-literal break from Tracking: expand GrantCredential across cloud services #807 documented in each README changelog.plan.pyversion alignment; all 16 planned versions are unpublished.cargo publish --workspace --dry-runfor the complete 16-crate publish plan.Existing MSRV limitation
A fresh downstream resolution with the facade's
fullfeature on Rust 1.86 fails for both publishedreqsign 0.20.8and this branch:crypto-bigint 0.7.11andctutils 0.4.8require Rust 1.87. This is a pre-existing dependency-resolution issue, not introduced by this release.