fix(ci): bump GitHub Actions off deprecated Node 20 runtime (#396)

* fix(ci): bump GitHub Actions off deprecated Node 20 runtime

GitHub is forcing Node 24 on 2026-06-16 and removing Node 20 from runners
on 2026-09-16. Bump all first-party actions to their current Node 24
majors so the deprecation annotation clears and the workflows keep running.

- build-and-deploy.yml: checkout@v4→v5, configure-pages@v4→v5,
  upload-pages-artifact@v3→v5, deploy-pages@v4→v5
- a11y.yml / lighthouse.yml: checkout@v4→v5, setup-node@v4→v5,
  node-version 20→24 (for pa11y-ci / Lighthouse)

Standard usage only — no action inputs changed. setup-node's v5 auto-cache
does not trigger (no packageManager field in package.json).

Closes #395

* fix(a11y): upgrade pa11y-ci to restore browser download

* fix(a11y): install Chrome for pa11y-ci in workflow

* fix(ci): run pa11y/Lighthouse tools on Node 20, keep actions on Node 24

The pa11y-ci job failed after the Node 24 bump: pa11y-ci's bundled
Puppeteer 9 cannot launch its Chromium on Node 24 (ENOENT on the bundled
browser). The GitHub Actions deprecation is about the *action* runtimes,
not the Node version the test tools run on — those are independent.

So keep the action bumps (checkout/setup-node/configure-pages/
upload-pages-artifact/deploy-pages @v5, all Node 24 runtimes, which clears
the deprecation) but run the pa11y/Lighthouse tools back on Node 20, their
validated runtime. This restores the exact known-good config that passed
on #394.

Reverts the earlier modernization attempt (pa11y-ci ^4 + an `npx puppeteer
browsers install chrome` step that was itself failing on a flaky Chrome
download) back to pa11y-ci ^3; restores the accurate Puppeteer-9 comments
in lab.html.

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>

Author: Dewain27

.github/workflows/a11y.yml

@@ -33,7 +33,7 @@ jobs:
 
     steps:
       - name: Checkout
-        uses: actions/checkout@v4
+        uses: actions/checkout@v5
 
       - name: Setup Ruby
         uses: ruby/setup-ruby@v1
@@ -47,7 +47,11 @@ jobs:
           JEKYLL_ENV: production
 
       - name: Setup Node
-        uses: actions/setup-node@v4
+        uses: actions/setup-node@v5
+        # The action runtime is Node 24 (clears the deprecation), but the
+        # browser test tool runs on Node 20: pa11y-ci's bundled Puppeteer 9
+        # cannot launch its Chromium on Node 24. The Node the tool runs on is
+        # independent of the action's own runtime.
         with:
           node-version: "20"
 

.github/workflows/build-and-deploy.yml

@@ -43,7 +43,7 @@ jobs:
 
     steps:
       - name: Checkout
-        uses: actions/checkout@v4
+        uses: actions/checkout@v5
 
       - name: Setup Ruby
         uses: ruby/setup-ruby@v1
@@ -57,12 +57,12 @@ jobs:
           JEKYLL_ENV: production
 
       - name: Setup Pages
-        uses: actions/configure-pages@v4
+        uses: actions/configure-pages@v5
 
       - name: Upload artifact
-        uses: actions/upload-pages-artifact@v3
+        uses: actions/upload-pages-artifact@v5
         with:
           path: ./_site
 
       - name: Deploy to GitHub Pages
-        uses: actions/deploy-pages@v4
+        uses: actions/deploy-pages@v5

.github/workflows/lighthouse.yml

@@ -33,7 +33,7 @@ jobs:
 
     steps:
       - name: Checkout
-        uses: actions/checkout@v4
+        uses: actions/checkout@v5
 
       - name: Setup Ruby
         uses: ruby/setup-ruby@v1
@@ -47,7 +47,10 @@ jobs:
           JEKYLL_ENV: production
 
       - name: Setup Node
-        uses: actions/setup-node@v4
+        uses: actions/setup-node@v5
+        # Action runtime is Node 24 (clears the deprecation); the Lighthouse
+        # tool itself runs on Node 20 to match the pa11y job and stay on the
+        # browser tooling's validated runtime.
         with:
           node-version: "20"
 

CHANGELOG.md

@@ -15,6 +15,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - **Labels: `type: bootcamp-feature`, `status: triage`, `status: backlog`, `status: in-progress`.** Support the Backlog Tracker's Triage → Backlog → In Progress → Done lifecycle.
 
 ### Changed
+- **CI: GitHub Actions bumped off the deprecated Node 20 runtime (#395).** All first-party actions across `build-and-deploy.yml`, `a11y.yml`, and `lighthouse.yml` now run on Node 24: `actions/checkout@v5`, `actions/setup-node@v5`, `actions/configure-pages@v5`, `actions/upload-pages-artifact@v5`, and `actions/deploy-pages@v5`. Clears the "Node.js 20 actions are deprecated" annotation ahead of GitHub forcing Node 24 on 2026-06-16 and removing Node 20 from runners on 2026-09-16. The deprecation concerns the **action** runtimes only; the pa11y-ci / Lighthouse browser test tools deliberately keep running on Node `20` (`setup-node`'s `node-version`), because pa11y-ci's bundled Puppeteer 9 cannot launch Chromium on Node 24 — the tool's Node is independent of the action's own runtime. Standard usage only — no action inputs changed.
 - **Agenda module rows now render as accented cards.** On every event/workshop agenda, `type: module` rows are styled like lab rows (boxed card, prominent title, hover) but with a distinct **purple** left accent rail (`--color-journey-purple`) versus the lab rows' blue rail — surfacing that modules are clickable links to their module page and visually separating modules from labs in the timeline. Previously module rows reused the plain, unboxed `--session` styling. New `.ws-agenda-row--module` rules in `_layouts/event.html`; the module `<li>` now carries `ws-agenda-row--module`.
 - **Issue template rename: "Redesign feedback" → "Portal Enhancements".** The air-theme redesign is now just "the site," so the template covering site-wide bugs/suggestions has been renamed and broadened. File renamed `.github/ISSUE_TEMPLATE/redesign-feedback.yml` → `portal_enhancement.yml`; label `redesign` → `portal-enhancement`. The "Which page?" dropdown now includes `Backlog tracker (/tracker/)`.
 - **Label rename: `feedback` → `discussion`.** Distinguishes open-ended threads from the existing `question` label (which implies a specific answer is wanted).