Source from repo

Azure Upgrade

Assess and upgrade Azure workloads between plans, tiers, or SKUs with automated migration steps

microsoftGitHub microsoftOfficialSource repo Original GitHub link Publisher page

Files

Skill

n/a

Size

156.9 KB

Entrypoint

SKILL.md

Format

git-repo

Open file

references/languages/java/rules/upgrade-strategy.md

Syntax-highlighted preview of this file as included in the skill package.

Rendered Source

markdown11 linesFree

references/languages/java/rules/upgrade-strategy.md

1# Upgrade Strategy
2 
3- **Incremental upgrades**: Stepwise dependency upgrades to avoid large jumps breaking builds.
4- **Minimal changes**: Only upgrade dependencies essential for compatibility with the modern Azure SDKs.
5- **Risk-first**: Handle EOL/challenging deps early in isolated steps.
6- **Necessary/Meaningful steps only**: Each step MUST change code/config. NO steps for pure analysis/validation. Merge small related changes. **Test**: "Does this step modify project files?"
7- **Automation tools**: Use automation tools like OpenRewrite for efficiency; always verify output. For BOM upgrades, run the [`scripts/upgrade_bom.py`](../scripts/upgrade_bom.py) script in the parent folder when Python 3.8+ is available; if Python is not available, follow the **Manual Fallback** sections in [bom-maven.md](../bom-migration/bom-maven.md) / [bom-gradle.md](../bom-migration/bom-gradle.md) instead (see [Migration Guidelines](../INSTRUCTION.md#maven-use-the-upgrade_bom-script)).
8- **Successor preference**: Compatible successor > Adapter pattern > Code rewrite.
9- **Build tool compatibility**: Check Maven/Gradle version compatibility with the project's JDK. Upgrade the build tool (including wrapper) if the current version does not support the JDK.
10- **Temporary errors OK**: Steps may pass with known errors if resolved later or pre-existing.
11

Loading source

Preparing the source view

Pulling the file list, source metadata, and syntax-aware rendering for this listing.

Marketplace

Source from repo

Azure Upgrade

Assess and upgrade Azure workloads between plans, tiers, or SKUs with automated migration steps

microsoftGitHub microsoftOfficialSource repo Original GitHub link Publisher page

Files

Skill

n/a

Size

156.9 KB

Entrypoint

SKILL.md

Format

git-repo

Open file

references/languages/java/rules/upgrade-strategy.md

Syntax-highlighted preview of this file as included in the skill package.

Rendered Source

markdown11 linesFree

references/languages/java/rules/upgrade-strategy.md

1# Upgrade Strategy
2 
3- **Incremental upgrades**: Stepwise dependency upgrades to avoid large jumps breaking builds.
4- **Minimal changes**: Only upgrade dependencies essential for compatibility with the modern Azure SDKs.
5- **Risk-first**: Handle EOL/challenging deps early in isolated steps.
6- **Necessary/Meaningful steps only**: Each step MUST change code/config. NO steps for pure analysis/validation. Merge small related changes. **Test**: "Does this step modify project files?"
7- **Automation tools**: Use automation tools like OpenRewrite for efficiency; always verify output. For BOM upgrades, run the [`scripts/upgrade_bom.py`](../scripts/upgrade_bom.py) script in the parent folder when Python 3.8+ is available; if Python is not available, follow the **Manual Fallback** sections in [bom-maven.md](../bom-migration/bom-maven.md) / [bom-gradle.md](../bom-migration/bom-gradle.md) instead (see [Migration Guidelines](../INSTRUCTION.md#maven-use-the-upgrade_bom-script)).
8- **Successor preference**: Compatible successor > Adapter pattern > Code rewrite.
9- **Build tool compatibility**: Check Maven/Gradle version compatibility with the project's JDK. Upgrade the build tool (including wrapper) if the current version does not support the JDK.
10- **Temporary errors OK**: Steps may pass with known errors if resolved later or pre-existing.
11