Repository navigation
chore: upgrade dependencies and fix vulnerabilities - #109
Merged
Merged
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 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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
pnpm auditonmainreports known vulnerabilities in the dependency tree, including critical Next.js (unauthenticated RCE on Windows), critical MapLibre GL JS (XSS sanitizer bypass), high sharp (libheif), moderate qs (array-limit bypass,isBufferDoS), moderate Vitest (@vitest/mockerpath traversal), and moderatebaseline-browser-mapping(DoS). Direct dependency ranges inpackage.jsonpin the vulnerable lines (next ^16.3.0,sharp ^0.35.3,vitest/@vitest/coverage-v8 ^4.1.10,@maplibre/maplibre-gl-leaflet ^0.1.3).What is the new behavior?
Upgrades dependencies to resolve all
pnpm auditadvisories (zero remaining). Files changed (2 files, +281/−324):package.json(6 version bumps) andpnpm-lock.yaml(regenerated).Advisories fixed:
next ^16.3.0->^16.3.4(plus@next/env ^16.3.0->^16.3.4)@maplibre/maplibre-gl-leaflet ^0.1.3->^0.1.4@vitest/mocker—vitest/@vitest/coverage-v8 ^4.1.10->^4.1.11sharp ^0.35.3->^0.35.4Overrides dropped: initially added scoped overrides for
maplibre-glandbaseline-browser-mapping, but re-tested without them — natural resolution already reaches patched versions, so they were removed. Final override list: none added (pre-existing overrides untouched).Verification commands and results:
pnpm audit: No known vulnerabilities foundpnpm lint(biome): cleanpnpm test(NODE_ENV=test): 8 files, 58 passed, 1 todopnpm build: successbuild (22.x)ande2e, CodeQL)Other information
Branch
chore/deps-security-updates->main(2 commits:b025ff5upgrade dependencies and fix vulnerabilities,d0ceb54drop unneeded overrides). No code, test, or config changes — dependency versions and lockfile only. No related issue.