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

import kotlinx.validation.ApiValidationExtension
import kotlinx.validation.KotlinApiBuildTask
import kotlinx.validation.KotlinApiCompareTask

plugins {
  id("com.vanniktech.maven.publish.base")
  id("binary-compatibility-validator")
}

configure<MavenPublishBaseExtension> {
  publishToMavenCentral(automaticRelease = true)
  signAllPublications()
  pom {
    name.set(project.name)

~~ under the License.

 -----
 Introduction
 -----
 Hervé Boutemy
 -----
 2016-05-29
 -----

Maven Compat

 Maven2 classes maintained as compatibility layer for plugins that need to keep Maven2 compatibility.

 Plugins should avoid these classes and be updated to use only Maven3 dependencies (and require Maven3): see

 *
 * <p><b>Warning:</b> Using a specific character encoding when hashing a {@link CharSequence} with
 * {@link #putString(CharSequence, Charset)} is generally only useful for cross-language
 * compatibility (otherwise prefer {@link #putUnencodedChars}). However, the character encodings
 * must be identical across languages. Also beware that {@link Charset} definitions may occasionally
 * change between Java releases.
 *

---
- job:
    name: elastic+elasticsearch+%BRANCH%+multijob+platform-support-windows
    display-name: "elastic / elasticsearch # %BRANCH% - windows compatibility"
    description: "Elasticsearch %BRANCH% Windows compatibility testing.\n"
    project-type: matrix
    node: master
    # Use a hard-coded workspace directory to avoid hitting file path limits with auto-generated workspace path

/**
 * Plugin upgrade configuration for Maven 4 compatibility.
 * This record holds information about plugins that need to be upgraded
 * to specific minimum versions to work properly with Maven 4.
 *
 * @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
 * @param reason the reason why this plugin needs to be upgraded

        if (lmCompatibility == 3 || lmCompatibility == 4 || lmCompatibility == 5) {
            // For LM compatibility 3-5, only 16 bytes are used
            doAnswer(invocation -> {
                byte[] dest = invocation.getArgument(2);
                int offset = invocation.getArgument(3);
                System.arraycopy(new byte[16], 0, dest, offset, 16);
                return null;

        // add a lifecycle task to allow for a possible future additional rest compatibility without needing to change task names
        TaskProvider<Task> checkRestCompatTask = project.getTasks().register(REST_COMPAT_CHECK_TASK_NAME, (thisCheckTask) -> {
            thisCheckTask.setDescription("Runs all REST compatibility checks.");
            thisCheckTask.setGroup("verification");
        });

 * limitations under the License.
 */

import gradlebuild.basics.capitalize
import gradlebuild.pluginpublish.extension.PluginPublishExtension
import org.gradle.plugin.compatibility.compatibility
import java.time.Year

plugins {
    id("gradlebuild.module-identity")
    `maven-publish`
    signing
    `java-gradle-plugin`
    id("com.gradle.plugin-publish")
}

      - run: ./gradlew sanityCheck -DdisableLocalCache=true ${{ needs.build.outputs.sys-prop-args }}
      - name: Upload Compatibility Report
        if: always()
        uses: actions/upload-artifact@v7
        with:
          name: binary-compatibility-report
          path: testing/architecture-test/build/reports/binary-compatibility/report.html

  unit-test:
    name: "${{ matrix.bucket.name }} (Unit Test)"
    permissions: