fix(release): run CI on release pull requests and start new repositories at 0.1.0 - #27
Merged
Merged
Conversation
…ies at 0.1.0 Release pull requests opened with GITHUB_TOKEN start no workflows, so a ruleset with required checks blocked their merge (repokeeper-demo-dotnet#5). release-please.yml now outputs the branch of such a pull request, and the generated release.yml gains a release-pr-ci job that dispatches ci.yml on it; ci.yml accepts workflow_dispatch. Repositories seeded at 0.0.0 had a first release of 1.0.0 despite bump-minor-pre-major; their config now sets initial-version 0.1.0. The standard moves to 1.4.0.
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.
Two findings from releasing the pilot repositories on 2026-09-28.
1. Release pull requests never ran CI. release-please opens them with
GITHUB_TOKEN, and GitHub starts no workflows for that. In a repository whose ruleset requires checks, the merge stayed blocked until someone closed and reopened the PR (vannt-dev/repokeeper-demo-dotnet#5).release-please.ymlgets a new outputpr_branch: the head branch of the release PR this run opened or updated, only when notokensecret was passed (a real token starts CI by itself). The reusable job's permissions don't change, so existing@v0callers keep working.release.ymlgains arelease-pr-cijob (actions: write) that runsgh workflow run ci.yml --ref <branch>. Its check runs land on the release commit under the same names, e.g.commits / commitlint, so they satisfy required checks.ci.ymlacceptsworkflow_dispatch. The job is left out when the ci module is off.2. First releases jumped to 1.0.0. Repositories seeded at
0.0.0(demo go, kotlin, php, ruby) released 1.0.0 despitebump-minor-pre-major, because that is release-please's default first version. Their config now setsinitial-version: 0.1.0while the seed is0.0.0.The standard moves to 1.4.0; this repository is updated with
repokeeper update(ci.ymlworkflow_dispatch, release.ymlrelease-pr-ci). The README describes both.Checks: typecheck, biome, 279/279 tests (six new or changed),
repokeeper checkmatches, actionlint clean on the changed workflows.🤖 Generated with Claude Code