This repository was archived by the owner on Nov 13, 2026. It is now read-only.
Repository navigation
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 lockfile resolves tar 7.5.10 and brace-expansion 2.0.2 / 5.0.4. Upgrade them to the patched versions with version-scoped pnpm overrides:
Regenerate the lockfile and update the affected @mapbox/node-pre-gyp and minimatch resolutions. Direct dependencies and unrelated lockfile package metadata remain unchanged. The brace-expansion 5.x update requires Node 20 or >=22, which is compatible with this repository's Node 24/26 engine constraint. This also reaches a newer tar patch than the tar update in #1.
Validation:
Generated with Node 24.22.1 and pnpm 10.34.9; pnpm accepts the lockfile as up to date under --frozen-lockfile.
Parsed both YAML files and verified that only the three intended package versions and their transitive references changed. No old targeted versions remain in package or snapshot entries.
git diff --check and a Gitleaks scan of the patch pass.
Full and production-only frozen installs are blocked locally by HTTP 403 fetching the existing node-forge@1.3.3 package. Build, type-check, lint, and integration tests could not run. An isolated Prettier check also could not load the project's uninstalled shared configuration.
The initial CI run was cancelled by @stepsecurity-app[bot], according to the check annotation. No additional reason was supplied. CI validation is still required.