chore: stop dependabot proposing maplibre-gl 6.x - #21
Merged
Merged
Conversation
maplibre-gl is pinned to 5.24.0 because react-map-gl v8 (@vis.gl/react-maplibre) cannot render with 6.x: the map constructs and the style parses into its layers, but it never reaches `loaded`, so the source caches are never built and no basemap tile is ever requested. The map renders blank with no error. Dependabot has now proposed the 6.x bump three times (#14, #17, #20), and each one would silently revert #16. Ignore the 6.x line until upstream supports it. The pin carries CVE-2026-85061, which is exempted with the same removal condition in pnpm-workspace.yaml: drop both once react-map-gl renders with maplibre-gl >= 6.4.1. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f30833812d
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
This branch was successfully deployed
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.
Why
maplibre-glis pinned to5.24.0(#16) because react-map-gl v8 cannot render with maplibre-gl 6.x: the map constructs and the style parses into its layers, but it never reachesloaded, so the source caches are never built and no basemap tile is ever requested. The map goes blank with no error, which is what made this hard to spot.Dependabot has now proposed the 6.x bump three times — #14, #17, #20 — and each one would have silently reverted the fix. #20 was the clearest case: everything else in it was fine, but it carried
maplibre-gl: ^6.9.1.What changed
An
ignoreentry formaplibre-gl >= 6.0.0, with the reason and the removal condition in a comment.This does not block anything else: the rest of the production group (Radix, date-fns, framer-motion, lucide-react, jose, swr, tailwind-merge, mapbox-gl, React, Next) will keep flowing normally.
Related state
prismaand@prisma/clienttogether at 6.2.1 instead of splitting them.pnpm-workspace.yamlwith the same removal condition.Both the ignore here and the CVE exemption come off together once react-map-gl renders with maplibre-gl >= 6.4.1.
Test plan
updatesblock parses (the Psych error on the dockerupdate-typesline is pre-existing and untouched)🤖 Generated with Claude Code