docs(release): remove stale pypi deployment + warn against recreating it - #3
Merged
Merged
Conversation
…0.2.1 The repo-level `pypi` GitHub Environment and two stale `pypi` Deployment records (ids 5525144710, 5365996483) were removed from the tt-atom repo on 2026-07-21. They were leftover from before the release workflow dropped PyPI: tags v0.1.0/v0.2.0/v0.2.1 have an older `.github/workflows/release.yml` baked into their commits with a dead `pypi-publish` job, so re-pushing those tags re-triggers a permanently-failing run and re-creates the stale deployment in the repo's Environments/Deployments UI. No package was ever published to PyPI (pypi.org/pypi/tt-atom/json returns 404). Add a maintainer note to RELEASING.md's Distribution section and a short pointer in release.yaml so future maintainers don't recreate the environment or rewrite those tags.
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
pypiGitHub Environment and two stalepypi-environment Deployment records (ids 5525144710, 5365996483) from the tt-atom repo. These were leftover from before the release workflow dropped PyPI; they showed up as failed deployments in the repo's Environments/Deployments UI.v0.1.0/v0.2.0/v0.2.1have an older.github/workflows/release.ymlbaked into their commits with a deadpypi-publishjob (Trusted Publishing never configured). Re-pushing those tags re-triggers the permanently-failing run and re-creates the stale deployment. Added a maintainer note toRELEASING.mdand a pointer inrelease.yamlso this isn't reintroduced.https://pypi.org/pypi/tt-atom/jsonreturns 404). Pure repo/CI hygiene — no code, no model, no accuracy/perf surface.Verification
gh api repos/moritztng/tt-atom/environments→[](pypi env gone)gh api repos/moritztng/tt-atom/deployments→ count 0 (both stale records gone)grep -ri pypi .github/workflows/release.yaml→ only explanatory NOTE comments, no job/stepMade with Cursor