Spring boot upgrade

Skill arconia-io/agent-skills/skills/spring-boot-upgrade

Upgrade Spring Boot, Spring AI, Arconia Framework, Gradle, or Maven versions using Arconia CLI. Use when the user wants to upgrade or update their project's framework version, migrate to a newer Spring Boot or Spring AI release, update the Gradle or Maven wrapper, or bring dependencies to their latest versions. Also use when the user mentions version migration, dependency upgrades, or keeping the project up to date.From its SKILL.md

Install

npx -y skills add arconia-io/agent-skills --skill spring-boot-upgrade

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
runs commandsInstructs the agent to run 8 commands, including `arconia update spring-boot --to-version=4.0 --dry-run` and 7 more.

What its file declares

Copied from the file, not written here

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.3 KB, 676 tokens by cl100k_base, as published. Nobody here has run it

Upgrade Frameworks and Build Tools

Use arconia update to upgrade frameworks and build tool wrappers. Each command runs a tested OpenRewrite migration recipe that handles dependency bumps, deprecated API replacements, configuration renames, and more.

Always commit your project to version control before running any upgrade so you can review the changes and revert if needed.

Available upgrade commands

Command	What it upgrades	`--to-version` default
`arconia update spring-boot`	Spring Boot	`4.0`
`arconia update spring-ai`	Spring AI	`2.0`
`arconia update framework`	Arconia Framework	`0.25`
`arconia update gradle`	Gradle wrapper	(latest)
`arconia update maven`	Maven wrapper	(latest)

Recommended workflow

Step 1: Preview changes with dry-run

Always preview before applying:

arconia update spring-boot --to-version=4.0 --dry-run

Review the output to understand what files will be modified.

Step 2: Apply the upgrade

arconia update spring-boot --to-version=4.0

Step 3: Verify the upgrade

arconia build
arconia test

If tests fail, review the changes in version control and fix any issues the automated migration could not handle.

Upgrade to a specific version

Use --to-version to target a specific release:

arconia update spring-boot --to-version=3.4
arconia update spring-ai --to-version=1.1
arconia update framework --to-version=0.24

Update build tool wrappers

Gradle and Maven wrapper updates do not take a --to-version flag — they update to the latest version automatically:

arconia update gradle
arconia update maven

These update gradle/wrapper/gradle-wrapper.properties or .mvn/wrapper/maven-wrapper.properties respectively.

Pass extra arguments to the build tool

arconia update spring-boot --to-version=4.0 -- --stacktrace

Gotchas

OpenRewrite modifies files in place. Always commit before upgrading so you can git diff the changes and revert with git checkout . if needed.
The --dry-run flag previews changes without modifying files. Always use it first, especially for major version upgrades.
Migration recipes handle most changes automatically (dependency versions, renamed APIs, configuration properties) but some manual adjustments may be needed after major upgrades. Always run tests after applying.
The --to-version flag is not available for arconia update gradle and arconia update maven — they always update to the latest version.
All upgrade commands use recipes from the Arconia Migrations project. For custom or additional recipes, use arconia rewrite run instead.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.