chore: bump firebase, taquito, fix protobufjs/noble-hashes CVEs#949
Merged
Conversation
- firebase 11.0.2 -> 11.10.0 (drops vestigial @firebase/app & @firebase/firestore direct pins) - @taquito/* 24.2.0 -> 24.3.0 - resolutions: protobufjs 7.5.8 (clears 1 critical + 4 high CVEs via @grpc/proto-loader) - resolutions: @noble/hashes 1.8.0 (works around @taquito 24.3.0 nested @noble/curves break against @noble/hashes 2.x exports field) Audit: critical 5 -> 1, high 153 -> 134.
✅ Deploy Preview for tezos-homebase ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
dompurify 3.3.0 -> 3.4.3 across the tree (direct dep + transitive via posthog-js and @types/dompurify). Added a resolution so the lockfile keeps a single copy. Patches dompurify CVEs landed in 3.4.x; dompurify is in the XSS-defense path for sanitized markdown rendering on DAO list cards and Etherlink proposal details.
Same-major minor/patch bumps with no breaking-change risk: Runtime: - @tanstack/react-query 5.90.20 -> 5.100.10 - connectkit 1.9.1 -> 1.9.2 - dayjs 1.11.19 -> 1.11.20 - graphql 15.10.1 -> 15.10.2 - html-react-parser 5.2.14 -> 5.2.17 - posthog-js 1.336.1 -> 1.373.4 - react-hook-form 7.71.1 -> 7.75.0 - @types/prismjs 1.26.5 -> 1.26.6 Dev: - @playwright/test 1.58.0 -> 1.60.0 - dotenv 17.2.3 -> 17.4.2 - ts-jest 29.4.6 -> 29.4.9 (clears the last critical: handlebars CVE) Audit: critical 1 -> 0, high 134 -> 130, moderate 127 -> 109.
Document the @noble/hashes ecosystem split that currently blocks unpinning wagmi/viem: @taquito 24.x's nested @noble/curves requires @noble/hashes 1.x, while current viem (via ox) requires 2.x. Saves the next person from rediscovering this the hard way.
…-taquito-protobufjs-noble # Conflicts: # yarn.lock
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
1 participant
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
Security-focused dependency bumps targeting runtime CVEs in the user-facing bundle.
firebase11.0.2 → 11.10.0 (drops vestigial@firebase/appand@firebase/firestoredirect pins that were older than what the umbrella ships)@taquito/*24.2.0 → 24.3.0resolutions["protobufjs"] = "7.5.8"— forces@grpc/proto-loadertransitive past the critical advisoryresolutions["@noble/hashes"] = "1.8.0"— works around@taquito 24.3.0's nested@noble/curvesimporting@noble/hashes/utilswithout the.jsextension, which the new@noble/hashes2.x exports field rejects (build break otherwise)Audit impact
protobufjs)protobufjschain +@taquito→axioschain)Remaining 1 critical is
handlebarsviats-jest— dev-only, does not ship.Most of the remaining 134 high are in dev tooling (
react-scripts,eslint,serve,jest, etc.) that doesn't reach the browser bundle.Test plan
yarn install— cleanyarn build— greennpx tsc --noEmit— greenyarn test:unit— same 2 pre-existing jsdom-env failures, no new regressions