Website, application and provider contracts evolve independently
The public site has its own version. Commerce application code, database migrations and provider contracts are implementation-specific streams and should not be collapsed into one number.
The published website overlay release
STABLE
Public website overlay
Current packaged and validated website release.
8.0.0Automation can read the public release model
Use release-channels.v9.json, version.json and the release manifest. They intentionally contain no live application credentials or private provider configuration.
Do not infer application compatibility from the website number
Use the Compatibility Center and implementation-owned release records for the commerce runtime itself.