Bump pinned resolutions and refresh lockfile for Dependabot alerts - #71
Merged
Conversation
dggrunzweig
approved these changes
Jul 28, 2026
Regenerates generated/generated.ts and the dist build artifacts so `yarn build && git diff --exit-code` passes in CI. The committed files had drifted behind the live schema (new PeriodFilter scalar, DateFilter.within/withinBalanceUTCOffset, StringMatchFilter.matchesAny, LedgerAccount.payment, SchemaPaymentInput).
Regenerates tests/fixtures/generated-test-client.ts so the "Verify test schema generated files are up-to-date" CI step passes. The fixture had drifted behind the live schema (PeriodFilter scalar, AddLedgerEntries batch types, LedgerAccount.payment, matchesAny, etc.). tests/fixtures/test-schema-queries.graphql regenerated identically, no change.
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
2 participants
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.
Clears 13 of the 15 open Dependabot alerts on
@fragment-dev/node-client. Most of them existed because this repo'sresolutionsblock pins packages to exact versions that earlier advisories had made safe and later advisories made vulnerable again — the pins were holding the tree below the patched releases.Pins bumped in
package.json:ws8.17.1 → 8.21.0 (CVE-2026-48779)vite6.4.1 → 6.4.3 (CVE-2026-53571, plus the bundledlaunch-editorCVE-2026-53632)tar7.5.11 → 7.5.22 (five advisories, including the critical CVE-2026-59873)brace-expansion@^1.1.71.1.12 → 1.1.16 (CVE-2026-13149)Re-resolved within existing ranges, no
package.jsonchange needed:js-yaml→ 4.3.0,@babel/core→ 7.29.7,shell-quote→ 1.10.0.Left open deliberately: the two
immutablealerts (GHSA hash-collision andListtrie-overflow DoS).immutableresolves to 3.7.6 because@ardatan/relay-compiler@12.0.0pins~3.7.6, reached via@graphql-tools/relay-operation-optimizerunder the graphql-codegen plugins. The advisories' first patched version is 4.3.9, so clearing them means forcing relay-compiler across the breaking 3.x → 4.x boundary. This repo has no Relay usage, so that optimizer never runs. Proposed for dismissal separately rather than fixed here.Verified:
yarn typecheckclean.yarn test:cipasses 5 tests; the 12 failures are pre-existing and environmental —tests/generated-sdk.test.tsand one other live-API suite throwPlease provide CLIENT_ID, CLIENT_SECRET, ...fromgetClientbefore any request is made, so they need credentials this run did not have.🤖 Generated with Claude Code