-
Notifications
You must be signed in to change notification settings - Fork 5.9k
refactor: use separate cache key in release, run standalone after caching #5859
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #5859 +/- ##
=======================================
Coverage 74.94% 74.94%
=======================================
Files 30 30
Lines 1688 1688
Branches 371 371
=======================================
Hits 1265 1265
Misses 361 361
Partials 62 62 Continue to review full report at Codecov.
|
828131c
to
44339d5
Compare
ci/build/npm-postinstall.sh
Outdated
@@ -132,7 +132,7 @@ install_with_yarn_or_npm() { | |||
# HACK: NPM's use of semver doesn't like resolving some peerDependencies that vscode (upstream) brings in the form of pre-releases. | |||
# The legacy behavior doesn't complain about pre-releases being used, falling back to that for now. | |||
# See https://github.com//pull/5071 | |||
npm install --unsafe-perm --legacy-peer-deps --omit=dev | |||
npm install --unsafe-perm --legacy-peer-deps --omit=dev -ddd |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is this -ddd
option?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Silly logging! https://docs.npmjs.com/cli/v8/using-npm/logging#aliases
I may want to remove it though 🤔
This fixes a caching issue causing dependency issues in the release. This now uses a separate cache key across OS's and it runs the standalone release after restoring cache. If we don't do this, the cache in the standalone release is overwritten which we don't want.