chore(ci): remove vestigial release.yml workflow#608
Merged
Conversation
The Release workflow (publish-on-tag) has zero runs since the repo was created — release-please.yml has been doing the build + twine upload inline since v4.4.x. Confirmed via the GitHub Actions API: workflow 204577101 has an empty workflow_runs array, while v4.4.1 through v4.6.0 all landed on PyPI through the release-please.yml path. Removing the dead file so future contributors don't waste time wiring secrets into a workflow that never fires. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.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
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.
Summary
`.github/workflows/release.yml` triggers on `push: tags: v*` and was intended to handle PyPI publishing on each release. It has zero runs ever — every release since v4.4.1 (including today's v4.6.0) has been published by `release-please.yml`'s inline build + twine upload step. The standalone workflow is dead code.
Verified via the Actions API:
```
$ gh api repos/adcontextprotocol/adcp-client-python/actions/workflows/204577101/runs --jq '.workflow_runs | length'
0
```
```
$ curl -s https://pypi.org/pypi/adcp/json | jq '.releases | keys[-5:]'
["4.4.1","4.4.2","4.4.3","4.5.0","4.6.0"]
```
(Reason it never fires: GitHub's anti-loop protection — when release-please pushes a tag using the default `GITHUB_TOKEN`, downstream tag-triggered workflows are suppressed.)
Test plan
🤖 Generated with Claude Code