Documentation releases now follow the new unified versioning scheme for our software releases rather than following the ValidMind Library version, starting with this 25.01 release.

Why change the versioning scheme?

We maintain multiple repositories, each with its own version tags. With the new versioning scheme, we can now provide a single unified release version, such as 25.01, that represents a collection of releases from these individual repositories. This ensures consistency and makes it easier to track and reference all changes associated with a specific release. Each unified version corresponds to updates across several repositories, simplifying version management for you.

This change does not affect how frequently new releases occur (release cadence) or the process you follow to upgrade. Only the versioning scheme for documentation has been updated. Everything else stays the same.

What's Changed

• Docs quick audit — ValidMind Library by @validbeck in #593
• Add Docker image for our docs site by @nrichers in #594
• Cleaned up Developer Fundamentals & other training by @validbeck in #599
• Delete test-results directory by @nrichers in #600
• Release notes — December 24, 2024 by @validbeck in #596
• Edited release script & notebook by @validbeck in #607
• Cleanup of 2024 releases + new cleanup notebook/script by @validbeck in #610
• Missing footnote from FAQ by @validbeck in #613
• Pulling in latest changes from validmind-library PR#282 by @validbeck in #615
• Add make execute PROFILE=exe-prod to docs-site action by @nrichers in #598
• Docs — Customize model overview page by @validbeck in #622
• Updated docs — Workflows by @validbeck in #620
• QoL improvements to release notes script/notebooks by @validbeck in #626
• Added instructions for Wait steps in workflows by @validbeck in #628
• Updated mathematical formula support for content blocks by @validbeck in #631

Full Changelog: v2.6.7...25.01