Upgrade GitHub Actions for Node 24 compatibility#36
Upgrade GitHub Actions for Node 24 compatibility#36salmanmkc wants to merge 3 commits intoshareAI-lab:mainfrom
Conversation
- 11 sessions from basic agent loop to autonomous teams - Python MVP implementations for each session - Mental-model-first docs in en/zh/ja - Interactive web platform with step-through visualizations - Incremental architecture: each session adds one mechanism
Signed-off-by: Salman Muin Kayser Chishti <13schishti@gmail.com>
|
@salmanmkc is attempting to deploy a commit to the crazyboym's projects Team on Vercel. A member of the Team first needs to authorize it. |
cool thanks! |
- s03: inject reminder into tool_result instead of mutating history (#37) - s05: SkillLoader uses rglob("SKILL.md") + frontmatter name priority, matching Agent Skills standard (#30, PR #34) - CI: upgrade actions/checkout and actions/setup-node to v6 (#36) - docs: update s05 skill directory structure in all 3 languages
|
Correction: This PR was automatically closed by GitHub when we force-pushed after a The CI upgrade has been incorporated into main (commit dbffe7c). Thanks for the contribution! 更正：这个 PR 是 |
2 participants
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
actions/checkoutv4v6actions/setup-nodev4v6Context
Per GitHub's announcement, Node 20 is being deprecated and runners will begin using Node 24 by default starting June 2nd, 2026.
Why this matters
always-authwas removed — if your workflow uses it, the step may failSecurity 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.