Phase 4: Summarize & Validate

Load this file when executing Phase 4. Refer back to upgrade-success-criteria and upgrade-strategy for success criteria and strategy, and ../rules/troubleshooting.md when failures occur.

Create .github/java-upgrade/{RUN_ID}/summary.md from the Summary Template — replace placeholders and follow HTML-comment instructions to populate final results.
Apply the validation checklist from the Migration Guidelines:
- Migrated project passes compilation
- All tests pass — don't silently skip tests
- No legacy SDK dependencies/references exist
- If azure-sdk-bom is used, ensure no explicit version dependencies for Azure libraries in the BOM
- For each migration guide recorded during migration, fetch and verify the migrated code follows the guide's recommendations. Fix any deviations.
Populate summary.md (Upgrade Result, Tech Stack Changes, Commits, Challenges, Limitations, Next Steps)
Clean up temp files; remove HTML comments from all .md files
Verify all goals met

Third-party checks

No alerts15d3 checks · Risk SAFE

Gen Agent Trust Hub15d
This skill provides a structured framework for Azure workload upgrades and Java SDK modernization. It incorporates several security-focused practices, such as mandatory reviews to ensure the preservation of authentication and authorization controls during code migration. The skill utilizes standard development tools and follows official Microsoft guidance for Azure resource management.
Socket15d
No alerts
Snyk15d
Risk: LOW · No issues

/azure-upgrade