Repository navigation
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
bashkit | 47ab411 | Commit Preview URL Branch Preview URL |
Oct 22 2026, 03:10 PM |
chaliy
marked this pull request as ready for review
October 22, 2026 15:39
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This branch has not been deployed
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.
What changed
Supported Node22/24 build, site and package-release recipe lanes select the October21 security patch versions22.23.4/24.22.1 instead of cached floating majors. Both native-binding runtime matrices use the same exact patched versions. The existing Windows/Node24 exception follows its updated exact matrix value.
Why
A floating major can reuse a runner-cached pre-fix runtime after a security release. Node runtime/OpenSSL/root-store fixes are separate from npm lockfile auditing.
Before / After
Node22→22.23.4 and24→24.22.1 for supported CI/build lanes. No interpreter/API behavior or dependency lock changes. The intentionally retained Node20 compatibility-only test lane is EOL and has no upstream supported security patch; it is not represented as fixed or as a deployment recommendation. Published native consumers still need the user's patched library artifacts and their own supported Node runtime.
Validation: full just pre-pr PASS on repository-pinned Rust1.95.0;7259 passed Rust test results across34 groups,65 existing ignored;179 Python script tests; format/strictClippy/docs/OKF/capability/workflow parity; cargo-vet success under unchanged policy. Actionlint structural validation and37 docs-route checks pass. Affected hosted JS/site CI must pass before merge. The initial check on workspaceRust1.99 was corrected to the repository pin without changing Rust source or lint policy.
Risk
Remaining findings
Development-only braces3.0.3 remains via AVA/globby/micromatch; latest AVA8.1.0 still uses that graph and no patched braces version is published. Native TLS/Wasmtime fixes already landed separately. User-owned Rust/JS/Python publication and downstream lock refresh remain required.
Checklist