Re: [AUH][PATCH v2 6/9] upgrade-helper.py: Add minor option for minor version upgrades

On Mon, 27 Apr 2026 at 14:30, Daniel Turull <[email protected]> wrote:
> That said, adding recipe variables to already-released branches (scarthgap) means backporting metadata changes. The CLI flags work today without touching any recipes, which is why I started there.
>
> Would you prefer I rework this as a recipe variable for the next version, or keep the CLI flags as a first step? I mean only one option (--stable) that can read AUH_UPGRADE_POLICY if present otherwise default to patch?

Please see my comment to 5/9 for additional thoughts on this. The
major point I need to stress is that the correct long term
maintainable thing is to extend existing oe-core mechanisms, even when
such changes are difficult to backport.

Specifically:

- the version check functionality in meta/lib/oe/recipeutils.py should
be extended to support checking for latest minor and point releases,
and possibly other ways to provide stable updates (e.g. commits in a
branch, or a custom regex for e.g. openssh's 10.1p3 schema).

- 'devtool check-upgrade-status --stable' or 'devtool latest-version
--stable' would return a list of what could be updated based on recipe
metadata (e.g. UPSTREAM_STABLE_RELEASES = "point" in some recipe would
make devtool query recipeutils for latest point release within the
same minor release)

- then AUH would simply use these mechanisms to do stable updates,
when it's run with --stable argument. It would be a trivial change; it
wouldn't need to know or care about how to pick the correct version,
just call a different function to obtain maintenance releases instead
of latest releases.

Alex