fix: update blocker on npm #854
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
ghost
requested review from
|
|
lili2311
approved these changes
Nov 4, 2019
thisislawatts
force-pushed
the
fix/update-blocker-on-npm
branch
2 times, most recently
from
24fdbbd
to
c248dd5
Compare
thisislawatts
force-pushed
the
fix/update-blocker-on-npm
branch
from
c248dd5
to
0d07932
Compare
3 tasks
|
🎉 This PR is included in version 1.242.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
What does this PR do?
Fixes an issue where our semantic release build pipeline includes a file intended only for the standalone binary.
It appears that our semantic release process is adding STANDALONE to all builds of our CLI, not only those intended to be used by pkg.
How should this be manually tested?
Run a deployment of the CLI