Move CI off the deprecated Node 20 runtime - #9
Merged
Conversation
Every action in both workflows targeted Node 20, which GitHub runners now force onto Node 24 with a deprecation warning. They were also 3-5 majors behind, not one: actions/checkout v4 -> v7 actions/setup-node v4 -> v7 actions/upload-artifact v4 -> v7 astral-sh/setup-uv v4 -> v9 codecov/codecov-action v4 -> v7 (pypa/gh-action-pypi-publish stays on its floating release/v1 tag.) The TypeScript job now runs a matrix of Node 20 and 24. package.json declares engines >=20, so both ends of that claim are tested instead of only the newest runtime — a v2-SDK-era dependency that quietly needs 22+ would otherwise be invisible until a user hit it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LVnEdm6smNC5ZJzghc7WRY
`astral-sh/setup-uv@v9` fails to resolve:
Unable to resolve action `astral-sh/setup-uv@v9`, unable to find version `v9`
The v9.0.0 release exists but that repository no longer publishes a floating
major tag, so the version has to be exact. checkout, setup-node,
upload-artifact and codecov-action all do publish theirs and stay on @v7.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LVnEdm6smNC5ZJzghc7WRY
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Every action in both workflows targeted Node 20, which the runners now force onto Node 24 with a deprecation warning on each run. They were also 3–5 majors behind, not one:
actions/checkoutactions/setup-nodeactions/upload-artifactastral-sh/setup-uvcodecov/codecov-actionpypa/gh-action-pypi-publishstays on its floatingrelease/v1tag.Node matrix
The TypeScript job now runs on Node 20 and 24.
package.jsondeclaresengines >=20, so testing only the newest runtime would leave the lower bound unverified — an SDK-v2-era dependency that quietly needs 22+ would stay invisible until a user hit it. Check names change totest-typescript (20)/test-typescript (24).The job names for Python are unchanged.
🤖 Generated with Claude Code
https://claude.ai/code/session_01LVnEdm6smNC5ZJzghc7WRY