Repository navigation
chore(ci): remove release-please workflow (releases run via maintainer CLI) - #539
Merged
Seth Juarez (sethjuarez) merged 1 commit intoSep 10, 2026
Merged
Conversation
…r CLI The microsoft org blocks the Actions GITHUB_TOKEN from opening pull requests, and an org member cannot install a GitHub App on the org, so release-please cannot run in CI here. Releases are instead cut by running the release-please CLI under a maintainer's own identity (which the org permits) to open the Release PR; the existing tag-triggered OIDC publisher handles PyPI once the maintainer tags the merge. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
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.
Why
The
microsoftorg blocks the ActionsGITHUB_TOKENfrom creating pull requests, and an org member cannot install a GitHub App on the org. Sorelease-pleasecan't run in CI here — the workflow could only ever 403 when opening the Release PR, failing on every push tomain.What changed
Removes
.github/workflows/release-please.yml. The release-please config (release-please-config.json,.release-please-manifest.json) stays — it's still the source of truth.New release flow (credential-free)
Releases are cut by running the release-please CLI under a maintainer's own identity (which the org permits — it's a real user, not the Actions token):
release-please manifest-pr→ opens the Release PR as the maintainer.release-please manifest-release(orgh release create python/X.Y.Z) tags the merge as the maintainer — a real-user tag push, so the existingprompty-python.ymlpublisher fires and publishes to PyPI via OIDC.No GitHub App, no PAT, no org-owner approval, and no reliance on the Actions token for PR creation or tag-triggered publishing.
This is the mechanism already in use for the first Python 2.0.0 release (#538).
Co-authored-by: Copilot App 223556219+Copilot@users.noreply.github.com