fix: pin package.json dependencies instead of using latest (#48) - #49
Open
erhnysr wants to merge 1 commit into
Open
fix: pin package.json dependencies instead of using latest (#48)#49erhnysr wants to merge 1 commit into
erhnysr wants to merge 1 commit into
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
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.
Problem
package.jsonused the mutablelatesttag for three production dependencies:latestmakes builds non-reproducible: the installed version depends on the npm registry state at install time rather than on the repository revision, so two checkouts of the same commit can resolve to different (and potentially breaking) versions.Fix
Pins each of the three to the exact version already recorded in
package-lock.jsonas the currently resolved version:@supabase/ssrlatest0.8.0@supabase/supabase-jslatest2.93.3nextlatest16.1.6No behavior change — these are the versions the lockfile already resolves to today. The only effect is that builds become deterministic. The matching spec strings in
package-lock.jsonare updated so the manifest and lockfile stay in sync.Closes #48