agentleFS
Sign inStart free
rrezartprebrezarrezartprebreza/spring-boot-skills/skills/spring-boot-3/spring-boot-migration/SKILL.md

spring-boot-migration

Skill344 starsChanged 3 months agoMITView on GitHub

Use when preparing a Spring Boot 3 application for Boot 4, upgrading to Boot 3.5 first, removing deprecated APIs, auditing dependencies, or planning a staged Framework 7 migration.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 8 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run unit, slice, integration, startup, and migration tests before changing the major version.

    line 15
  2. Distinctive:

    Remove Boot 3 deprecations and record all explicitly versioned dependencies.

    line 16
  3. Distinctive:

    Verify Spring Cloud and other portfolio release-train compatibility independently.

    line 18
  4. Distinctive:

    Remove Undertow assumptions.

    line 24
  5. Very specific:

    Add spring-boot-properties-migrator temporarily after changing the Boot version, then remove it.

    line 27
  6. Distinctive:

    Use the classic starters only as a temporary diagnostic bridge, never as the final dependency model.

    line 33
  7. Distinctive:

    Run the application with every supported profile.

    line 37
  8. Distinctive:

    Verify JSON contracts, security failures, pagination, and error responses.

    line 39
  9. Distinctive:

    Remove the properties migrator and all classic starters before declaring the migration complete.

    line 41

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Spring Boot 3 to 4 Migration

Migrate in controlled stages. Keep behavior changes separate from the framework upgrade.

Establish the baseline

  1. Upgrade to the latest Boot 3.5 maintenance release.
  2. Run unit, slice, integration, startup, and migration tests before changing the major version.
  3. Remove Boot 3 deprecations and record all explicitly versioned dependencies.
  4. Compare the Boot 3.5 and Boot 4 dependency-management reports.
  5. Verify Spring Cloud and other portfolio release-train compatibility independently.

Prepare for Boot 4

  • Require Java 17 or newer; prefer Java 21 for application builds.
  • Replace javax.* remnants with Jakarta APIs before the upgrade.
  • Remove Undertow assumptions; Boot 4 requires a Servlet 6.1-compatible container.
  • Inventory Jackson 2 custom modules, serializers, ObjectMapper beans, and package imports.
  • Inventory test annotations, especially @MockBean, @SpyBean, and implicit MockMvc setup.
  • Add spring-boot-properties-migrator temporarily after changing the Boot version, then remove it.

Migrate dependencies deliberately

Boot 4 is more modular. Prefer dedicated starters over relying on incidental transitive dependencies. Expect dedicated starters for web MVC, security tests, Flyway/Liquibase, and technology-specific tests. Use the classic starters only as a temporary diagnostic bridge, never as the final dependency model.

Verify the result

  • Run the application with every supported profile.
  • Exercise schema migration against a production-like database copy.
  • Verify JSON contracts, security failures, pagination, and error responses.
  • Confirm actuator exposure, logging, metrics, and tracing behavior.
  • Remove the properties migrator and all classic starters before declaring the migration complete.

Examples

  • See examples/good-migration-plan.md for a staged migration.
  • See examples/bad-migration-plan.md for a risky one-step upgrade.

Gotchas

  • Agent jumps from an old Boot 3 minor directly to Boot 4 - upgrade to current 3.5 first.
  • Agent changes framework versions and business behavior together - isolate the migration diff.
  • Agent assumes all Boot 3 starters keep the same names and transitive dependencies - audit each one.
  • Agent leaves spring-boot-properties-migrator in production - remove it after configuration cleanup.
  • Agent treats passing compilation as completion - verify runtime wiring, JSON, security, and tests.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free