Include the latest MontePy release on montepy.org

[tjlaboss]

Description

• Rename "release" -> "version"
• Display version under the logo on the website

Fixes #544

Checklist

• [x] I have performed a self-review of my own code
• [x] I have made corresponding changes to the documentation
• [ ] I have added tests that prove my fix is effective or that my feature works (if applicable)

Discussion

As of 08ded2fcf4ec77bcb3c3d06bea7c40e1596b0995, this displays the latest build. Is that better / more correct?

If not: how should we make it display the most recent release?

[MicahGale]

You need to make sure that setuptools_scm gets properly triggered before building which I think is already done in the build process.

[tjlaboss]

setuptools_scm gets the maj.min.patch.dev+commit number. Right now, it's 0.4.1.dev119+g494ef24f.

So basically I'm wondering:

• Should we display that version on the website, instead of latest release?
  • Pros: It ensures that the version number corresponds to the latest documentation on develop.
  • Cons: It's kind of ugly, and I think people reading the docs are more likely to want the latest release.
• If not, and we display just the release, instead of the latest version:
  • Should we just strip the dev/local parts like: '.'.join('0.4.1.dev117+g8329afe6'.split('.')[:3])?
  • Or is it better to do python -m setuptools_scm --strip-dev?

[MicahGale]

Versioning is based on tags. Try locally doing something like git tag v0.4.2 delete any local montepy/_version.py and rebuild. It should look good at that point I think.

[MicahGale]

Also as part of the release process there's a check for a full release version. a .dev version will cause pipeline failure, and so the website should never deploy with a dev version.

[tjlaboss]

I see: the website shall only deploy at release time.

[MicahGale]

I see what release is doing: https://www.sphinx-doc.org/en/master/usage/configuration.html#confval-release