ci(release)!: unify release+publish with the rest of the ecosystem#25
Merged
ci(release)!: unify release+publish with the rest of the ecosystem#25
Conversation
- Move semantic-release para _release.yml reusável (guard de packages_changed + GitHub App token), chamado por ci.yml após o job `checks` - Adicionar _publish.yml pinado ao release_sha, com checagem idempotente por pacote e provenance - Remover publishCmd inline do .releaserc.cjs (agora .github/ workflows/_publish.yml é o responsável por publicar) - Remover release.yml standalone (cron semanal era no-op) e a entrada correspondente em templates.manifest.yml Resolve o CI rodando checks e release em paralelo no push para main.
Automated Review — Round 1SummaryThe PR introduces new workflow files for publishing packages and managing releases using semantic-release. However, there are potential issues with error handling and npm authentication that need to be addressed to ensure robustness and security. Changes
🔍 Found 3 suggestions (see inline comments) Reviewed by OpenAI gpt-4o-mini (fallback) | 5,437 in / 213 out | $0.0009 — Round 1 of 2 |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
rlueder
added a commit
that referenced
this pull request
Apr 24, 2026
- Move semantic-release para _release.yml reusável (guard de packages_changed + GitHub App token), chamado por ci.yml após o job `checks` - Adicionar _publish.yml pinado ao release_sha, com checagem idempotente por pacote e provenance - Remover publishCmd inline do .releaserc.cjs (agora .github/ workflows/_publish.yml é o responsável por publicar) - Remover release.yml standalone (cron semanal era no-op) e a entrada correspondente em templates.manifest.yml Resolve o CI rodando checks e release em paralelo no push para main.
precisa-saude-release-bot Bot
pushed a commit
that referenced
this pull request
Apr 24, 2026
## [1.6.1](v1.6.0...v1.6.1) (2026-04-24) ### ⚠ BREAKING CHANGES * **release:** unify release+publish with the rest of the ecosystem (#25) ### Bug Fixes * **cli:** nota sobre higiene de templates no copy-templates ([131eb43](131eb43)) * **templates:** usar contexto do repo atual no pr-review-responder ([c1dde13](c1dde13)) ### CI/CD * **release:** unify release+publish with the rest of the ecosystem ([#25](#25)) ([55942e3](55942e3))
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
1 participant
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.
Summary
ci.ymlpassa a orquestrarchecks→release→publish(mesma forma de datasus-brasil / fhir-brasil / medbench-brasil / platform). Resolve o CI rodando checks e semantic-release em paralelo no push paramain._release.ymlreusável (cópia canônica: guard depackages_changed, GitHub App token para tag/commit, outputsreleased/version/release_sha) e_publish.ymlreusável (pinado aorelease_sha, checagem idempotente vianpm view,--provenance)..releaserc.cjsdeixa de publicar inline — opnpm publishagora roda em_publish.ymlcontra o SHA do commit de release.release.ymlstandalone removido (o cron semanal era no-op porque docs/ci/chore não promovem release) junto com a entrada notemplates.manifest.yml.Operational note
_release.ymlusasecrets.RELEASE_APP_ID/RELEASE_APP_PRIVATE_KEY(mesma GitHub App já usada pelos outros quatro repos). Confirmar que os secrets estão herdados no nível de org antes do merge.Breaking change
Marcado como
!porque muda o caminho de publicação (quem publica passa de semantic-release emrelease.ymlpara_publish.ymlchamado porci.yml). Nenhuma mudança de API nos pacotes publicados.Test plan
main→CI/CDdispara,checksroda primeiro,releasesó começa apóscheckspassarreleasedetecta mudança empackages/**e roda semantic-release, criando ochore(release)commit + tagpublishroda depois, comif: needs.release.outputs.released == 'true', e publica os 9 pacotes com provenancepackages/**) faz oreleasepular (guardpackages_changed)