fix(template): refresh Next.js nanoid lock resolution - #28
Merged
Conversation
Uh oh!
There was an error while loading. Please reload this page.
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 freeto 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.
Summary
nanoidresolves to 3.3.18nanoid >=3.3.17invariant in the normal template testCommits
e073145fix(template): refresh nanoid lock resolutionb657ab6test(template): enforce safe nanoid baselinee4a6d5bdocs: document template lock refreshesVerification
The release check exercised the generated
next-appthroughnpm ci --ignore-scripts, ESLint, a production Next.js build,npm audit --omit=dev --audit-level=high(0 production vulnerabilities),scripts/validate.sh, and package smoke.Closes the time-dependent template lock drift identified at origin/main b487d49.