Fix/release publish npm token#13
Merged
Merged
Conversation
…via GitHub Actions - workflow atualizado para: - executar standard-version no CI - push automático de commits e tags gerados - publicar pacote no npm automaticamente após release - uso de token de acesso pessoal do GitHub para push seguro - uso de token npm via secrets para publicação segura Facilita releases automáticas e reduz passos manuais.
…a evitar erro 403
Codecov ReportAll modified and coverable lines are covered by tests ✅ 📢 Thoughts on this report? Let us know! |
devflowbotbr
approved these changes
Jul 24, 2025
Collaborator
devflowbotbr
left a comment
There was a problem hiding this comment.
Aprovado. Ajuste corrigido para uso correto do token no push, garantindo permissão e evitando erro 403.
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.
📝 Descrição
Corrige o uso do token no workflow de release para publicação no npm, evitando erro 403 por falta de permissão no push.
✅ Checklist
🔗 Issue relacionada (se houver)
Closes #xx