Skip to content

Latest commit

 

History

History
64 lines (46 loc) · 1.37 KB

MAINTAINERS.md

File metadata and controls

64 lines (46 loc) · 1.37 KB

Maintainers

When implementation is deemed to be ready for a stable release, ensure the following steps are performed:

  • Update CHANGELOG.md, replacing the development title with release version and date.
  • Ensure the version value in the implementation has been updated.

A release can be made with the following commands.


Perform a local clean build:

python -m build

Verify packages can be published:

twine check dist/*

Validate artifacts with a local pip install:

pip install dist/*.whl
cd <copied-sandbox-example>
python -m fetchdep --version
python -m fetchdep
pip uninstall fetchdep

Create a local release tag and verify the signed tag:

git tag -s -a v<version> <hash> -m "fetchdep <version>"
git verify-tag <tag>

Push the tag to GitHub to start the release workflow:

git push origin <tag>

After the release workflow creates a build, sanity check its logs to ensure the generated artifact seems sane. If the package appears to be in a good state, authorize the workflow's environment to complete publishing.

After a release is made, check the pip install with PyPI:

cd <copied-sandbox-example>
pip install fetchdep
python -m fetchdep --version
python -m fetchdep
pip uninstall fetchdep

If no issues, complete the automatically created draft release notes in GitHub to complete the release.