Repository navigation
ci: release automatically when a CHANGELOG version is merged - #30
Merged
Merged
Conversation
The release workflow could only be started manually, and the integration used for automated maintenance cannot dispatch workflows. Releasing now happens on push to main: when the newest CHANGELOG version has no tag, the workflow runs the full release (quality, tag, GitHub release, npm); when it is tagged but its Studio package versions are missing from npm, it only publishes them; otherwise it does nothing. Manual dispatch with dry_run is kept for previews and recovery.
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.
Follow-up to #29. The integration used for automated maintenance cannot dispatch workflows:
workflow_dispatchreturns 403 "Resource not accessible by integration". So a release could not finish without someone pressing Run workflow. With this change, merging the release PR is enough.Behavior on push to
mainA
preparejob reads the newest## [X.Y.Z]section ofCHANGELOG.md([Unreleased]is ignored) and plans one of three actions:vX.Y.Ztag missingmainare missing from npmpreparejob takes a few seconds and every other job is skipped.Manual dispatch keeps the same inputs (
version,target,dry_run) for previews and recovery. The later jobs now read the plan fromprepareinstead of the dispatch inputs.Validation
actionlintreports no issues.main(v3.4.0 tagged, Studio 0.2.0 not on npm) planstarget=npm.## [3.4.1]section without a tag planstarget=all.target=none.CONTRIBUTING.md→ Releasing now describes the merge-driven flow.Note for merging
Merging this PR triggers the
target=npmcase for v3.4.0, which publishes@rendis/statepro-studio-react@0.2.0and@rendis/statepro-studio-web-component@0.2.0. That only works once both packages have the npm Trusted Publisher configured (rendis/statepro/release.yml). Without it, the publish step fails with an authentication error and nothing is published.