Mark recipes whose point releases are fixes-only (1/3)
cover Mark recipes whose point releases are fixes-only (1/3)
From: Daniel Turull <[email protected]>
First of three series opting recipes into UPSTREAM_STABLE_RELEASE_REGEX. This one covers the recipes whose upstream publishes a written stable-branch policy, so qualification can be checked against a document rather than inferred. Later series cover recipes qualifying on branch structure and changelog evidence, and a smaller tail with weaker evidence.
Why:
The Auto Upgrade Helper's --stable mode proposes upgrades only within a stable point-release series, so it can be run against a stable branch without pulling in feature releases. It needs to know, per recipe, which upstream versions count as a point release, and that is upstream-specific:
for some projects the series is the major, for others major.minor, for others a suffix that is not dot-separated at all.
https://docs.yoctoproject.org/dev/ref-manual/release-process.html#stable-point-release-upgrades
Method:
Each recipe needed two things: a mechanism that can express its series, and evidence that point releases in that series carry only fixes.
Screened out before any reading: version schemes that cannot express a point release, development series (whose point releases are not fixes-only), abandoned lines, and projects with no per-series branch or other bugfix-only marker.
Evidence required for the rest:
- a written upstream policy where one exists, cited by file and line at a pinned tag;
- the changelog for two to three point releases, including at least one that is not the newest, with section headings enumerated before any prose is read;
- ABI signal where the project provides one, such as libtool version-info or a soname;
- what the OE stable branches have actually done since forking.
A new command-line option, a new configuration option, or a changed documented default in a point release is disqualifying. An additive API symbol may be acceptable but is disclosed in the commit message rather than glossed. Each commit message states what the point releases actually contain, so the reasoning can be checked rather than taken on trust.
Disclaimer:
Produced with AI assistance, which did the screening, the changelog reading and the drafting. I have reviewed each recipe myself: the qualification decision, the evidence cited, and the resulting regex. Errors are mine.
Daniel
Daniel Turull (7):
util-linux: inherit upstream-stable-release-point
systemd: inherit upstream-stable-release-point glib-2.0: inherit upstream-stable-release-point
dbus: inherit upstream-stable-release-point
xz: inherit upstream-stable-release-point
git: inherit upstream-stable-release-point
perl: inherit upstream-stable-release-point
meta/recipes-core/dbus/dbus_1.16.2.bb | 6 ++++++ meta/recipes-core/glib-2.0/glib.inc | 4 +++- meta/recipes-core/systemd/systemd.inc | 5 +++++ meta/recipes-core/util-linux/util-linux.inc | 4 ++++ meta/recipes-devtools/git/git_2.55.0.bb | 4 ++++ meta/recipes-devtools/perl/perl_5.44.0.bb | 2 +- meta/recipes-extended/xz/xz_5.8.3.bb | 4 ++++ 7 files changed, 27 insertions(+), 2 deletions(-)
PATCH 1/7 util-linux: inherit upstream-stable-release-point
From: Daniel Turull <[email protected]>
util-linux's README ("Stable Branches") documents stable/v<major>.<minor> branches whose maintenance releases are bug fixes only, so upgrades within a major.minor are stable point upgrades per the OE-Core stable release policy (ref-manual, "Stable Point Release Upgrades").
https://docs.yoctoproject.org/dev/ref-manual/release-process.html#stable-point-release-upgrades
https://github.com/util-linux/util-linux/blob/v2.42.2/README#L95
Checked the last point release for feature creep:
2.42.2 (Jun 16 2026), against 2.42.1 (May 18 2026): 32 commits, all fixes or hardening -- memory safety (a libblkid use-after-free, two buffer overflows, a libfdisk GPT fix), privilege tightening (X-mount.subdir restricted for non-root), diagnostics (fanotify queue overflow detection) and documentation. No new options or behaviour.
These releases are not picked up on the OE stable branches: util-linux has had zero point-release bumps on kirkstone, scarthgap or wrynose since each branch forked from master, leaving them at 2.37.4, 2.39.3 and 2.41.3 respectively. This addresses that gap going forward.
This addresses the general case on master, where PV is 2.42.x. Since the regex is derived from PV, an older branch scopes it to that branch's series, and the 2.39 series scarthgap ships does not qualify. 2.39 adopted the new kernel mount API, so 2.39.1 introduced LIBMOUNT_FORCE_MOUNT2={always,never,auto} as, in its own words, "a stable workaround for use cases where new kernel API is not ready to use"; the series also took new CPU model support and libblkid bcachefs sub-device label probing. That is a property of the 2.39 series rather than of the project -- 2.42.2 is 32 commits of pure fixes -- but it means this must not be backported unchanged, and each branch's series needs checking on its own. For the avoidance of doubt it is not a development-series effect either:
util-linux has no development/stable version split, and pre-release work goes to -rc tags.
AI-Generated: Kiro with Claude Opus 5
--- meta/recipes-core/util-linux/util-linux.inc | 4 ++++ 1 file changed, 4 insertions(+)
meta/recipes-core/util-linux/util-linux.inc +4 -0
@@ -22,3 +22,7 @@ SRC_URI = "${KERNELORG_MIRROR}/linux/utils/util-linux/v${MAJOR_VERSION}/util-lin SRC_URI[sha256sum] = "03a05d3adf9602ef128f2da05b84b3205ce60c351e5737c0370f74000679ce8a" CVE_PRODUCT = "util-linux" + +# util-linux publishes bugfix/security-only point releases on its +# stable/v<major.minor> branches. +inherit upstream-stable-release-point
Re: [PATCH 1/7] util-linux: inherit upstream-stable-release-point
Quoted 37 lines · On Fri, 2026-07-31 at 14:25 +0200, [email protected] wrote:
From: Daniel Turull <[email protected]>
util-linux's README ("Stable Branches") documents stable/v<major>.<minor> branches whose maintenance releases are bug fixes only, so upgrades within a major.minor are stable point upgrades per the OE-Core stable release policy (ref-manual, "Stable Point Release Upgrades").
https://docs.yoctoproject.org/dev/ref-manual/release-process.html#stable-point-release-upgrades
https://github.com/util-linux/util-linux/blob/v2.42.2/README#L95Checked the last point release for feature creep:
2.42.2 (Jun 16 2026), against 2.42.1 (May 18 2026): 32 commits, all fixes or hardening -- memory safety (a libblkid use-after-free, two buffer overflows, a libfdisk GPT fix), privilege tightening (X-mount.subdir restricted for non-root), diagnostics (fanotify queue overflow detection) and documentation. No new options or behaviour.
These releases are not picked up on the OE stable branches: util-linux has had zero point-release bumps on kirkstone, scarthgap or wrynose since each branch forked from master, leaving them at 2.37.4, 2.39.3 and 2.41.3 respectively. This addresses that gap going forward.
This addresses the general case on master, where PV is 2.42.x. Since the regex is derived from PV, an older branch scopes it to that branch's series, and the 2.39 series scarthgap ships does not qualify. 2.39 adopted the new kernel mount API, so 2.39.1 introduced LIBMOUNT_FORCE_MOUNT2={always,never,auto} as, in its own words, "a stable workaround for use cases where new kernel API is not ready to use"; the series also took new CPU model support and libblkid bcachefs sub-device label probing. That is a property of the 2.39 series rather than of the project -- 2.42.2 is 32 commits of pure fixes -- but it means this must not be backported unchanged, and each branch's series needs checking on its own. For the avoidance of doubt it is not a development-series effect either:
util-linux has no development/stable version split, and pre-release work goes to -rc tags.
Quoted 2 lines
AI-Generated: Kiro with Claude Opus 5
Signed-off-by Daniel Turull <[email protected]>
Hi Daniel,
We merged the rest of this series but skipped this patch as I wanted to take a closer look at that last paragraph above.
Scarthgap already has v2.39.3, so API fixes in 2.39.1 aren't really an issue. However, reading the 2.39.1 release notes it aimed to "resolve the regression that occurred due to the v2.39 rewrite for the new kernel mount interface" which sounds like a valid fix for me. Supporting new CPU models is low risk and likely wanted by many users of our stable branches anyway. And allowing libblkid to handle bcachefs' version scheme and sub-device labels is low risk and a sensible way to handle what was still a moving target.
So I'd say util-linux have shown good judgement in managing a stable branch and we should be able to track any of their stable branches.
Please send a v2 with an updated commit message if you agree with my conclusions.
Best regards,
Signature · 1 line
Paul Barker
Re: [PATCH 1/7] util-linux: inherit upstream-stable-release-point
Quoted 56 lines · Paul Barker
Quoted 38 lines · On Fri, 2026-07-31 at 14:25 +0200, [email protected] wrote:
From: Daniel Turull <[email protected]>
util-linux's README ("Stable Branches") documents stable/v<major>.<minor> branches whose maintenance releases are bug fixes only, so upgrades within a major.minor are stable point upgrades per the OE-Core stable release policy (ref-manual, "Stable Point Release Upgrades").
https://docs.yoctoproject.org/dev/ref-manual/release-process.html#stable-point-release-upgrades
https://github.com/util-linux/util-linux/blob/v2.42.2/README#L95Checked the last point release for feature creep:
2.42.2 (Jun 16 2026), against 2.42.1 (May 18 2026): 32 commits, all fixes or hardening -- memory safety (a libblkid use-after-free, two buffer overflows, a libfdisk GPT fix), privilege tightening (X-mount.subdir restricted for non-root), diagnostics (fanotify queue overflow detection) and documentation. No new options or behaviour.
These releases are not picked up on the OE stable branches: util-linux has had zero point-release bumps on kirkstone, scarthgap or wrynose since each branch forked from master, leaving them at 2.37.4, 2.39.3 and 2.41.3 respectively. This addresses that gap going forward.
This addresses the general case on master, where PV is 2.42.x. Since the regex is derived from PV, an older branch scopes it to that branch's series, and the 2.39 series scarthgap ships does not qualify. 2.39 adopted the new kernel mount API, so 2.39.1 introduced LIBMOUNT_FORCE_MOUNT2={always,never,auto} as, in its own words, "a stable workaround for use cases where new kernel API is not ready to use"; the series also took new CPU model support and libblkid bcachefs sub-device label probing. That is a property of the 2.39 series rather than of the project -- 2.42.2 is 32 commits of pure fixes -- but it means this must not be backported unchanged, and each branch's series needs checking on its own. For the avoidance of doubt it is not a development-series effect either:
util-linux has no development/stable version split, and pre-release work goes to -rc tags.Quoted 2 lines
AI-Generated: Kiro with Claude Opus 5
Signed-off-by Daniel Turull <[email protected]>Hi Daniel,
We merged the rest of this series but skipped this patch as I wanted to take a closer look at that last paragraph above.
Scarthgap already has v2.39.3, so API fixes in 2.39.1 aren't really an issue. However, reading the 2.39.1 release notes it aimed to "resolve the regression that occurred due to the v2.39 rewrite for the new kernel mount interface" which sounds like a valid fix for me. Supporting new CPU models is low risk and likely wanted by many users of our stable branches anyway. And allowing libblkid to handle bcachefs' version scheme and sub-device labels is low risk and a sensible way to handle what was still a moving target.
Quoted 5 lines
So I'd say util-linux have shown good judgement in managing a stable branch and we should be able to track any of their stable branches.
Please send a v2 with an updated commit message if you agree with my conclusions.
I agree with your conclusions. I'll send a v2 for only this one.
I'm waiting to send series 3 until all what I sent is merged (for series 1 and 2). I was hopping to have more components that will have stable branches, but most are single track.
Best regards,
Daniel
Quoted 3 lines
Best regards,
PATCH 2/7 systemd: inherit upstream-stable-release-point
In reply to [email protected]From: Daniel Turull <[email protected]>
systemd's README ("STABLE BRANCHES AND BACKPORTS") documents per-release stable branches carrying backported patches. The current one, v261-stable, is branched in the main repository; the README still points at the systemd-stable repository, which holds the branches up to v255. The major is a single version part (261 -> 261.1), so upgrades within a major are stable point upgrades per the OE-Core stable release policy (ref-manual, "Stable Point Release Upgrades"). STABLE_VERSION_PARTS is set to 1 accordingly.
https://docs.yoctoproject.org/dev/ref-manual/release-process.html#stable-point-release-upgrades
https://github.com/systemd/systemd/blob/v261.1/README#L460
https://github.com/systemd/systemd/tree/v261-stable
Checked the last point release for feature creep:
261.2 (Jul 23 2026), against 261.1 (Jun 26 2026): 277 commits, mostly fixes. NEWS files both releases under "CHANGES WITH 261" and gives neither its own entry. Four items are feature-shaped: refcounting, argument handling and JSON output additions, plus one new internal string-util flag.
Those are small internal additions on a real, diverged stable branch rather than mainline drift, and none introduce a new subsystem: closer in scope to a security-hardening batch than a feature release, though broader than a pure bugfix release.
These bumps are not free: the scarthgap 255.4 -> 255.13 bump was held for a v2 because TCLIBC=musl broke, and was merged once fixed. A point release being fixes-only upstream does not remove the need to build and test it.
Already tracked this way on the OE stable branches, counting only bumps made since each branch forked from master: kirkstone 250.4 -> 250.14 and scarthgap 255.4 -> 255.21. wrynose has had no point-release bump yet.
AI-Generated: Kiro with Claude Opus 5
--- meta/recipes-core/systemd/systemd.inc | 5 +++++ 1 file changed, 5 insertions(+)
meta/recipes-core/systemd/systemd.inc +5 -0
@@ -21,4 +21,9 @@ SRC_URI = "git://github.com/systemd/systemd.git;protocol=https;branch=${SRCBRANC CVE_PRODUCT = "systemd" +# systemd publishes bugfix/security-only releases on its stable/v<major>-stable +# branches (e.g. 261 -> 261.1). The major is a single version part. +STABLE_VERSION_PARTS = "1" +inherit upstream-stable-release-point + CVE_STATUS[CVE-2019-3815] = "not-applicable-platform: only applied to RHEL"
PATCH 3/7 glib-2.0: inherit upstream-stable-release-point
In reply to [email protected]From: Daniel Turull <[email protected]>
GLib's docs/backports.md states that only bug and documentation fixes are backported to the current stable branch, that new features and API/ABI changes must not be, and that micro stable releases are intended as drop-in replacements. So upgrades within a major.minor are stable point upgrades per the OE-Core stable release policy (ref-manual, "Stable Point Release Upgrades").
https://docs.yoctoproject.org/dev/ref-manual/release-process.html#stable-point-release-upgrades
https://gitlab.gnome.org/GNOME/glib/-/blob/2.88.2/docs/backports.md#L18
Checked the last two point releases for feature creep:
2.88.2 (Jun 25 2026): entirely "Bugs fixed" backports plus translation updates.
2.88.1 (May 02 2026): seven fixes -- a GCC 16 miscompilation, a GRegex out-of-bounds read with security impact, and five further out-of-bounds reads. No API or behaviour changes.
The series opened with 2.88.0 (Mar 16 2026), which must stay outside the regex as the feature-level release.
Already tracked this way on the OE stable branches, counting only bumps made since each branch forked from master: kirkstone 2.72.0 -> 2.72.3, scarthgap 2.78.4 -> 2.78.6, and wrynose 2.88.0 -> 2.88.2.
AI-Generated: Kiro with Claude Opus 5
--- meta/recipes-core/glib-2.0/glib.inc | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
meta/recipes-core/glib-2.0/glib.inc +3 -1
@@ -30,7 +30,9 @@ LEAD_SONAME = "libglib-2.0.*" GNOMEBN = "glib" -inherit gettext gi-docgen gnomebase ptest-gnome upstream-version-is-even bash-completion gio-module-cache manpages gobject-introspection-data +# GLib publishes bugfix/security-only micro releases on its stable +# (even-minor) series. +inherit gettext gi-docgen gnomebase ptest-gnome upstream-version-is-even bash-completion gio-module-cache manpages gobject-introspection-data upstream-stable-release-point S = "${UNPACKDIR}/${GNOMEBN}-${PV}"
PATCH 4/7 dbus: inherit upstream-stable-release-point
In reply to [email protected]From: Daniel Turull <[email protected]>
D-Bus's CONTRIBUTING.md documents even-minor stable branches, currently dbus-1.16.x, that receive only cherry-picked bug fixes, so upgrades within a major.minor are stable point upgrades per the OE-Core stable release policy (ref-manual, "Stable Point Release Upgrades"). It also states that odd-minor development branches such as 1.17.x are not supported at all and receive no bug fixes, not even for security vulnerabilities, so only the even-minor stable series should be tracked.
https://docs.yoctoproject.org/dev/ref-manual/release-process.html#stable-point-release-upgrades
https://gitlab.freedesktop.org/dbus/dbus/-/blob/dbus-1.16.2/CONTRIBUTING.md#L65
Checked the only point release in the series so far for feature creep, the 1.16.x series having just one non-.0 release to date:
1.16.2 (Feb 27 2025): two items -- one build-regression fix for verbose-mode builds against libselinux >= 3.8, and a documentation update. No API or behaviour changes.
Already tracked this way on the OE stable branches, counting only bumps made since each branch forked from master: kirkstone 1.14.0 -> 1.14.8. scarthgap has had zero point-release bumps since its fork and remains at 1.14.10; wrynose ships 1.16.2 as its initial version with no bump yet.
AI-Generated: Kiro with Claude Opus 5
--- meta/recipes-core/dbus/dbus_1.16.2.bb | 6 ++++++ 1 file changed, 6 insertions(+)
meta/recipes-core/dbus/dbus_1.16.2.bb +6 -0
@@ -5,6 +5,12 @@ SECTION = "base" inherit meson pkgconfig gettext upstream-version-is-even ptest-gnome +# D-Bus publishes bugfix/security-only micro releases on its stable +# (even-minor) branches. Odd-minor development branches (e.g. 1.17.x) are +# not supported at all and receive no bug fixes, not even for security +# vulnerabilities, so only the even-minor stable series is tracked here. +inherit upstream-stable-release-point + LICENSE = "AFL-2.1 OR GPL-2.0-or-later" LIC_FILES_CHKSUM = "file://COPYING;md5=eb0ffc69a965797a3d6686baa153ef05 \ file://dbus/dbus.h;beginline=6;endline=22;md5=df4251a6c6e15e6a9e3c77b2ac30065d \
PATCH 5/7 xz: inherit upstream-stable-release-point
In reply to [email protected]From: Daniel Turull <[email protected]>
XZ Utils's README documents that an even minor (Y) is a stable series where the revision (Z) "is incremented when bugs get fixed without adding any new features". So upgrades within a major.minor are stable point upgrades per the OE-Core stable release policy (ref-manual, "Stable Point Release Upgrades").
https://docs.yoctoproject.org/dev/ref-manual/release-process.html#stable-point-release-upgrades
https://github.com/tukaani-project/xz/blob/v5.8.3/README#L138
Checked the last two point releases for feature creep:
5.8.3 (Mar 31 2026): one CVE (CVE-2026-34743, a buffer overflow in lzma_index_append), one invalid-memory-access fix, build portability fixes for Windows ARM64EC and Hurd, and man page translations. No new options or API.
5.8.2 (Dec 17 2025): build portability fixes for four toolchains, a RHEL 9 kernel-bug workaround, and a resource-aware memory-limit default tweak that is a bugfix rather than a new feature. No new options or API.
Already tracked this way on the OE stable branches, counting only bumps made since each branch forked from master: kirkstone picked up 5.2.6 and scarthgap 5.4.7, one bump each.
AI-Generated: Kiro with Claude Opus 5
--- meta/recipes-extended/xz/xz_5.8.3.bb | 4 ++++ 1 file changed, 4 insertions(+)
meta/recipes-extended/xz/xz_5.8.3.bb +4 -0
@@ -34,6 +34,10 @@ SRC_URI[sha256sum] = "3d3a1b973af218114f4f889bbaa2f4c037deaae0c8e815eec381c3d546 UPSTREAM_CHECK_REGEX = "releases/tag/v(?P<pver>\d+(\.\d+)+)" UPSTREAM_CHECK_URI = "https://github.com/tukaani-project/xz/releases/" +# XZ Utils publishes bugfix/security-only micro releases on its stable +# (even-minor) branches. +inherit upstream-stable-release-point + CACHED_CONFIGUREVARS += "gl_cv_posix_shell=/bin/sh" inherit autotools gettext ptest
PATCH 6/7 git: inherit upstream-stable-release-point
In reply to [email protected]From: Daniel Turull <[email protected]>
Git's maintainer documentation defines the version scheme explicitly:
vX.Y.0 are feature releases carrying bugfixes and enhancements in any area, while vX.Y.Z (Z>0) maintenance releases "contain only bugfixes for the corresponding vX.Y.0 feature release and earlier maintenance releases". So upgrades within a major.minor are stable point upgrades per the OE-Core stable release policy (ref-manual, "Stable Point Release Upgrades").
https://docs.yoctoproject.org/dev/ref-manual/release-process.html#stable-point-release-upgrades
https://github.com/git/git/blob/v2.55.0/Documentation/howto/maintain-git.adoc#L47
Checked recent maintenance releases for feature creep:
2.44.4 (May 28 2025): CVE fixes only, seven of them, merged up from the fixes that appeared in v2.43.7. The release notes contain nothing else. 2.35.7 (Feb 06 2023): four fixes -- two libcurl portability fixes, and two symlink-escape fixes in apply and clone back-merged from older maintenance lines.
No 2.55.x point release exists yet, 2.55.0 being the current tip, so this relies on the documented policy plus the historical pattern above rather than a same-series point release. The ref-manual admits that basis: a recipe may qualify on clear historical evidence that a class of bump is bugfix-only (ref-manual, "Criteria for Qualifying Upstreams").
Already tracked this way on the OE stable branches, counting only bumps made since each branch forked from master: kirkstone 2.35.2 -> 2.35.7, five point bumps, and scarthgap 2.44.0 -> 2.44.4, three point bumps. wrynose ships 2.53.0 as its initial version with no bump yet.
AI-Generated: Kiro with Claude Opus 5
--- meta/recipes-devtools/git/git_2.55.0.bb | 4 ++++ 1 file changed, 4 insertions(+)
meta/recipes-devtools/git/git_2.55.0.bb +4 -0
@@ -46,6 +46,10 @@ EXTRA_OECONF:append:class-native = " --with-gitconfig=/etc/gitconfig " # Needs brokensep as this doesn't use automake inherit autotools-brokensep perlnative bash-completion manpages +# Git's maintainer docs define vX.Y.Z (Z>0) maintenance releases as +# bugfix-only, scoped to the corresponding vX.Y.0 feature release. +inherit upstream-stable-release-point + EXTRA_OEMAKE = "NO_RUST=1 NO_PYTHON=1 CFLAGS='${CFLAGS}' LDFLAGS='${LDFLAGS}'" EXTRA_OEMAKE += "'PERL_PATH=/usr/bin/env perl'" EXTRA_OEMAKE += "COMPUTE_HEADER_DEPENDENCIES=no"
PATCH 7/7 perl: inherit upstream-stable-release-point
In reply to [email protected]From: Daniel Turull <[email protected]>
perlpolicy documents a strict maintenance-branch policy: new releases of a maint branch may only contain security/CVE fixes, crashing bugs, regressions, build and install blockers, portability fixes and factual documentation corrections, and must not contain patches that "add or remove features", "break binary compatibility", or "add new warnings or errors or deprecate features". New dual-life module versions are explicitly deferred to the next stable series. So upgrades within a major.minor are stable point upgrades per the OE-Core stable release policy (ref-manual, "Stable Point Release Upgrades"). Long-lived per-even-minor maint branches back this up, maint-5.6 through maint-5.42, with a documented back-porting vote process.
https://docs.yoctoproject.org/dev/ref-manual/release-process.html#stable-point-release-upgrades
https://github.com/Perl/perl5/blob/v5.42.2/pod/perlpolicy.pod#L259
Checked the last two point releases for feature creep. perldelta makes this easy to see, as maint releases carry no "Core Enhancements" section at all:
5.42.2 (Mar 29 2026): one CVE in a vendored dependency, CVE-2026-4176 in Compress::Raw::Zlib, plus module version bumps. States "There are no changes intentionally incompatible with 5.42.1".
5.42.1 (Mar 08 2026): four fixes -- a Configure fix so POSIX locale values can be passed in for cross-compilation, an AIX thread-safe locale workaround, a Win32 build fix, and module version bumps. States "There are no changes intentionally incompatible with Perl 5.42.0". 5.42.0 (Jul 02 2025) is the series-opening release, not a point
release: it adds seven language-level features, confirming X.Y.0 bumps are feature bumps that must stay outside the regex.
Cross-checked the previous series the same way: 5.40.1, 5.40.2 and 5.40.3 all show the same profile, with security, module, documentation, test and bug-fix sections only and no Core Enhancements.
The policy forbidding binary-compatibility breaks in maint releases also covers the ABI concern directly.
Already tracked this way on the OE stable branches, counting only bumps made since each branch forked from master: kirkstone 5.34.1 -> 5.34.3 and scarthgap 5.38.2 -> 5.38.4 are both in-series point bumps. wrynose is still at 5.42.0 while master is at 5.42.2, so it is missing the CVE-2026-4176 fix -- exactly the tracking gap --stable is meant to close.
AI-Generated: Kiro with Claude Opus 5
--- meta/recipes-devtools/perl/perl_5.44.0.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
meta/recipes-devtools/perl/perl_5.44.0.bb +1 -1
@@ -27,7 +27,7 @@ SRC_URI[perl.sha256sum] = "3b855066b92491cb40e86affb1ca57d1a388aa43e51b91c7806a3 B = "${WORKDIR}/perl-${PV}-build" -inherit upstream-version-is-even update-alternatives +inherit upstream-version-is-even update-alternatives upstream-stable-release-point DEPENDS += "perlcross-native bzip2 zlib virtual/crypt" DEPENDS:append:class-native = " bzip2-replacement-native"