chore: refresh dependencies and infrastructure pins - #151
Merged
Conversation
Co-authored-by: Gábor Pichner <[email protected]>
Lighthouse results
Updated automatically by CI. |
95gabor
marked this pull request as ready for review
July 20, 2026 07:10
Contributor
Author
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
95gabor
approved these changes
Jul 20, 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
Verification
pnpm install --frozen-lockfilepnpm audit --audit-level low— no known vulnerabilitiespnpm run lint— passed with existing warnings in.commitlintrc.jsandrelease.config.mjspnpm run typecheckpnpm run build— blocked locally becauseSUPABASE_URLis not set in this runner; Docker is also unavailable for local Supabase setupNotes
@percy/clipinned at 1.31.14 because newer Percy packages still pull the previously vulnerablefast-xml-parserpath.@types/nodeon Node 24, and did not cross ESLint 10 / TypeScript 7 major lines in this maintenance pass.