🔥Hotfix - Fix Corepack error in build pipeline #3571
Merged
Conversation
This file contains 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
Coverage report
Test suite run success13 tests passing in 1 suite. Report generated by 🧪jest coverage report action from e0d21ff |
Calinator444
changed the title
|
Deployed changes to https://app-sswwebsite-9eb3-pr-3571.azurewebsites.net |
PageSpeed Insights
View the full report https://pagespeed.web.dev/report?url=https://app-sswwebsite-9eb3-pr-3571.azurewebsites.net |
Calinator444
changed the title
wicksipedia
approved these changes
Feb 3, 2025
3 tasks
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.
Older versions of Corepack have the the npm registrey key (which was recently updated) hard coded. The alpine image we use in the Docker container for our deployment pipeline still uses a version of Corepack with the old key, causing our deployments to fail when we try to enable Corepack during the build step.
See issue nodejs/corepack#625 (comment).
To fix this I've updated our build pipeline to manually install the latest version of Corepack. The fix was published here.
Affected routes: N/a
Fixed 🚀 CI/CD - CorePack Build error in pipeline #3572
Include done video or screenshots
Figure: Build pipeline running successfully