build(deps): roll up release dependency patches - #396
Merged
Conversation
Combine the vetted Rust dependency and Node tooling updates into one coherent set of lockfiles for the next release. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Bring the roadmap forward to v0.6.x and align architecture and test references with the current core module layout and concurrency model. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
This was referenced Aug 28, 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
bytesto 1.12.1,mdns-sdto 0.20.2,napito 3.10.5,napi-deriveto 3.5.10, andthiserrorto 2.0.19@napi-rs/clito 3.7.3 and@types/nodeto 26.1.1This rollup supersedes #351, #352, #353, #357, #383, #384, and #385. The optional jsdom 30 update in #393 is intentionally excluded because it drops the documented Node 18/20 development floor. The conflicted Vitest update in #356 and failing TypeScript 7 migration in #354 remain separate.
Validation
npm run ci