maven-3.8.x: {}
    maven-3.0.x: {}
    maven-2.2.x: {}
    pre-reset-master: {}
  features:
    issues: true
notifications:
  commits: commits@maven.apache.org
  issues: issues@maven.apache.org

- master — default target for all changes (new features + bug fixes).  
  If the change should also go to maven-4.0.x, request a backport in the PR.

- maven-3.10.x — target for 3.x changes (new features + bug fixes).  
  If the change should also go to maven-3.9.x, request a backport in the PR.
  maven-3.9.x should receive only serious bug fixes, as it is approaching EOL.

Backports are typically handled by maintainers; 

      - name: 'Check out repository'
        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
      # When we specify multiple JDKs, the final one becomes the default, which is used to execute Maven itself.
      # Our Maven configuration then specifies different JDKs to use for some of the steps:

ksp = { id = "com.google.devtools.ksp", version.ref = "ksp" }
gradle-lint = { id = "com.android.lint", version.ref = "lint-gradle" }
maven-publish = { id = "com.vanniktech.maven.publish.base", version.ref = "maven-publish" }
maven-sympathy = { id = "io.github.usefulness.maven-sympathy", version.ref = "maven-sympathy" }
mrjar = { id = "me.champeau.mrjar", version.ref = "mrjar" }
shadow = { id = "com.gradleup.shadow", version.ref = "shadow-plugin" }