feat(ci): adopt release-please for automated releases#74
Merged
Conversation
Why: framework publishes 14 modules from one repo, all version-locked to a single git tag, but releases and tags are cut manually with no changelog or automated bump. What: add the shared reusable-release.yml@v1 workflow plus a single-package release-please config and manifest baselined at the current release (0.3.16). On merge of the release PR, release-please creates the GitHub release, which triggers the existing publish.yml (release: published) to publish all 14 packages at that tag. No extra-files: package versions come from the release tag, so the many nested _index.yaml files are left untouched. publish is disabled in the reusable workflow since publish.yml already handles it.
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.
Why
frameworkpublishes 14 modules from one repo (actor,agent,bootloader, …), all version-locked to a single git tag, but releases/tags are cut manually — no changelog, no automated bump.What
wippyai/template-module/.github/workflows/reusable-release.yml@v1(publish: false—publish.ymlalready publishes).release-please-config.json(release-type: simple) +.release-please-manifest.jsonbaselined at the current release0.3.16.extra-files: all 14 packages take their version from the release tag, so the nested_index.yamlfiles are left untouched (zero churn, zero risk to publishing).Flow (unchanged publish behavior)
Push to
master→ release-please opens a release PR → on merge it creates the GitHub Release → the existingpublish.yml(release: published) publishes all 14 packages at that tag.Testing
No visual changes.