unity-idm/unity / .agents/skills/update-dependencies
update-dependencies
VerifiedUpdate Maven dependency and build-plugin versions in the Unity root POM, either as one bulk patch/revision update or as an interactive full update with per-library minor/major choices, including staged Vaadin upgrades with release-note-driven compatibility work. Use when asked to discover, apply, build, and commit dependency updates in a Unity checkout.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.2 KB |
| agents/openai.yaml | config | 213 B |
| references/dependency-policy.md | markdown | 854 B |
| references/full-mode.md | markdown | 3.1 KB |
| references/patch-mode.md | markdown | 2.9 KB |
| references/vaadin-updates.md | markdown | 6.3 KB |
| scripts/maven_metadata_candidates.pyexecutable | script | 4.6 KB |
SKILL.md
View on GitHub---
name: update-dependencies
description: >-
Update Maven dependency and build-plugin versions in the Unity root POM, either as one bulk patch/revision update
or as an interactive full update with per-library minor/major choices, including staged Vaadin upgrades with
release-note-driven compatibility work. Use when asked to discover, apply, build, and commit dependency updates
in a Unity checkout.
---
# Update Dependencies
Update dependency and build-plugin versions declared by the master `pom.xml`. Use Maven's Versions Plugin to
discover versions, make exact and reviewable POM edits, run the repository's full build, and commit only a
successful result.
## Choose the mode
- **Patch** or **revision** mode updates every eligible incremental version in bulk and creates one commit.
- **Full** mode includes the bulk patch pass, then asks which eligible libraries should receive a minor or major
update before creating one commit.
- A dedicated **Vaadin** update uses the staged workflow in
[references/vaadin-updates.md](references/vaadin-updates.md).
Infer the mode from the request. If it is not explicit, ask the user to choose patch/revision or full mode before
changing files. Discovery may happen before that question because it is read-only.
For patch/revision mode, read [references/patch-mode.md](references/patch-mode.md). For full mode, read all of:
- [references/patch-mode.md](references/patch-mode.md)
- [references/full-mode.md](references/full-mode.md)
- [references/dependency-policy.md](references/dependency-policy.md)
For any Vaadin candidate in any mode, also read
[references/vaadin-updates.md](references/vaadin-updates.md). This includes Vaadin patch candidates found during a
bulk patch pass.
## Guardrails
- Work from the checkout root containing the master `pom.xml`; read and follow its `AGENTS.md` first.
- Require a ticket ID before applying dependency updates. Discovery may run without one, but do not edit files until
the user supplies the ID.
- Inspect `git status --short` before editing. Preserve unrelated work and never stage it. If `pom.xml` already has
user changes, inspect them and stop for clarification when the skill's edits cannot be isolated safely.
- Scope automated version edits to the root `pom.xml`. Use Maven with `-N` for version discovery so module POMs are
not processed. Never change the Unity project version, reactor-module versions, or parent coordinates as part of
dependency updating.
- Use release versions only. Honor the root POM's Versions Plugin configuration and `version-rules.xml`; do not
bypass ignored-version rules merely to reach a newer number.
- For Vaadin, use only freely usable releases. Never select or retain a release that Vaadin identifies as
commercial or that requires a paid Vaadin license for building or running the application. This requirement is
unconditional, applies in every mode, and cannot be overridden by a request for the "latest" version. Resolve the
newest free release and perform non-patch upgrades as specified in `references/vaadin-updates.md`.
- Treat one version property or BOM as one logical library even when it controls several artifacts. Deduplicate
property, dependency, and plugin report entries before editing or prompting.
- Interpret patch/minor/major using Maven's version comparison and the existing version line. If a version scheme is
ambiguous, do not guess; identify that candidate and ask for clarification.
- Apply only exact versions reported by Maven. Inspect `git diff -- pom.xml` after edits and remove any unintended
changes before building.
- A dependency update can include the smallest source and test adaptations required by the selected versions, but
do not expand into unrelated refactoring.
## Build and commit
Run the full repository build with tests after the complete update set is ready:
```bash
mvn -T 1C clean install -Dunity.selenium.opts=--headless=new -Dgpg.skip=true > "$dep_update_tmp/build.log" 2>&1
```
Create `dep_update_tmp` with `mktemp -d` earlier in the run. While the build runs, keep the user informed at least
once per minute. On failure, inspect the saved log, find the root cause, and fix update-caused compatibility or test
problems within scope. Do not commit while the required build fails. Preserve the log while it is useful, then
remove the verified temporary directory created for this run.
Before committing, run `git diff --check`, inspect the complete diff, and stage explicit attributable paths only;
never use `git add -A`. Create exactly one commit for the completed update set unless the user requested a different
split. Each staged Vaadin minor or major hop is a separate update set and therefore gets its own successful build
and commit. Prefix every commit subject with the required ticket ID followed by one space and a concise imperative
subject, without a colon (for example, `UY-1601 Update Jackson dependencies`). If Maven finds no eligible updates,
do not build or create an empty commit; report that the POM is current for the selected mode.
Finish by reporting the old-to-new versions, skipped and manual-only candidates, build result, and commit hash. For
Vaadin, also report the release, upgrade, and changelog URLs reviewed and summarize the compatibility adaptations.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |