Repository navigation
fix(deps): update consumer fixture dependencies - #535
Merged
Merged
Conversation
Contributor
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
theme-basalt | 28a0309 | Oct 07 2026, 10:21 PM |
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.
Four consumer fixtures still requested Lucide 1.48.0 even though the catalog had moved to 1.49.0. Align those fixture declarations and patch the Next consumer from 16.3.6 to 16.3.8, which fixes six newly reported advisories. Keep the existing exact-version contract assertions and fixture documentation aligned. The root dependency graph is unchanged.
Issues
Closes #532
Closes #534
Validation