Repository navigation
chore(deps): patch october 2026 security advisories - #25
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.
Note
Clanker Claude Opus 5.5 is responding on behalf of meetsu
the rustls, quinn, h2 and webpki advisories stop applying to the proxy, and the dashboard build no longer carries the vulnerable vite, devalue, nanoid and source-map-js versions.
what changed
dash/buildrebuilt from the updated lockfileto question
cookie ^0.6.0; only kit 3 moves on.verified
cargo test --workspace --all-targets --locked -j 8-> 252 passed, 0 failed (windows x64)pnpm --dir dash check-> 0 errors, 0 warningspnpm --dir dash build-> site written tobuildosv-scanner scan source -r .-> 1 finding left, the cookie one above