Repository navigation
Bump next to 16.4.2 and follow-redirects - #485
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
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
next16.3.8 → 16.4.2 andfollow-redirects(via axios) 1.16.0 → 1.16.1. No behavior change.Evidence
yarn npm audit --environment production: next 1242816 / 1242818 / 1242859 (fixed after 16.4.0; the app uses server actions), follow-redirects 1242604 / 1242605.Proof
yarn exec tsc --noEmitclean.yarn test:unit: 8/8.yarn buildexit 0, with the slot-5 LessonsApi running so the sitemap could prerender.