Repository navigation
fix: refresh patched Rust worker and template trust dependencies - #269
Merged
Merged
Conversation
|
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.
Refs durable-workflow/.github#237, RUSTSEC-2026-0381 and RUSTSEC-2026-0382.
Update only webpki-roots to 1.0.10 and rustls-webpki to 0.103.16, including registry checksums, in the Rust worker/template locks. Existing SDK 4.1.0 pins, source/protocol, PHP/Python dependencies and historical evidence remain unchanged.
Both locked/offline Rust 1.86 builds pass. All applicable normal repository checks pass, including the candidate image, polyglot smoke, documented SDK/application workflows and upgrade scenarios, namespaces, typed search attributes, CodeQL, public boundary and Sonar. This qualifies this source/tree; an older failed Sample #255 observation remains failed with unknown cause. No rescue, complete OS-bundle remediation or new SDK/image adoption is claimed by this narrow lock refresh.