ci: automate tagged package releases - #14
Merged
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.
Closes #7
Summary
Prepare AliasingAtlas for repeatable, versioned public releases through GitHub Actions.
Changes
v*.*.*tags.project.versioninpyproject.toml.twine check.RELEASING.mdwith one-time PyPI setup and maintainer checklist.Required Repository Setup
Before the first publish:
aliasing-atlasproject on PyPI.BoussettaNyquistNavigatorrelease.ymlpypipypienvironment in GitHub repository settings.Until this one-time setup is complete, the workflow will build and validate artifacts but publishing will fail at the publish step.
Validation
pytest -q: 38 passedCommits
This PR intentionally contains focused commits:
787e63bci: automate tagged package releases5408164docs: add release checklist and PyPI setupc13c914docs: document automated release status1643d23docs: record release automationThe generated
.coveragefile is local and not included.