[codex] Add package release workflow#446
Merged
jayscambler merged 2 commits intomainfrom Mar 17, 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 adds a dedicated GitHub Actions release workflow for publishing the Python and npm packages through the existing
releaseenvironment.Today the repo has CI coverage and a configured
releaseenvironment, but no workflow that actually builds, validates, and publishes package artifacts. That leaves package publication as a manual local process even though the repository already has release-environment approval configured.What This Adds
The new workflow is manual (
workflow_dispatch) and supports releasing from a chosen ref. It validates artifacts before any publish step runs, then gates the actual publish jobs behindenvironment: releaseso the existing reviewer approval remains the final control point.The workflow does the following:
autocontext/autoctx --helpts/README.mdanddist/index.jsPYPI_API_TOKENNPM_TOKENWhy This Matters
This closes the gap between having release credentials/environment protections configured and actually being able to use them. It also makes package publication reproducible and reviewable instead of relying on an ad hoc local release flow.
Validation
I validated the workflow structure locally and also separately validated the release artifacts from
main:0.2.1builds successfully withuv buildautoctx --helprunsREADME.mdand builtdist/output