add smoke test for prototype namespace on release versions

[pmeier]

We use our version format as indicator for a release branch. On main we have

vision/version.txt

Line 1 in 997384c

0.17.0a0

while on a release branch this is

vision/version.txt

Line 1 in fbb4cc5

0.16.0

Meaning, we only run the check if we find a a0 after the regular semantic versioning.

This should prevent #7983 in the future.

cc @bjuncek

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/vision/7995

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

✅ No Failures

As of commit 0b6c4c6 with merge base 1a9ff0d ():
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[NicolasHug]

Thanks Philip

[pmeier]

I had another look and I'm not sure if the regex I used above is capturing everything. Our versions are all over the place:

	local	build CI	unittest CI
main	0.17.0a0+997384c	0.17.0.dev20230926+cpu	0.17.0a0+1a9ff0d
rc	0.16.0+a90e584	0.16.0+cpu	0.16.0+a90e584
release	0.15.2a0+fa99a53*	0.16.0+cpu	0.16.0+fbb4cc5

*: Not sure what happened here. But this what I get with git checkout v0.15.2 && python setup.py develop.

Since there is no rush for merging this before release, I suggest we wait after release to fill the blanks and revisit the regex.