ci: release on push to main, matching openadapt-privacy - #9
Draft
abrichr wants to merge 1 commit into
Draft
Conversation
The GH006 repair (ADMIN_TOKEN) is kept. The trigger goes back to push. Dispatch-only was adopted on the reasoning that merging would publish a release whose only content was a CI-config change. That is a commit-message choice, not a property of the trigger: this package's [tool.semantic_release.commit_parser_options] sets minor_tags = ["feat"] and patch_tags = ["fix", "perf"], so ci/chore/docs/build/refactor/style/test commits publish nothing and the run exits green reporting no release. openadapt-privacy is the control: four chore/docs commits since v1.0.0, four green push-triggered release runs, PyPI still 1.0.0. Dispatch-only also leaves this repository's release badge stuck on its last failure and makes it behave unlike its siblings, which is the drift that hid the five-month GH006 failure in the first place. This commit is deliberately typed `ci:` so it cannot itself cause a release. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NyCHrzA1psrKMFfroYbzaM
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.
What this changes
One line of substance: the release trigger goes from
workflow_dispatchback topush: branches: [main]. The GH006 repair (secrets.ADMIN_TOKEN) is keptexactly as-is. The result is byte-for-byte the same shape as
openadapt-privacy, which had the identical failure on 2026-02-18, wasrepaired on 2026-07-15, stayed push-triggered, and has been green since.
Why the stated reason for dispatch-only does not hold
Dispatch-only was chosen so that merging would not "publish a version whose sole
content is a version bump". Whether a merge releases is decided by the commit
message, not by the trigger. This package's
pyproject.tomlsays:Only
feat,fixandperfmove a version. Aci:orchore:merge runs theworkflow, reports no release, and exits green.
openadapt-privacyis thecontrol: 4
chore:/docs:commits sincev1.0.0, 4 green push-triggeredrelease runs, PyPI still on 1.0.0.
Cost of dispatch-only
README.mdstill reads "Release and PyPI Publish -failing" right now, and dispatch-only means no future push ever replaces it.
GH006 failure sit unseen from 2026-02-18 to 2026-07-27.
DRAFT — merging this publishes v0.1.3
Not a defect in this PR; a consequence of the commits already on
main.python-semantic-release considers everything since
v0.1.2:2e9859efix: bound ruff to 0.16.x and fix the defects its expanded defaults found (fix: bound ruff to 0.16.x and fix the defects its expanded defaults found #8)494b8fffix(ci): release through protected main via explicit dispatch (fix(ci): release through protected main via explicit dispatch #7)b27487achore: gitignore .private/ (chore: gitignore .private/ #6)a5958c4docs: refresh README to shared OpenAdapt house style (docs: refresh README to shared OpenAdapt house style #5)41ce4d4docs: add lifecycle status banner pointing to openadapt-flow (docs: add Research status banner (not required by the product) #4)677a146fix(ci): use v9 branch config for python-semantic-release (fix(ci): use v9 branch config for python-semantic-release #3)Those
fix:commits are version-bumping, so the first push-triggered run afterthis merges will publish v0.1.3 to PyPI and GitHub Releases. That is
legitimate unreleased work, but it is a release, so this PR stays a draft until
a human says go.
This PR's own commit is typed
ci:and cannot cause a release by itself.🤖 Generated with Claude Code
https://claude.ai/code/session_01NyCHrzA1psrKMFfroYbzaM