Skip to content

Upgrade Frogbot to use node24#1300

Open
blowsie wants to merge 1 commit intojfrog:devfrom
blowsie:enhancement/upgrade-frogbot-to-node24
Open

Upgrade Frogbot to use node24#1300
blowsie wants to merge 1 commit intojfrog:devfrom
blowsie:enhancement/upgrade-frogbot-to-node24

Conversation

@blowsie
Copy link
Copy Markdown

@blowsie blowsie commented May 6, 2026

Summary

Upgrades the GitHub Action runtime from the deprecated node16 to node24 (current LTS).

This is a re-do of the previous (closed, unmerged) Node 20 attempt in #770. Skipping straight to Node 24 — Node 20 itself reaches end-of-life in April 2026, so a node20 bump would be near-immediately stale.

Changes

  • action.yml: using: "node16""node24"
  • action/package.json and action/package-lock.json: "node": ">=16.0.0"">=24.0.0"
  • .github/workflows/action-test.yml: setup-node node-version: "16.x""24.x"
  • .github/workflows/test.yml: setup-node node-version: "16""24"
  • docs/templates/jfrog-pipelines/pipelines-npm.yml and pipelines-yarn2.yml: runtime image version: "16""24"

Related

Notes

This PR mirrors the exact scope of #770. There are additional node-version: "16" references in .github/workflows/release-gate.yml and .github/workflows/test-v3.yml that did not exist when #770 was opened — happy to roll those into this PR or address them separately, whichever maintainers prefer.

Test plan

  • CI: action-test.yml passes on node 24 across ubuntu / windows / macOS
  • CI: test.yml Go suite passes with node 24
  • Verify the published GitHub Action runs end-to-end on a sample repo

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 6, 2026

All contributors have signed the CLA ✍️ ✅
Posted by the CLA Assistant Lite bot.

@blowsie
Copy link
Copy Markdown
Author

blowsie commented May 6, 2026

I have read the CLA Document and I hereby sign the CLA

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant