fix: allow for missing patch number in tag when deploying docs

[RobPasMue]

Following discussion on dev meeting - tags missing patch number should also be accepted for deploying stable docs since it isn't necessary to have them

[ansys-reviewer-bot]

Thanks for opening a Pull Request. If you want to perform a review write a comment saying:

@ansys-reviewer-bot review

[SMoraisAnsys]

Following discussion on dev meeting - tags missing patch number should also be accepted for deploying stable docs since it isn't necessary to have them

That might be a dumb question but why are we allowing versions that don't follow X.Y.Z template ?
Are maintainers following that approach only releasing minor releases or do they expect to also release patch releases ? If it's the latter, I'm a bit confused as of how this will end up in pypi or github releases.

[RobPasMue]

Following discussion on dev meeting - tags missing patch number should also be accepted for deploying stable docs since it isn't necessary to have them

That might be a dumb question but why are we allowing versions that don't follow X.Y.Z template ? Are maintainers following that approach only releasing minor releases or do they expect to also release patch releases ? If it's the latter, I'm a bit confused as of how this will end up in pypi or github releases.

According to our actions, we were allowing them previously. We can remove this behavior altogether as well, but there's nothing preventing a user from creating a tag "v0.8" and pushing it to PyPI without a patch number. Not ideal, but nothing preventing you from doing it either.

We can discuss this further on Thursday if you prefer.

[SMoraisAnsys]

Following discussion on dev meeting - tags missing patch number should also be accepted for deploying stable docs since it isn't necessary to have them

That might be a dumb question but why are we allowing versions that don't follow X.Y.Z template ? Are maintainers following that approach only releasing minor releases or do they expect to also release patch releases ? If it's the latter, I'm a bit confused as of how this will end up in pypi or github releases.

According to our actions, we were allowing them previously. We can remove this behavior altogether as well, but there's nothing preventing a user from creating a tag "v0.8" and pushing it to PyPI without a patch number. Not ideal, but nothing preventing you from doing it either.

We can discuss this further on Thursday if you prefer.

I don't think I'll be able to join on Thursday (I'm getting back from travel) but that's a subject that should be clarified yeah. I'd rather have no X.Y version and only X.Y.Z versions.

[SMoraisAnsys]

Taking the liberty to "block" this PR as long as the dicussion on releasing minor versions is not clarified