Added
- Full AL2023 point-release list logged on every run. Previously
only the single highest pending release was logged
(Newer Amazon Linux release available: X). Now every pending point
release is listed with its exactdnf upgrade --releasever=...
command, and the run explicitly states whether the kernel will be
included or excluded when crossing -- visible in--check,
--dry-run, and live runs alike, not just the interactive picker.
Fixed
--kerneldidn't govern the AL2023 release-crossing step. Crossing
a point-release boundary applies that release's full package set,
which very often bundles a kernel bump alongside everything else.
pm_upgrade_releaseveralways applied it unconditionally regardless of
--kernel-- meaning a plain--yesrun (no--kernel) could still
silently end up installing a new kernel, just because a release
boundary happened to be pending, completely defeating--kernel's
opt-in guarantee for that specific path.lib/dnf.sh: newpm_upgrade_releasever_no_kernel(), mirroring
pm_full_upgrade_no_kernel()-- runs the release-crossing
transaction with native--exclude='kernel*'.aws-patch.sh:run_patch()now selects the correct
releasever-upgrade function based onFLAG_KERNEL, exactly like it
already does for the normal full-upgrade step. Dry-run messaging
updated to match.
- New test coverage confirming
pm_upgrade_releasever_no_kernelexcludes
the kernel andpm_upgrade_releasever(the--kernelpath) does not.
81/81 tests passing.
Install
Debian/Ubuntu:
curl -fsSLO https://github.com/yousafkhamza/aws-patch/releases/download/v1.10.5/aws-patch_1.10.5_all.deb
sudo dpkg -i aws-patch_1.10.5_all.debRHEL/Amazon Linux/Rocky/AlmaLinux:
curl -fsSLO https://github.com/yousafkhamza/aws-patch/releases/download/v1.10.5/aws-patch-1.10.5-1.noarch.rpm
sudo rpm -i aws-patch-1.10.5-1.noarch.rpmOne-line installer (any supported OS):
curl -fsSL https://raw.githubusercontent.com/yousafkhamza/aws-patch/main/install.sh | sudo bashVerify downloads against SHA256SUMS in this release.