ci(publish): pular npm publish quando a versão já existe - #1
Merged
Merged
Conversation
Guard antes do whoami/publish: consulta `npm view` e, se a versão do package.json já está publicada, encerra o job verde. Permite Releases retroativos e re-runs sem falhar (o npm é imutável por versão). Co-Authored-By: Claude Opus 4.8 (1M context) <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.
Adiciona um guard no
publish.yml: antes dowhoami/publish, consultanpm view @orynlabs/smsgo@$VERSION. Se a versão dopackage.jsonjá está no npm, o job encerra verde e pula a publicação.Por quê: o npm é imutável por versão. Sem isso, um GitHub Release retroativo (ex.:
v0.3.0, já publicado) ou um re-run do workflow falha emnpm publish. Com o guard, esses casos ficam limpos; versões novas seguem publicando normalmente com--provenance.🤖 Generated with Claude Code