quarkus-update

Compare Quarkus build files against reference projects and report upgrade differences.

30|10|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/quarkusio/skills --skill quarkus-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quarkus-update
Source: https://github.com/quarkusio/skills/tree/main/skills/quarkus-update
Command: npx skills add https://github.com/quarkusio/skills --skill quarkus-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you prevent outdated or mismatched Quarkus build configuration by checking your project against reference generator outputs and identifying the practical steps required to upgrade safely.

Core Features & Use Cases

  • Build tool and Quarkus version detection: Determines whether you use Maven, Gradle, or Gradle Kotlin DSL and extracts the Quarkus platform version to select the correct reference.
  • Reference comparison of build files: Compares your build configuration (BOM setup, plugin versions/configs, build properties, and wrapper presence/version signals) and reports meaningful differences.
  • Upgrade guidance with automation + context: Uses quarkus update --dry-run to explain what changes would be applied, then cross-checks generator structural changes to highlight what requires manual attention.

Quick Start

Use the quarkus-update skill to compare your Maven or Gradle Quarkus project's build files against the latest supported reference and receive an upgrade plan with both automated and manual change guidance.

Frequently Asked Questions about quarkus-update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upgrade my Quarkus project to the latest platform version?

Upgrading your Quarkus project involves detecting your build tool and current platform version, comparing your build files against reference-generated projects, and applying the resulting upgrade plan for both automated and manual changes.

What is the difference between an automated Quarkus update and a structural diff?

An automated Quarkus update uses the dry-run command to apply standard patches, while a generator structural diff identifies deeper configuration changes requiring manual attention to keep your build fully aligned with the latest reference.

Does the Quarkus update check work with both Maven and Gradle build configurations?

Yes, the Quarkus update check supports Maven, Gradle, and Gradle Kotlin DSL projects by detecting the build tool, extracting the Quarkus platform version, and comparing the relevant build files against the correct reference tag.

Why does my Quarkus build configuration show differences after a version upgrade?

Differences appear after a Quarkus version upgrade because the skill compares your build files against newer reference-generated projects to identify necessary changes in BOM setup, plugin versions, and build properties while ignoring user-specific application settings.

Can I see what changes will be applied before running a Quarkus version upgrade?

Yes, you can see changes before running a Quarkus version upgrade because the skill executes a dry-run to explain what automated patches would be applied and cross-checks generator structural changes to highlight manual follow-ups.

What are the limitations of using a reference comparison for Quarkus build updates?

The limitation of reference comparison for Quarkus build updates is that while it reports meaningful differences in build files and applies automated patches, complex structural changes still require manual intervention and cannot be fully automated.