Repository navigation
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.
Summary
Patch the Rust TLS verifier/root bundle and HTTP transport locks, require certifi 2026.10.19 for Python consumers, and update both Python lockfiles. Refresh affected TypeScript test tooling, require supported patched Node versions, and pin CI/release recipes to the October security releases.
Changelog: part of October 2026 cross-project security remediation program.
Test Plan
just pre-prandjust pre-pushpassed with Rust 1.99.0 and Node 26.12.1, including Rust mock-server tests, Python 201 tests, TypeScript 188 tests, generation helper tests, and example checks.Compatibility
The Python trust-bundle minimum and Node engine floor are intentional security requirements. Rust downstream consumers with existing lockfiles must update them to obtain the patched transitive versions.