chore(deps)!: update all dependencies, require Node.js >= 22 - #291
Merged
Conversation
Contributor
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (4)
📒 Files selected for processing (7)
✅ Files skipped from review due to trivial changes (6)
WalkthroughBump SDK and site dependencies, raise Node.js engine floor to >=22.12.0, replace ChangesDependency & docs updates
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested labels
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Code Review
This pull request updates various dependencies and devDependencies across multiple packages in the workspace, including AWS and Azure SDKs, Astro, Vitest, and Biome. The reviewer suggests reverting the dependency version bumps in the Node.js SDK package (src/sdks/nodejs/package.json) to maintain maximum compatibility and avoid forcing consumers of the SDK to upgrade their own AWS and Azure SDK versions unnecessarily.
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the repository’s production and development dependencies (workspace-wide) and refreshes the pnpm catalog/lockfile, aiming to keep the monorepo current while retaining Node compatibility and simplifying cleanup scripts.
Changes:
- Bumped root, website, IaC, and Node.js SDK/test dependencies to newer versions and updated the pnpm catalog.
- Updated
pnpm-lock.yamlto reflect the new dependency graph. - Updated the root
cleanscript to use Node’s built-infs.rmSyncinstead ofrimraf.
Reviewed changes
Copilot reviewed 6 out of 8 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
| package.json | Bumps core deps/dev tools and pnpm version; updates clean script. |
| pnpm-workspace.yaml | Updates catalog versions (Biome, Node types, Vitest, CDK libs, etc.). |
| pnpm-lock.yaml | Refreshes lockfile to match updated dependency set. |
| src/website/package.json | Updates Astro + sitemap/check tooling versions. |
| src/iac/package.json | Bumps aws-cdk devDependency. |
| src/sdks/nodejs/package.json | Updates SDK dependency versions and bumps rimraf. |
| tests/sdks/nodejs/package.json | Updates Node.js SDK test dependency versions (keeps testcontainers on v11). |
- Bump engines.node from >=20.0.0 to >=22.0.0 (root + nodejs SDK) - Upgrade testcontainers from v11 to v12.0.1 (requires Node >=22.22) - Remove rimraf from nodejs SDK devDependencies (use fs.rmSync) BREAKING CHANGE: Requires Node.js >= 22
macalbert
changed the title
- Update all GitHub Actions workflows from node 20.x to 22.x - Update CONTRIBUTING, README, docs, SDK READMEs, examples - Update AGENTS.md pnpm version (9+ -> 11+) - Update Lambda runtime examples in skills (nodejs20.x -> nodejs22.x)
BREAKING CHANGE: Requires Node.js >= 22 - CLI: 0.10.0 -> 0.11.0 - GHA: 0.10.0 -> 0.11.0 (shares version with CLI) - Node.js SDK: 0.2.0 -> 0.3.0 - Add changelog entries for all three components
macalbert
changed the title
This was referenced May 30, 2026
Closed
Closed
- ADR-0009: SDK Dependency Compatibility Policy (min viable versions) - SDK Node.js: revert deps to ^3.700.0 (AWS) / ^4.5.0 (Azure) - SDK Node.js: engine lowered to >=18.0.0 (actual runtime minimum) - Root: engine bumped to >=22.12.0 (matches toolchain deps) - Fix escaped quotes in docs/github-action.md YAML example - Update changelogs to reflect accurate engine requirements
- SDK Node.js engines: >=18.0.0 -> >=22.12.0 (Node 18/20 are EOL) - ADR-0009 Rule 1: track active LTS, don't support dead runtimes - Update SDK changelog to reflect BREAKING engine change
- i18n (en, es, ca): prereqNode and reqNode → v22+ - DocsContent.astro: YAML examples node-version → 22.x - examples/sdk/nodejs: bump @envilder/sdk → ^0.3.0
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@src/website/src/i18n/ca.ts`:
- Line 406: The UI copy uses a broad Node version string; update the prereqNode
translation key value from "Node.js v22+" to the precise minimum supported
runtime "Node.js v22.12+" (and make the same change for the other identical
occurrence of prereqNode in this file) so the displayed requirement matches the
enforced runtime floor (>=22.12).
In `@src/website/src/i18n/en.ts`:
- Line 405: Update the displayed Node.js prerequisite string to the exact
enforced engine range: change the value of the prereqNode entry (and any other
occurrences of that same string) from "Node.js v22+" to "Node.js v22.12+" so
users are not misled into using unsupported 22.0–22.11 releases; locate the
prereqNode key in src/website src i18n (en.ts) and replace its value
accordingly.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 62ca77c6-cd3c-411b-a127-8e1827147e0e
⛔ Files ignored due to path filters (2)
.github/skills/common-architecture-decisions/SKILL.mdis excluded by none and included by nonepackage.jsonis excluded by none and included by none
📒 Files selected for processing (11)
docs/architecture/adr/0009-sdk-dependency-compatibility-policy.mddocs/changelogs/cli.mddocs/changelogs/gha.mddocs/changelogs/sdk-nodejs.mddocs/github-action.mdexamples/sdk/nodejs/package.jsonsrc/sdks/nodejs/package.jsonsrc/website/src/components/DocsContent.astrosrc/website/src/i18n/ca.tssrc/website/src/i18n/en.tssrc/website/src/i18n/es.ts
✅ Files skipped from review due to trivial changes (6)
- docs/github-action.md
- src/website/src/i18n/es.ts
- docs/changelogs/gha.md
- src/website/src/components/DocsContent.astro
- docs/changelogs/sdk-nodejs.md
- docs/architecture/adr/0009-sdk-dependency-compatibility-policy.md
🚧 Files skipped from review as they are similar to previous changes (2)
- docs/changelogs/cli.md
- src/sdks/nodejs/package.json
Update all references from '22+' to '22.12+' to match the actual engine constraint enforced by commander 15, commitlint 21, and astro 6.4. Rephrase ADR-0009 Rule 4 as a target policy.
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
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
Updates all dependencies to latest, bumps Node.js requirement to >= 22, and releases CLI 0.11.0 / Node.js SDK 0.3.0. Supersedes 8 individual Dependabot PRs.
Breaking Changes
Version Bumps
envilder)@envilder/sdk)Changes
Dependencies (root workspace)
packageManagerfield)rimraf— replaced withnode -e "fs.rmSync(...)"(zero deps, cross-platform)Node.js SDK (
src/sdks/nodejs)rimraffrom devDependenciescleanscript to usefs.rmSyncengines.nodeto>=22CI/CD Workflows
node-version: "20.x"to"22.x"tests.yml,verify-action-build.yml,tests-nodejs-sdk.yml,publish-action.yml,test-action.yml,coverage-report.ymlDocumentation
README.md,CONTRIBUTING.md,docs/requirements-installation.mddocs/github-action.md,github-action/README.mdsrc/sdks/nodejs/README.md,examples/sdk/nodejs/README.md.github/AGENTS.md(pnpm 9+ → 11+)nodejs20.x→nodejs22.x)Changelogs
[0.11.0]entries todocs/changelogs/cli.mdanddocs/changelogs/gha.md[0.3.0]entry todocs/changelogs/sdk-nodejs.mdCommits
chore(deps): update all dependencies to latestchore(scripts): Replace rimraf with Node.js fs module for clean scriptchore(deps): bump node engines to >=22 and upgrade testcontainers to v12ci: update all workflows and docs to Node.js 22chore(release): bump CLI to 0.11.0 and Node.js SDK to 0.3.0Validation
pnpm build✅pnpm lint✅ (secretlint + biome + tsc)pnpm test✅ (274 tests passing, 37 test files)pnpm format✅Closes
Closes #276
Closes #277
Closes #278
Closes #279
Closes #285
Closes #286
Closes #287
Closes #288
Summary by CodeRabbit
Breaking Changes
Chores
Documentation