aws-patch v1.10.1

Fixed

• Amazon Linux 2023 "newer release available" reported forever, even
  immediately after successfully upgrading to that exact release.
  dnf's release-notification banner lists the latest known AL2023
  point-release snapshot unconditionally -- including when it's the
  exact one the host is already running. pm_check_releasever_update
  (lib/dnf.sh) was reporting that scraped value as "available" with no
  comparison against the currently running release, so every run
  re-triggered the expensive pm_upgrade_releasever step
  (dnf upgrade --releasever=..., often 30s-plus, sometimes much longer
  under load) for a release the host was already on -- with nothing to
  actually upgrade. Fixed by extracting the currently-running dated
  snapshot from OS_NAME/PRETTY_NAME (the generic OS_VERSION_ID is
  only ever "2023" and can't be used for this comparison) and only
  reporting a candidate that is genuinely newer. pm_list_releasever_updates
  received the same fix. New regression tests reproduce the exact
  scenario from a live host (banner lists 2023.12.20260727while
  already running 2023.12.20260727) alongside a "genuinely behind"
  case to confirm real updates are still detected correctly.

---

Install

Debian/Ubuntu:

curl -fsSLO https://github.com/yousafkhamza/aws-patch/releases/download/v1.10.1/aws-patch_1.10.1_all.deb
sudo dpkg -i aws-patch_1.10.1_all.deb

RHEL/Amazon Linux/Rocky/AlmaLinux:

curl -fsSLO https://github.com/yousafkhamza/aws-patch/releases/download/v1.10.1/aws-patch-1.10.1-1.noarch.rpm
sudo rpm -i aws-patch-1.10.1-1.noarch.rpm

One-line installer (any supported OS):

curl -fsSL https://raw.githubusercontent.com/yousafkhamza/aws-patch/main/install.sh | sudo bash

Verify downloads against SHA256SUMS in this release.