chore(release): remove Private classifier + add PyPI Trusted Publishing workflow#4
Merged
Zer0pa-Architect-Prime merged 2 commits intomainfrom May 4, 2026
Merged
Conversation
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.
Summary
This PR removes the deliberate upload gate and wires up OIDC Trusted Publishing so the package can be released to PyPI.
Change 1 —
pyproject.tomlRemoves the single line:
This classifier was an intentional hold on public distribution. Its removal is operator-authorized (2026-05-03). No other content in
pyproject.tomlwas touched.Change 2 —
.github/workflows/publish.yml(new file)Adds a GitHub Actions workflow that fires on
v*tags and publishes the built package to PyPI using PyPI Trusted Publishing (OIDC). There are no stored credentials, API tokens, or passwords — the workflow usesid-token: writeto obtain a short-lived OIDC token that PyPI verifies against the registered Trusted Publisher slot for the package namecuneiform-control.The
environment: pypiblock matches the environment name that must be registered in the PyPI Trusted Publisher settings for this repository.What this does NOT do