// Use when updating major Node.js versions across ng-mocks projects, including CI/CD, .nvmrc, Docker images, npm compatibility, @types/node, and wrapper-based validation.
| name | update-node-version |
| description | Use when updating major Node.js versions across ng-mocks projects, including CI/CD, .nvmrc, Docker images, npm compatibility, @types/node, and wrapper-based validation. |
Use this skill when the request is to update major Node.js version across some or all of the repository.
Begin with a plain Markdown checklist that works in AI Agent:
- [ ] Identify which projects should move to the new Node line
- [ ] Inspect all current Node, npm, Docker, and type-version declarations
- [ ] Update the affected config and package files together
- [ ] Re-bootstrap dependencies with wrapper commands
- [ ] Run wrapper-based validation on every changed target
- [ ] Summarize the new version mapping and any compatibility limits
.nvmrccompose.yml.circleci/config.ymlpackage.jsontests-e2e/package.jsone2e/*/package.json.nvmrcnpm versionengines.npm@types/node where applicablesh compose.sh <target>.sh test.sh for root, e2e, and every changed target.# Bootstrap changed targets
sh compose.sh root
sh compose.sh e2e
sh compose.sh <target>
# Validation
sh test.sh root
sh test.sh e2e
sh test.sh <target>
sh test.sh rootsh test.sh e2esh test.sh <target> for each target whose Node line changednpm install, npm update, or ad-hoc node commands for validation when wrapper commands exist.chore(docker): updating node images.Use when triaging or fixing ng-mocks GitHub issues and bug reports in a dedicated worktree based on upstream/main, with a local issue-* regression test, a focused source fix, coverage validation, e2e matrix checks, a conventional commit message, and a pull request.
Use when refreshing package-lock.json files in ng-mocks.
Use when syncing or simplifying example code in docs/articles or README.md so embedded docs samples stay aligned with examples tests while removing compatibility noise from the published snippets.
Use when preparing GitHub Dependabot pull requests by listing open PRs, verifying they are authored by app/dependabot, enabling auto-merge, and approving them without merging manually.
Use when replaying the current local branch onto upstream/main, or onto another provided remote branch, by stashing local changes, resetting to the target branch, and cherry-picking missing commits back one by one.