New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(core): consistent template versioning #2763
Conversation
639d1ab
to
94d25dc
Compare
94d25dc
to
9c784ad
Compare
|
||
latest_reference, latest_version = latest | ||
update_available = latest_reference != reference or latest_version != version | ||
return update_available, latest_reference |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This would mean that if I install hypothetical version 1.3.0 and migrate, and then install hypothetical version 1.2.0 and run migration check, it'd say a new version is available and downgrade, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, EmbeddedTemplates::get_latest_reference_and_version
checks if project's template version is newer than renku's template version and returns the latest of the two, so, 1.3.0
will be the latest version/reference in that case and nothing will be changed.
Description
Use template repository's tag as version (instead of the Renku version) for templates bundled with Renku CLI.
Fixes #2714