[PR #111] [MERGED] Upgrade GitHub Actions for Node 24 compatibility #163

New Issue

2026-06-06T22:09:31-04:00

yindo commented

2026-06-06 22:09:31 -04:00

📋 Pull Request Information

Original PR: https://github.com/vxcontrol/pentagi/pull/111
Author: @salmanmkc
Created: 2/21/2026
Status: ✅ Merged
Merged: 2/21/2026
Merged by: @asdek

Base: master ← Head: upgrade-github-actions-node24

📝 Commits (1)

8ff0584 Upgrade GitHub Actions for Node 24 compatibility

📊 Changes

1 file changed (+6 additions, -6 deletions)

View changed files

📝 .github/workflows/ci.yml (+6 -6)

📄 Description

Summary

Upgrade GitHub Actions to their latest versions to ensure compatibility with Node 24, as Node 20 will reach end-of-life in April 2026.

Changes

Action	Old Version(s)	New Version	Release	Files
`actions/cache`	`v3`	`v5`	Release	ci.yml
`actions/checkout`	`v4`	`v6`	Release	ci.yml
`actions/setup-go`	`v5`	`v6`	Release	ci.yml
`actions/setup-node`	`v4`	`v6`	Release	ci.yml

Context

Per GitHub's announcement, Node 20 is being deprecated and runners will begin using Node 24 by default starting March 4th, 2026.

Why this matters

Node 20 EOL: April 2026
Node 24 default: March 4th, 2026
Action: Update to latest action versions that support Node 24

⚠️ Breaking Changes

actions/checkout (v4 → v6): Major version upgrade — review the release notes for breaking changes
actions/setup-go (v5 → v6): Major version upgrade — review the release notes for breaking changes
actions/cache (v3 → v5):
- ⚠️ v4 uses a new caching backend - existing caches may not be reused on first run
actions/setup-node (v4 → v6): Major version upgrade — review the release notes for breaking changes
- ⚠️ Input always-auth was removed — if your workflow uses it, the step may fail

Security Note

Actions that were previously pinned to commit SHAs remain pinned to SHAs (updated to the latest release SHA) to maintain the security benefits of immutable references.

Testing

These changes only affect CI/CD workflow configurations and should not impact application functionality. The workflows should be tested by running them on a branch before merging.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/vxcontrol/pentagi/pull/111 **Author:** [@salmanmkc](https://github.com/salmanmkc) **Created:** 2/21/2026 **Status:** ✅ Merged **Merged:** 2/21/2026 **Merged by:** [@asdek](https://github.com/asdek) **Base:** `master` ← **Head:** `upgrade-github-actions-node24` --- ### 📝 Commits (1) - [`8ff0584`](https://github.com/vxcontrol/pentagi/commit/8ff05844a026b50df22b080b43f86439c30f493a) Upgrade GitHub Actions for Node 24 compatibility ### 📊 Changes **1 file changed** (+6 additions, -6 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/ci.yml` (+6 -6) </details> ### 📄 Description ## Summary Upgrade GitHub Actions to their latest versions to ensure compatibility with Node 24, as Node 20 will reach end-of-life in April 2026. ## Changes | Action | Old Version(s) | New Version | Release | Files | |--------|---------------|-------------|---------|-------| | `actions/cache` | [`v3`](https://github.com/actions/cache/releases/tag/v3) | [`v5`](https://github.com/actions/cache/releases/tag/v5) | [Release](https://github.com/actions/cache/releases/tag/v5) | ci.yml | | `actions/checkout` | [`v4`](https://github.com/actions/checkout/releases/tag/v4) | [`v6`](https://github.com/actions/checkout/releases/tag/v6) | [Release](https://github.com/actions/checkout/releases/tag/v6) | ci.yml | | `actions/setup-go` | [`v5`](https://github.com/actions/setup-go/releases/tag/v5) | [`v6`](https://github.com/actions/setup-go/releases/tag/v6) | [Release](https://github.com/actions/setup-go/releases/tag/v6) | ci.yml | | `actions/setup-node` | [`v4`](https://github.com/actions/setup-node/releases/tag/v4) | [`v6`](https://github.com/actions/setup-node/releases/tag/v6) | [Release](https://github.com/actions/setup-node/releases/tag/v6) | ci.yml | ## Context Per [GitHub's announcement](https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/), Node 20 is being deprecated and runners will begin using Node 24 by default starting March 4th, 2026. ### Why this matters - **Node 20 EOL**: April 2026 - **Node 24 default**: March 4th, 2026 - **Action**: Update to latest action versions that support Node 24 ### ⚠️ Breaking Changes - **actions/checkout** (v4 → v6): Major version upgrade — review the [release notes](https://github.com/actions/checkout/releases) for breaking changes - **actions/setup-go** (v5 → v6): Major version upgrade — review the [release notes](https://github.com/actions/setup-go/releases) for breaking changes - **actions/cache** (v3 → v5): - ⚠️ v4 uses a new caching backend - existing caches may not be reused on first run - **actions/setup-node** (v4 → v6): Major version upgrade — review the [release notes](https://github.com/actions/setup-node/releases) for breaking changes - ⚠️ Input `always-auth` was **removed** — if your workflow uses it, the step may fail ### Security Note Actions that were previously pinned to commit SHAs remain pinned to SHAs (updated to the latest release SHA) to maintain the security benefits of immutable references. ### Testing These changes only affect CI/CD workflow configurations and should not impact application functionality. The workflows should be tested by running them on a branch before merging. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

yindo added the pull-request label 2026-06-06 22:09:31 -04:00

yindo closed this issue

2026-06-06 22:09:31 -04:00

yindo referenced this issue

2026-06-06 22:09:41 -04:00

[PR #163] [MERGED] chore: expand .gitignore with IDE and OS patterns #203

yindo referenced this issue

2026-06-06 22:09:45 -04:00

[PR #185] [MERGED] Multi-Provider Expansion & Testing Infrastructure #221

Sign in to join this conversation.