Update Micronaut platform versions

[jamesfredley]

Summary

Update the Micronaut-related release dependencies for the Grails 8 line and keep the Forge metadata aligned with the Micronaut platform it actually builds against.

This addresses the release-audit follow-up around Micronaut platform promotion and stale dependency metadata:

• Grails-Micronaut moves from Micronaut platform 5.0.0 to 5.0.3.
• Grails Forge stays on the Micronaut 4 line and updates its embedded platform metadata to 4.10.16.
• The Micronaut-tied BOM dependency sets add explicit ASM 9.10.1 constraints required by dependency validation.
• Forge generator expectations are updated to match the emitted Micronaut platform version.

Why

The pre-release review called out Micronaut dependency promotion and stale BOM/Forge metadata as release-readiness cleanup. Keeping the root Grails-Micronaut island, Forge properties, generated Forge POM metadata, and validation constraints in sync avoids a release where generated apps or BOM checks disagree with the versions the build is actually using.

Verification

• ./gradlew validateDependencyVersions -PincludeMicronautProjects
• ./gradlew :grails-micronaut:compileGroovy -PincludeMicronautProjects
• ./gradlew :grails-forge:processResources
• CI completed all checks for the branch; TestLens reported all tests passed, with one Windows shell CLI test flake rerun noted as unrelated.

Note

Targeted Forge tests were attempted but blocked by the existing unrelated grails-data-graphql static compilation failure in the current 8.0.x tree.

[Copilot]

Pull request overview

Updates Micronaut platform versions across the Grails/Micronaut “island” and Grails Forge, and introduces explicit ASM version constraints to satisfy dependency version validation for Micronaut-related BOMs.

Changes:

• Bumps Grails-Micronaut Micronaut platform version from 5.0.0 to 5.0.3 (root build).
• Keeps Grails Forge on Micronaut platform 4.10.16 and updates the corresponding Forge test expectation.
• Adds explicit org.ow2.asm:asm / org.ow2.asm:asm-util constraints (version 9.10.1) into the Micronaut-tied BOM dependency sets to support dependency validation.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
grails-forge/test-core/src/test/groovy/org/grails/forge/create/CreateAppSpec.groovy	Updates Forge generator test to expect Micronaut platform 4.10.16.
grails-forge/grails-forge-core/src/main/resources/pom.xml	Updates Forge’s embedded Micronaut platform BOM reference to 4.10.16.
grails-forge/gradle.properties	Updates Forge’s Micronaut version property to 4.10.16.
gradle.properties	Updates Grails-Micronaut Micronaut platform version to 5.0.3.
dependencies.gradle	Adds ASM version + dependency entries needed for dependency version validation in Micronaut BOM contexts.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 49.5691%. Comparing base (c88070e) to head (d7a84ac).

Additional details and impacted files

@@                Coverage Diff                 @@
##                8.0.x     #15825        +/-   ##
==================================================
- Coverage     49.5810%   49.5691%   -0.0119%     
+ Complexity      16695      16689         -6     
==================================================
  Files            1947       1947                
  Lines           92598      92598                
  Branches        16179      16179                
==================================================
- Hits            45911      45900        -11     
- Misses          39589      39597         +8     
- Partials         7098       7101         +3     

see 3 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[testlens-app]

🚨 TestLens detected 5 failed tests 🚨

Here is what you can do:

1. Inspect the test failures carefully.
2. If you are convinced that some of the tests are flaky, you can mute them below.
3. Finally, trigger a rerun by checking the rerun checkbox.

Test Summary

CI - Groovy Joint Validation Build / build_grails > :grails-test-examples-gorm:integrationTest

Test	Runs
DirtyCheckBindingSpec > an explicit bindable:true id constraint declared on a @DirtyCheck base is inherited and binds over HTTP	❌

CI / Build Grails-Core (windows-latest, 25) > :grails-shell-cli:test

Test	Runs
RunningApplicationProcessSpec > stop terminates a running process and removes the PID file	❌

CI / Functional Tests (Java 21, indy=false) > :grails-test-examples-gorm:integrationTest

Test	Runs
DirtyCheckBindingSpec > an explicit bindable:true id constraint declared on a @DirtyCheck base is inherited and binds over HTTP	❌

CI / Functional Tests (Java 21, indy=true) > :grails-test-examples-gorm:integrationTest

Test	Runs
DirtyCheckBindingSpec > an explicit bindable:true id constraint declared on a @DirtyCheck base is inherited and binds over HTTP	❌

CI / Functional Tests (Java 25, indy=false) > :grails-test-examples-gorm:integrationTest

Test	Runs
DirtyCheckBindingSpec > an explicit bindable:true id constraint declared on a @DirtyCheck base is inherited and binds over HTTP	❌

🏷️ Commit: 19a8f59
▶️ Tests: 39320 executed
⚪️ Checks: 44/44 completed

Test Failures

RunningApplicationProcessSpec > stop terminates a running process and removes the PID file (:grails-shell-cli:test in CI / Build Grails-Core (windows-latest, 25))

Condition not satisfied:

!process.isAlive()
||       |
||       true
|Process[pid=9556, exitValue=1]
false

	at org.grails.cli.gradle.RunningApplicationProcessSpec.stop terminates a running process and removes the PID file(RunningApplicationProcessSpec.groovy:217)

DirtyCheckBindingSpec > an explicit bindable:true id constraint declared on a @DirtyCheck base is inherited and binds over HTTP (:grails-test-examples-gorm:integrationTest in CI / Functional Tests (Java 21, indy=false))

groovy.lang.MissingPropertyException: No such property: FORM for class: gorm.DirtyCheckBindingSpec
	at gorm.DirtyCheckBindingSpec.an explicit bindable:true id constraint declared on a @DirtyCheck base is inherited and binds over HTTP(DirtyCheckBindingSpec.groovy:83)

DirtyCheckBindingSpec > an explicit bindable:true id constraint declared on a @DirtyCheck base is inherited and binds over HTTP (:grails-test-examples-gorm:integrationTest in CI / Functional Tests (Java 21, indy=true))

groovy.lang.MissingPropertyException: No such property: FORM for class: gorm.DirtyCheckBindingSpec
	at gorm.DirtyCheckBindingSpec.an explicit bindable:true id constraint declared on a @DirtyCheck base is inherited and binds over HTTP(DirtyCheckBindingSpec.groovy:83)

DirtyCheckBindingSpec > an explicit bindable:true id constraint declared on a @DirtyCheck base is inherited and binds over HTTP (:grails-test-examples-gorm:integrationTest in CI / Functional Tests (Java 25, indy=false))

groovy.lang.MissingPropertyException: No such property: FORM for class: gorm.DirtyCheckBindingSpec
	at gorm.DirtyCheckBindingSpec.an explicit bindable:true id constraint declared on a @DirtyCheck base is inherited and binds over HTTP(DirtyCheckBindingSpec.groovy:83)

DirtyCheckBindingSpec > an explicit bindable:true id constraint declared on a @DirtyCheck base is inherited and binds over HTTP (:grails-test-examples-gorm:integrationTest in CI - Groovy Joint Validation Build / build_grails)

groovy.lang.MissingPropertyException: No such property: FORM for class: gorm.DirtyCheckBindingSpec
	at gorm.DirtyCheckBindingSpec.an explicit bindable:true id constraint declared on a @DirtyCheck base is inherited and binds over HTTP(DirtyCheckBindingSpec.groovy:83)

Muted Tests

Select tests to mute in this pull request:

• DirtyCheckBindingSpec > an explicit bindable:true id constraint declared on a @DirtyCheck base is inherited and binds over HTTP
• RunningApplicationProcessSpec > stop terminates a running process and removes the PID file

Reuse successful test results:

• ♻️ Only rerun the tests that failed or were muted before

Click the checkbox to trigger a rerun:

• Rerun jobs

---

Learn more about TestLens at testlens.app.