From c34897f73c19ed00229c0715a3de11b136040e96 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Mon, 18 May 2026 19:37:13 +0000
Subject: [PATCH] Version Packages

---
 .changeset/drop-node-20.md | 13 -------------
 CHANGELOG.md               | 14 ++++++++++++++
 package.json               |  2 +-
 3 files changed, 15 insertions(+), 14 deletions(-)
 delete mode 100644 .changeset/drop-node-20.md

diff --git a/.changeset/drop-node-20.md b/.changeset/drop-node-20.md
deleted file mode 100644
index e398ab2..0000000
--- a/.changeset/drop-node-20.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-'github-actions-updater': minor
----
-
-Drop Node 20 support; require Node 22+.
-
-Node 20 left LTS at the end of April 2026, so the project drops it from its supported runtimes. The CLI is now tested on Node 22 and Node 24, with Node 24 as the build/release default. `package.json`'s `engines.node` bumps from `>=20.0.0` to `>=22.0.0`.
-
-**What this means in practice:** the `engines` field is advisory — npm will print a warning when installing on Node 20 but will still complete the install. Configurations with `engine-strict=true` will refuse outright. The CLI itself uses no Node 22+ APIs in this release, so unaffected users on Node 20 are likely to keep working for a while — but any regression observed on Node 20 will not be treated as a bug, and CI will not catch one.
-
-**What to do if you're on Node 20:** upgrade your runner to Node 22 or Node 24. There are no source-level API changes in this release; the bump is policy-only.
-
-Why this isn't a major: the `engines` field is a soft contract, no runtime API changed, and the package is young enough that burning a 2.0.0 on a Node-support narrowing alone would make the version stream noisier than it needs to be. A loud changelog entry captures the contract change without committing the version number.
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 1f14559..fbacc99 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,19 @@
 # github-actions-updater
 
+## 1.2.0
+
+### Minor Changes
+
+- 9eae823: Drop Node 20 support; require Node 22+.
+
+  Node 20 left LTS at the end of April 2026, so the project drops it from its supported runtimes. The CLI is now tested on Node 22 and Node 24, with Node 24 as the build/release default. `package.json`'s `engines.node` bumps from `>=20.0.0` to `>=22.0.0`.
+
+  **What this means in practice:** the `engines` field is advisory — npm will print a warning when installing on Node 20 but will still complete the install. Configurations with `engine-strict=true` will refuse outright. The CLI itself uses no Node 22+ APIs in this release, so unaffected users on Node 20 are likely to keep working for a while — but any regression observed on Node 20 will not be treated as a bug, and CI will not catch one.
+
+  **What to do if you're on Node 20:** upgrade your runner to Node 22 or Node 24. There are no source-level API changes in this release; the bump is policy-only.
+
+  Why this isn't a major: the `engines` field is a soft contract, no runtime API changed, and the package is young enough that burning a 2.0.0 on a Node-support narrowing alone would make the version stream noisier than it needs to be. A loud changelog entry captures the contract change without committing the version number.
+
 ## 1.1.0
 
 ### Minor Changes
diff --git a/package.json b/package.json
index 26b1ea9..71a479e 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "github-actions-updater",
-  "version": "1.1.0",
+  "version": "1.2.0",
   "description": "ncu for GitHub Actions — scans .github/workflows for outdated remote uses: references and reports or updates them, with a polished colorful CLI.",
   "keywords": [
     "github-actions",