`mason publish` did not create a tag

[lucaferranti]

Hi there,

I'm happy to have finally submitted my first library to mason, hopefully not the last one and happy to be the guinea pig to smooth the workflow edges :)

One question, the documentation instructions don't mention to manually create a tag when using mason publish, as such I assumed this would be done automatically, but it does not seem the case (repo link).

Do I need to make the release manually? Or should that be handled by mason publish ?

[lucaferranti]

gentle bump

I just made a new release of ForwardModeAD and the instructions in the documentation

mason publish Steps:
Write a library or binary package in chapel using mason

Host the package in a git repository. (e.g. GitHub)

Fork the mason-registry on GitHub

Ensure your package has a remote origin.

Run mason publish in your package

Go to the link provided to open a pull request to the mason registry.

Wait for mason-registry maintainers to approve PR.

Manual Steps:
Write a library or binary package in chapel using mason

Host that package in a git repository. (e.g. GitHub)

Create a tag of your package that corresponds to the version number prefixed with a ‘v’. (e.g. v0.1.0)

Fork the mason-registry on GitHub

Create a branch of the mason-registry and add your package’s Mason.toml under Bricks/<package_name>/<version>.toml

Add a source field to your <version>.toml pointing to your package’s repository.

Open a PR in the mason-registry for your newly created branch containing just your <version>.toml.

Wait for mason-registry maintainers to approve the PR.

are not clear to me. I understand the instructions above as I don't have to manually create the tag if I use mason publish, however it seems this is not the case, since running mason publish does not create the tag.

Do I need to create the tag manually also if I run mason publish?