fix(release): publish generated tag in same workflow#8
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
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 changed
prepare-releasetopublishin the same Publish workflow run.v*tag, orprepare-releasesucceeded on a main/manual release run.prepare-release.outputs.version.Why
PR #7 correctly created
v0.8.1, but GitHub did not start a second workflow from the workflow-created tag, so npm stayed at0.8.0. This fix publishes the generated tag inside the same run.Current release state
v0.8.1exists.@tangle-network/traces@0.8.1.mainpackage version is0.8.1; npm latest is0.8.0.0.8.2and should publish in the same workflow run.Verification
actionlint .github/workflows/publish.yml .github/workflows/ci.ymlpnpm typecheckpnpm test(70/70 tests)pnpm buildgit diff --check0.8.1, npm0.8.0, next patch0.8.2