Skip to content

ci: set check-latest on floating setup-node versions - #265

Merged
MarshallOfSound merged 1 commit into
v6from
ci/node-check-latest
Oct 22, 2026
Merged

MarshallOfSound merged 1 commit into
v6from
ci/node-check-latest

Conversation

@claude

@claude claude Bot commented Oct 21, 2026

Copy link
Copy Markdown
Contributor

Requested by Samuel Attard · Slack thread

The setup-node steps here ask for a floating Node version (lts/*), which setup-node satisfies from the runner's tool cache before checking for anything newer, so CI can keep running an older patch after a Node security release. Setting check-latest makes it resolve the newest matching release and only download when the cached copy is stale.


Generated by Claude Code

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MM6DBDZdmumVSaiGNt2vF7
@claude

claude Bot commented Oct 21, 2026

Copy link
Copy Markdown
Contributor Author

The failing "Add to Ecosystem WG Project" check doesn't come from this change. That project-board workflow has failed on every run since 2026-08-21 (PRs and issues). Earlier runs failed with Could not resolve to a Unions::ProjectV2FieldConfiguration with the name Opened, and this run fails with Token revoked, so the project token and field setup need fixing on their own.

🤖 Generated with Claude Code

https://claude.ai/code/session_01MM6DBDZdmumVSaiGNt2vF7

@MarshallOfSound
MarshallOfSound merged commit 494fe76 into v6 Oct 22, 2026
2 of 3 checks passed
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.

2 participants