feat: Automatic PyPI Publishing using Tags

[PCain02]

Automatic PyPI Publishing using Tags

Description

This PR adds the ability to publish to PyPI automatically when using tags. tag_publish.yml and test-publish.yml were the main targets of the PR. The lowercase t tag will be used for test publishing and the lowercase v tag is for real publishing. They should look like t0.7.1 and v0.7.1

The commands to use this are as follows where the version number is replaced with the next sequential version.

poetry version 0.3.1
git add pyproject.toml
git commit -m "Chore: Bump version to 0.3.1"
git tag t0.3.1
git push origin t0.3.1

You will know it worked if Test PyPI has updated the version number

Note: Do not use the v tag to test the PR because that will cause a new release which is not ideal.

Linked Issues

Closes: #137

Type of Change

• Feature
• Bug fix
• Documentation

Contributors

• @PCain02

[CalebKendra]

This PR needs a secret key to work in the publish.yml file.

I lack experience in Pypi and needed to approve this. Potentially another TL could help?

[rebekahrudd]

Should we test this in your fork?

I ran into issues because I was in your fork but then I couldn't push to your fork to test it. Here's my output:

[rebekahrudd]

This worked on Linux:

[AlishChhetri]

@PCain02, please confirm that this feature works on macOS. I see you’ve tested it on Windows, and Rebekah confirmed it on Linux. We just need a macOS test to complete the cross-platform verification. The feature looks great, and I don’t see any issues with the implementation.

One question for clarification: does any instance of a v tag trigger a release to PyPI, or only when that tag is committed to the main branch? For instance, if someone on a feature branch uses a v tag, would it publish to PyPI without being merged into main?

Thank you for clarifying, and I apologize if it’s a basic question!