website: Add missing release info files for the last few releases and handle CalVer properly#4367
Conversation
Files were created by running the following:
$ ./content/en/docs/started/installing-kubeflow/get_new_releases.sh
This fixes the build failure in kubeflow#4366.
Signed-off-by: Christian Heusel <christian@heusel.eu>
christian-heusel
changed the title
The `latest.json` now uses a CalVer tag ("26.03") without a "v" prefix
and only two version components, which broke the shortcode's semver
assumptions. Add explicit if/else branches for semver vs CalVer when
extracting major/minor integers and resolving the release-info JSON
path.
Assisted-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Signed-off-by: Christian Heusel <christian@heusel.eu>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Comparing a semver minor (e.g. 10 from v1.10.0) against a CalVer month (e.g. 3 from 26.03) produced a nonsensical negative lag. Now detects scheme per release: CalVer uses month-based lag, semver uses minor-based lag, and mixed schemes show a "legacy semver release" message instead of a meaningless number. Assisted-By: Claude Sonnet 4.6 <noreply@anthropic.com> Signed-off-by: Christian Heusel <christian@heusel.eu>
christian-heusel
force-pushed
the
chore/add-latest-releases-info-files
branch
from
f442552 to
7229f0c
Compare
christian-heusel
changed the title
thesuperzapper
left a comment
thesuperzapper
left a comment
There was a problem hiding this comment.
We discussed this a bit on a call just noting down what we said.
Personally, I think we should just remove the version lag calculation entirely as its not that helpful anymore with the new cal versions. We can probably simply remove the "and is xxx minor versions from the latest", and if distribution has not yet updated to a version of Kubeflow with cal-versioning just warn the user about that.
2 participants
Description of Changes
Files were created by running the following:
This fixes the build failure in #4366.
Checklist
Screenshots
cc @dominikkawka @tarekabouzeid regarding the 26.03 release