[ci-maintainer] Bump Node 20-era GitHub Actions to Node 24 majors in 4 workflows (checkout v4.4.0, setup-node v4.4.0, create-pull-request v7.0.11)

Review the listed pins in .github/workflows/ci.yml, import-architectures.yml, refresh-community-people.yml, deploy-gh-pages.yml, and create-milestones.yml, then skim the create-pull-request v8 release notes for input renames. Apply the specified SHA and version-comment replacements, run ci.yml via a PR, and confirm the next scheduled runs have no Node 20 warnings and still open the expected pull request.

CI Issue

refresh-community-people.yml (run 34800476820) and the other scheduled/PR workflows emit GitHub's Node 20 deprecation warning: the pinned actions target the node20 runtime and are force-run on Node 24. Node 20 actions reach end of life on the runner; the warning becomes a hard failure when the runner removes the node20 shim.

Affected pins (current main):

• .github/workflows/ci.yml:16 — actions/checkout@11d5960a326750d5838078e36cf38b85af677262 # v4.4.0
• .github/workflows/ci.yml:20 — actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
• .github/workflows/import-architectures.yml:19,20 — same checkout/setup-node pins
• .github/workflows/import-architectures.yml:34 — peter-evans/create-pull-request@22a9089034f40e5a961c8808d113e2c98fb63676 # v7.0.11
• .github/workflows/refresh-community-people.yml:19,20,27 — same three pins
• .github/workflows/deploy-gh-pages.yml:26,29 — same checkout/setup-node pins
• .github/workflows/create-milestones.yml:21 — same checkout pin

Evidence

gh run view 34800476820 — "Refresh community profiles" schedule run, Node 20 deprecation annotations on checkout / setup-node / create-pull-request steps. Latest major tags verified against their action.yml: actions/checkout@v7.0.1, actions/setup-node@v7.0.0 and peter-evans/create-pull-request@v8.1.1 all declare runs.using: node24.

Recommendation (exact replacement text)

Keep the repo's SHA-pinning convention; only the pin and comment change:

• actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1 (replaces every 11d5960a… # v4.4.0)
• actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0 (replaces every 49933ea5… # v4.4.0)
• peter-evans/create-pull-request@5f6978faf089d4d20b00c7766989d076bb2fc7f1 # v8.1.1 (replaces 22a90890… # v7.0.11)

Verification after applying: trigger ci.yml via any PR and confirm the deprecation annotations are gone; let the next scheduled refresh-community-people / import-architectures run confirm the create-pull-request major bump still opens its PR (v8 is a major — skim its release notes for input renames before applying).

Note: open PR #193 (.github/dependabot.yml) is complementary, not a duplicate — it automates future bumps; this issue is the one-time catch-up. Contract test PR #301 may need its expected-pin data refreshed after this lands.

Who can land this

All changes are inside .github/workflows/**, which this agent's contributor-tier App token cannot push (no Workflows permission — GitHub rejects the push server-side). A maintainer using normal user credentials, or an ISSUES_PRS_MERGE agent on an App installation with Workflows read/write (#6985), must apply the edit. It is mechanical: 8 line replacements across 5 files, listed above.

Filed by ci-maintainer agent (ACMM L4/L5 — hold-gated mode)

🐝 Hive Agent: ci-maintainer | Instance: hosted-available-lke648397-260827-5n31 | SHA: unknown

— hive: agent=ci-maintainer backend=copilot model=kimi-k3