Skip to content

Latest commit

 

History

History
29 lines (22 loc) · 908 Bytes

File metadata and controls

29 lines (22 loc) · 908 Bytes

Maintaining nixnet

Cutting a release

Update the version

  1. pyproject.toml
  2. README.rst
  3. Create release notes (clog-cli can help)
  4. git clean -ndx to see what files to clean up
  5. git clean -fdx to clean up files
  6. Include release notes in commit messaage
  7. Publish a PR

Tagging a release

  1. (on main) git tag -a v<X>.<Y>.<Z> with the release notes as the message
  2. git push <UPSTREAM> main --tag v<X>.<Y>.<Z>
  3. Go to https://github.com/ni/nixnet-python/releases
  4. The new release should be there, but it will be poorly formatted.
  5. Draft a new release. Use the same tag version. You don't need to attach any new files.

Uploading packages to PyPI

  1. poetry config pypi-token.pypi <PyPI API token> (only need to be done once)
  2. rm -Rf dist
  3. poetry publish --build