Skip to content

Conversation

mdellweg
Copy link
Member

@mdellweg mdellweg commented May 5, 2025

The upgrade strategy when the dependecy on core is newer than any supported branch, should be to just wait until eventually one of the newer branches is declared supported. If we keep upgrading the dependency aggressively, we will likely miss the window to relax on a later supported branch.

The upgrade strategy when the dependecy on core is newer than any
supported branch, should be to just wait until eventually one of the
newer branches is declared supported. If we keep upgrading the
dependency aggressively, we will likely miss the window to relax on a
later supported branch.
updated, new_requirement = scan_requirement(requirement, supported_versions)
if updated:
new_requirement = scan_requirement(requirement, supported_versions)
if new_requirement is not None:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍


core_template = yaml.safe_load(request.content)
supported_versions = {parse(v) for v in core_template["supported_release_branches"]}
latest = core_template["latest_release_branch"]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

and this is the key that will keep us from updating to latest-released over and over until a new supported is added. got it.

@mdellweg mdellweg merged commit 17d3795 into pulp:main May 5, 2025
11 checks passed
@mdellweg mdellweg deleted the core_update_policy branch May 5, 2025 13:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants