publish-release: gate auto-publish to bot merges on main only (release-model pilot)#255
Open
ptr727 wants to merge 2 commits into
Open
publish-release: gate auto-publish to bot merges on main only (release-model pilot)#255ptr727 wants to merge 2 commits into
ptr727 wants to merge 2 commits into
Conversation
A human PR merge no longer auto-cuts a release. The publish job runs on a push only for a bot merge (the codegen App merges every Dependabot/codegen PR, so its identity gates it); a human merge/promotion skips and the maintainer dispatches when ready. Narrow the push trigger to main so bot merges to develop don't release; develop prereleases come via dispatch. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #255 +/- ##
========================================
Coverage 99.76% 99.76%
========================================
Files 15 15
Lines 232994 232994
Branches 243 243
========================================
Hits 232450 232450
Misses 462 462
Partials 82 82 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adjusts the release automation policy in the publish-release workflow so that automatic publishes only happen from main, and only when the push is performed by specific bot identities, while keeping manual publishing via workflow_dispatch for main and develop.
Changes:
- Narrow the
pushtrigger tobranches: [main](no longer triggers ondeveloppushes). - Gate the
publishjob sopushevents only publish whengithub.actorisptr727-codegen[bot]ordependabot[bot]. - Allow
workflow_dispatchpublishes formainanddeveloponly.
Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
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
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.
Pilot of the fleet release-model change (per maintainer decision): a human PR merge never auto-cuts a release; only a bot (Dependabot/codegen) code-merge to
maindoes, plus manual dispatch.pushtrigger narrowed to[main]— bot merges todevelopno longer release;developprereleases come viaworkflow_dispatch.github.actor == 'ptr727-codegen[bot]'(the App merges every bot PR) /dependabot[bot], so a human merge/promotion tomainskips the release — the maintainer dispatches when the change is release-ready. Thepaths:filter still means an Actions-only bump publishes nothing.actor=ptr727-codegen[bot], human merges →actor=ptr727.Takes effect on
mainreleases once this promotes tomain. First repo of the rollout; the template docs (WORKFLOW.md/AGENTS.md) +PUBLISH_ON_MERGEdeletion follow.🤖 Generated with Claude Code