Version in pyproject.toml is still 6.0.0

[s-t-e-v-e-n-k]

The version field in pyproject.toml is still set to 6.0.0, which doesn't match the version number either in the GitHub release or on PyPi.

[mjbear]

The version field in pyproject.toml is still set to 6.0.0, which doesn't match the version number either in the GitHub release or on PyPi.

True enough.

ntc-templates/pyproject.toml

Line 3 in 784e3fa

version = "6.0.0"

I have some thoughts on how a check for the version could be added to the GitHub Actions CI/CD process.
(I'm not sure we want to auto-update/edit the pyproject.toml file via GH Actions, but I could look into that too.)

I'm a volunteer, so if the maintainers have further feedback/thoughts I'm game for a discussion. 😀

[s-t-e-v-e-n-k]

We probably don't need to -- there are plugins for poetry that will take the version number from a file or something like that instead of hardcoding it and having to edit it.

[mjbear]

Releases are created in GitHub so using that workflow to update the pyproject.toml file could be ideal.

I'll continue to look into this as I have time. Thank you!

[mjbear]

Releases are created in GitHub so using that workflow to update the pyproject.toml file could be ideal.

I'll continue to look into this as I have time. Thank you!

I have a possible solution for this that I need to run by the ntc-templates maintainers. ✨ 🪄
Maybe I spoke too soon 😐

Update:
My thoughts are to auto-bump the version based on the GH Release.
So far everything I've found online as inspiration has been based on pull requests which is not what we'd want.

What I've found thus far is that it seems once the release event is triggered as created we likely can't interject changes to the content.

• https://github.com/callowayproject/bump-my-version
• Set the version on pyproject.toml automatically scanapi/scanapi#47
• https://github.com/bulv1ne/poetry-bumpversion
• https://github.com/orgs/community/discussions/25234
• https://github.com/orgs/community/discussions/26842
• https://www.reddit.com/r/github/comments/184brmg/best_way_to_update_version_strings_in_code_as/?rdt=56555

[mjbear]

Update:
It also doesn't seem that we can hook in prior to tag creation either.
I suppose a check could be made on push or PR event (though I don't like that option), because I wouldn't want to burden contributors with is the innards of the pyproject.toml file.

Maybe this is something that just needs handled as manual release steps. Thoughts?
@jmcgill298 @jvanderaa @itdependsnetworks