fix(deploy): pin npm for Amplify builds - #8
Merged
Merged
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.
Description
11.6.2during the Amplify frontend pre-build phase so it matches the repository's declared package manager.Link to issue or ticket
N/A
Steps to QA
mainbranch.11.6.2.npm cicompletes without the apackage-lock synchronization error.npx turbo run build --filter=weband publishes the frontend artifact successfully.Local verification confirmed that
amplify.ymlparses successfully and that this branch differs frommainonly by the npm setup commands in the Amplify pre-build phase.Screenshots
N/A