feat(ci): adopt release-please for automated releases#2
Merged
Conversation
Why: web-components publishes 4 modules (mermaid, markdown, chartjs, voice) but has never been released (no tags, no releases) and has no changelog or automated versioning. What: add the shared reusable-release.yml@v1 workflow plus a single-package release-please config. Since the repo has never been released, bootstrap-sha pins the changelog start and release-as forces the first release to 0.1.0. On merge of the release PR, release-please creates the GitHub release, which triggers the existing publish.yml (release: published) to publish all 4 packages at that tag. release-as should be dropped after 0.1.0 ships so normal semver bumping resumes.
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
web-componentspublishes 4 modules (mermaid,markdown,chartjs,voice) but has never been released — no tags, no releases, no changelog, no automated versioning.What
Mirror the
frameworkmonorepo setup (single shared version across packages, published on release):wippyai/template-module/.github/workflows/reusable-release.yml@v1(publish: false—publish.ymlalready publishes onrelease: published).release-please-config.json+.release-please-manifest.json.bootstrap-shapins the changelog start, andrelease-as: "0.1.0"forces the first release to v0.1.0.Flow
Push to
main→ release-please opens a release PR → on merge it creates the GitHub Releasev0.1.0→ the existingpublish.ymlpublishes all 4 packages at that tag.Follow-up
release-asis sticky — drop it after v0.1.0 ships so normal semver bumping resumes. Happy to send that one-line follow-up once 0.1.0 is out.No visual changes.