ci: pin the ubuntu Node 22 leg to the declared engines floor

package.json requires `^22.23.4 || >=24.0.0` and STATE.md documents the final
gate matrix as Node 22.23.4 plus Node 24.22.1, but the CI matrix asked for the
floating `22` alias, so the leg could silently resolve below the supported
floor and never proved the minimum we declare. Pin it to 22.23.4 and describe
the matrix accurately in STATE.md.
This commit is contained in:
DeryFerd
2026-11-15 22:33:03 +07:00
parent 98e01cc47b
commit 241b3bef05
2 changed files with 5 additions and 2 deletions
+4 -1
View File
@@ -31,7 +31,10 @@ jobs:
- os: windows-latest
node: 24
- os: ubuntu-latest
node: 22
# Pinned to the declared engines floor (`^22.23.4 || >=24` in
# package.json) so CI proves the minimum supported Node rather than
# whatever the floating `22` alias resolves to on the day it runs.
node: "22.23.4"
steps:
- name: Checkout repository
uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+1 -1
View File
@@ -1,7 +1,7 @@
# BLA state of the project
**Version:** 3.4.1 (`package.json` ↔ `src/identity.ts`, verified by build; see `CHANGELOG.md`)
**Status:** CI matrix runs typecheck, build, tests and the benchmark on ubuntu / macos / windows with Node 24. Windows checkouts keep `challenge/**` LF via `.gitattributes` so the CrackMe seals verify.
**Status:** CI matrix runs typecheck, build, tests and the benchmark on ubuntu / macos / windows with Node 24, plus ubuntu on the pinned engines floor Node 22.23.4. Windows checkouts keep `challenge/**` LF via `.gitattributes` so the CrackMe seals verify.
**Publishing:** tagged releases (`git tag bla-agents-<version>`) plus GitHub Releases. The release workflow can also publish the packed tarball to npm with provenance when `NPM_TOKEN`/OIDC is configured; a release cut may intentionally skip the npm step (see `CHANGELOG.md`).
## One-sentence usage