Repository navigation
fix(deps): Patch Vite and prepare Figbird prerelease - #161
Merged
Merged
Conversation
matt-humaan
changed the title
matt-humaan
marked this pull request as ready for review
October 21, 2026 19:44
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
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.
The refreshed inventory exposes three Vite launch-editor advisories in the demo. Raise the declared Vite floor within v8 and regenerate its lockfile.
Bump Figbird from 0.24.0-pre.22 to 0.24.0-pre.23 so the previously merged package dependency fixes are included in a new release. This retains the existing prerelease line and next tag. After merge, the existing workflow tests/builds the package and stages it on npm for maintainer approval.
Validation: the original dependency change passed demo build/audit and GitHub CI. For the subsequent version bump, verified that package.json and both lockfile version fields agree and that no other JSON data changed; fresh CI is triggered by this push. No local builds, tests or type checks were run for the version bump. The root sprintf-js advisory remains separate.
https://linear.app/humaans/issue/SUP-4142/update-all-clear-soon-vulnerabilities