The GitHub Actions job "Forge - Next GCP Deploy" on grails-core.git/hotfix/forge-native-image-8.0.0-M1 has failed. Run started by GitHub user jamesfredley (triggered by jamesfredley).
Head commit for run: e61ffbc25ceb2216bdcc21a180125c7215f37944 / James Fredley <[email protected]> Fix forge dockerBuildNative class-initialization conflicts The Micronaut Gradle Application Plugin 4.6.2 transitively pulls the GraalVM Reachability Metadata Repository entry for ch.qos.logback at metadata-version 1.4.9, which marks the package as --initialize-at-build-time but does not cover the additional classes introduced in logback 1.5.x. The analytics module also forced org.postgresql.Driver to initialize at build time, which in turn pulled java.sql.DriverManager into build-time init. As a result dockerBuildNative failed with "* was unintentionally initialized at build time" errors for logback, slf4j, and DriverManager when deploying grails-forge to Cloud Run. Override the bundled logback metadata locally so logback 1.5.x and slf4j 2.x initialize at runtime, and rely on the official PostgreSQL GRM metadata (which covers 42.7.3 through 42.7.11) plus Micronaut SQL's runtime DriverManager registration instead of forcing build-time initialization for the postgres driver. Assisted-by: claude-code:claude-4.7-opus Report URL: https://github.com/apache/grails-core/actions/runs/25574621620 With regards, GitHub Actions via GitBox
