assertTrue(
                    description.toLowerCase().contains("compatibility")
                            || description.toLowerCase().contains("fix"),
                    "Description should mention compatibility or fix");
        }
    }

                if (hasIssues) {
                    context.success("Maven 4 compatibility issues fixed");
                    modifiedPoms.add(pomPath);
                } else {
                    context.success("No Maven 4 compatibility issues found");
                }
            } catch (Exception e) {
                context.failure("Failed to fix Maven 4 compatibility issues" + ": " + e.getMessage());
                errorPoms.add(pomPath);

            assertTrue("Rich report file doesn't exist", isFile)
        }

        return CheckResult(failure, scrapeRichReport(richReportFile), buildResult).apply {
            println(richReport.toText())
            block()
        }
    }

    /**

 *
 * <h3>All-in-One Option</h3>
 * The {@code --all} option is a convenience flag equivalent to {@code --model 4.1.0 --infer --fix-model --plugins}.
 * It performs a complete upgrade to Maven 4.1.0 with all optimizations, compatibility fixes, and plugin upgrades.
 *
 * <h3>Maven 4 Compatibility Fixes</h3>

     *       without any resolution. Files will be copied to this exact location.</li>
     * </ul>
     * <p>
     * <strong>Maven 3 Compatibility:</strong> This behavior maintains compatibility with Maven 3.x,
     * where resource {@code targetPath} elements were always interpreted as relative to the output directory

        /** The minimum version required for Maven 4 compatibility */
        final String minVersion;

        /**
         * Creates a new plugin upgrade information holder.
         *
         * @param groupId the Maven groupId of the plugin
         * @param artifactId the Maven artifactId of the plugin
         * @param minVersion the minimum version required for Maven 4 compatibility
         */

---
title: "Go, Backwards Compatibility, and GODEBUG"
layout: article
---

<!--
This document is kept in the Go repo, not x/website,
because it documents the full list of known GODEBUG settings,
which are tied to a specific release.
-->

## Introduction {#intro}

Go's emphasis on backwards compatibility is one of its key strengths.
There are, however, times when we cannot maintain complete compatibility.

            if (stage.specificBuilds.contains(SpecificBuild.SanityCheck)) {
                buildReportTab(
                    "API Compatibility Report",
                    "$HIDDEN_ARTIFACT_DESTINATION/report-architecture-test-binary-compatibility-report.html",
                )
                buildReportTab("Incubating APIs Report", "incubation-reports/all-incubating.html")
            }

            <option value="$PROJECT_DIR$/build-logic-settings/build-environment" />
            <option value="$PROJECT_DIR$/build-logic-settings/configuration-cache-compatibility" />
            <option value="$PROJECT_DIR$/build-logic/binary-compatibility" />
            <option value="$PROJECT_DIR$/build-logic/build-init-samples" />
            <option value="$PROJECT_DIR$/build-logic/build-update-utils" />

If your PR includes any changes to the Gradle Public API, it will cause the binary compatibility check to fail.
The binary compatibility check runs as a part of the broader sanity check.
The latter runs on every PR and is a prerequisite for merging.

If you run the sanity check locally with the `./gradlew sanityCheck`, you can see the binary compatibility error in the output.
It looks like the following:

```