Repository navigation
ci(ENG-4207): remove the manual publish-tag workflow - #162
Merged
Merged
Conversation
It published defender-v0.9.6 after the release job's npm token failed. Publishing is back on the release job, so the manual path isn't needed. This reverts #161. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Reverts #161. The manual
publish-tagpath was a one-off for publishingdefender-v0.9.6after the release job's npm token failed. Publishing stays on the release-please job.🤖 Generated with Claude Code
Summary by cubic
Removes the manual
publish-tagworkflow so npm publishing happens only through the release-please job.defender-v0.9.6after the release job's npm token failed.Written for commit 65a2d53. Summary will update on new commits.