fix: Build change with not making release latest #3
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
This commit actually builds our own changes to this Action. So far, that's a change that stops it from making the release "latest" in commit 2736a44 This was built by running `npm build package` locally to avoid working out how to handle auto-release workflows running on a fork.
dancorne
force-pushed
the
dont-make-latest2
branch
from
44b1c5a to
61d3993
Compare
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.
This commit actually builds our own changes to this Action. So far, that's a change that stops it from making the release "latest" in commit 2736a44
This was built by running
npm build packagelocally to avoid working out how to handle auto-release workflows running on a fork.