- name
Update dependencies of the Theia framework and record what was learned. Its main use is the post-release dependency update after every minor release (NPM upgrade that reduces dependency vulnerabilitie
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add eclipse-theia/theia --skill update-dependency -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add eclipse-theia/theia --skill update-dependency -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add eclipse-theia/theia --skill update-dependency -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add eclipse-theia/theia --skill update-dependency -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/eclipse-theia/theia/tree/HEAD/.agents/skills/update-dependencyFrom the publisher
Each tracked technology has its own folder under deps/ with a single GUIDE.md: the steps, the versions that move together, known issues and a log of past updates.
Read it before changing anything; it holds what earlier updates had to learn the hard way.
Not covered here: the VS Code API version, nls.metadata.json and built-in extensions (separate monthly update), and the default LLM models (update-default-models skill).
A technology without a folder: copy deps/_template and fill it as part of the update.
The release process around updates is documented in doc/Publishing.md (3.6 Update Major Dependencies, 3.7 NPM Upgrade, 3.8 Electron Update), the support policy in doc/runtime-policy.md and lockfile rules in doc/lockfile-maintenance.md. Link to them instead of repeating them.
release/x.y.x): the general workflow with the GUIDE of that technology.Runs after every minor release 1.x.0 (Publishing 3.6 to 3.8), on the branch the user has checked out (see Branches). Two PRs, one decision list.
git tag -l 'v1.x.0') and the checked-out branch contains it (git merge-base --is-ancestor v1.x.0 HEAD). Note the start commit (git rev-parse HEAD); all diffs of this run are against it. Read the last log entries of deps/npm-upgrade, deps/vulnerabilities and deps/electron, and the follow-ups of the previous NPM upgrade PR.npm audit and Dependabot). Show the user the counts and the list before changing anything.npm outdated) that need their own update.pr.md per PR, audit counts before/after, "Currently not fixable" with suggested follow-up issues, the 3.6 decision, and the Theia IDE follow-ups (Publishing 3.6/3.8 ticket with toDoWithRelease and dependencies labels).release/x.y.x) and whether it is a regular update or one to fix a vulnerable version.
For a release branch, find it with git branch -r --list 'origin/release/*' and check which one the user means.npm view <pkg>@<version> version); list newer patches of the same line.
Never assume a version exists: stop and ask if it does not.
Resolve the coupled versions listed in the GUIDE (e.g. the Node.js bundled with Electron).release/x.y.x backport), tell the user and wait for them to check it out.git grep -n '<old-version>' -- ':!CHANGELOG.md'.
For an exact version bump with unchanged transitive dependencies, edit package-lock.json by hand (version, resolved, integrity from npm view <pkg>@<version> dist.integrity) instead of regenerating it, and confirm the diff is only those lines.node scripts/verify-lockfile-platforms.js, npm ci, npm run lint, npm run build and the tests the GUIDE asks for, plus its manual smoke test.
If the environment cannot run a step (missing system libraries, no display), say which step was skipped and why; do not report it as passed.chore(<dependency>): upgrade <Name> from <old> to <new>, chore(deps): NPM upgrade after <version>), the body is a flat bullet list of what changed beyond the version.
Fill .github/PULL_REQUEST_TEMPLATE.md into a pr.md for the user; the PR base is the target branch.master or a release/* branch itself, uncommitted changes of someone else), say so and ask; do not fix it yourself.master, when checking diffs, so commits below the run do not count as changes.npm-upgrade-<version>, <dependency>-<version> (e.g. electron-44.9.1).SECURITY.md.CHANGELOG.md entry.© 2026 Skills Rack.
---name: update-dependencydescription: Update dependencies of the Theia framework and record what was learned. Its main use is the post-release…---# .agents/skills/update-dependency/SKILL.mdOverview
Update dependencies of the Theia framework and record what was learned. Its main use is the post-release dependency update after every minor release (NPM upgrade that reduces dependency vulnerabilities reported by npm audit and Dependabot, Electron update, Node.js/React check). Also covers single updates on demand (Electron, Monaco, TypeScript, Node.js, React, AI provider SDKs, vulnerable dependencies), on master or a `release/x.y.x` branch. Use when asked for the "post-release update", "npm upgrade", "update/upgrade/bump <dependency>", to reduce dependency vulnerabilities or npm audit findings, or to list outdated dependencies. Not for the VS Code API version bump.
FAQ
Download .agents/skills/update-dependency/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/eclipse-theia/theia.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.