Upgrade Node.js to v24 and modernize development tooling - #595
Merged
Conversation
razor-x
marked this pull request as ready for review
July 28, 2026 19:38
Adopt the toolchain patterns from @seamapi/makenew-tsmodule v3.0.4, mirroring the update already applied to seamapi/javascript-http and seamapi/docs. - Add engines and devEngines and drop .nvmrc. Node v24 is now the default in CI and the devcontainer, with v22.11.0 still supported. - Update the workflow action versions and install dependencies with npm ci --ignore-scripts followed by npm rebuild. - Update the npm dependencies. Refreshing the lockfile also records the esbuild platform packages that npm tracks for tsx. - Fix the tsconfig.json schema URL. TypeScript v6 is already in place through @seamapi/smith v1.1.0, which declares typescript, tsx, eslint, and jiti as peer dependencies and depends on @types/node directly, so none of them are declared here. The Python toolchain is unchanged: Poetry, pylint, black, and the Python version matrices in CI are untouched. Running the codegen produces byte for byte identical output under the updated toolchain. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Y2XoVcysK4XshKsKtsbK4U
razor-x
force-pushed
the
claude/docs-makenew-tsmodule-update-by6n46
branch
from
July 28, 2026 19:41
49abb46 to
9d8de25
Compare
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
2 participants
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.
Summary
This PR upgrades the project's Node.js runtime requirement to v24 while maintaining backward compatibility with v22, and modernizes the development tooling stack with updated dependencies and GitHub Actions versions.
Key Changes
Node.js and Runtime Requirements
enginesdevEnginesconfiguration to declare support for Node.js v24.11.0 and v22.11.0, with npm v11.0.0 and v10.9.4.nvmrcremoval and devcontainer Node.js version from 20 to 24devEnginesconfigurationDevelopment Dependencies
^6.0.3), ESLint (^9.31.0), and type definitions (@types/node ^24.10.9)tsx(^4.6.2) andjiti(^2.4.2)GitHub Actions Updates
actions/checkoutfrom v4 to v7actions/setup-nodefrom v4 to v7 and removed npm cache configurationactions/download-artifactfrom v4 to v8actions/upload-artifactfrom v4 to v7crazy-max/ghaction-import-gpgfrom v6 to v7stefanzweifel/git-auto-commit-actionfrom v5 to v7cycjimmy/semantic-release-actionfrom v4 to v6softprops/action-gh-releasefrom v2 to v3tj-actions/globfrom v21 to v22Node.js Setup Action Improvements
.github/actions/setup-node/action.ymlwith explicit npm rebuild and postinstall/prepare script execution--ignore-scriptsflag tonpm cito prevent automatic script execution during installnpm rebuild,npm run postinstall, andnpm run preparefor better controlConfiguration Updates
tsconfig.jsonschema URL to include.jsonextensionhttps://claude.ai/code/session_01Y2XoVcysK4XshKsKtsbK4U