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; 
however, after agreement you may open a separate backport PR to the target maintenance branch.
-->

# under the License.

_extends: maven-gh-actions-shared:.github/release-drafter.yml
tag-template: maven-$RESOLVED_VERSION

# Override replacers to strip backport branch prefixes and handle JIRA links
replacers:
  # Strip backport branch prefixes like [maven-4.0.x], [maven-3.x], etc.
  - search: '/^\[maven-[\d\.x-]+\]\s*-?\s*/g'
    replace: ''
  # Convert JIRA ticket references to links (but not maven branch prefixes)

# under the License.

_extends: maven-gh-actions-shared
tag-template: maven-$RESOLVED_VERSION

include-pre-releases: true
prerelease: true

# Override replacers to strip backport branch prefixes and handle JIRA links
replacers:
  # Strip backport branch prefixes like [maven-4.0.x], [maven-3.x], etc.
  - search: '/^\[maven-[\d\.x-]+\]\s*-?\s*/g'
    replace: ''
  # Convert JIRA ticket references to links (but not maven branch prefixes)

{
  "upstream": "elastic/elasticsearch",
  "targetBranchChoices": [
    { "name": "master", "checked": true },
    { "name": "7.x", "checked": true },
    "7.15",
    "7.14",
    "6.8"
  ],
  "targetPRLabels": ["backport"],
  "branchLabelMapping": {
    "^v8.0.0$": "master",
    "^v7.16.0$": "7.x",
    "^v(\\d+).(\\d+).\\d+$": "$1.$2"
  }

| [Conscrypt]      | ✅      | ✅           | [BoringSSL]     | Activated if Conscrypt is first registered provider.         |
| [OpenJSSE]       |         | ✅           | [OpenJDK]       | OpenJDK backport.                                            |
| [Corretto]       | ✅      | ✅           | [OpenSSL]       | Amazon's high-performance provider. [Tracking bug.][bug5592] |

All providers support HTTP/1.1 and TLSv1.2.

- If submitting code, is your pull request against master? Unless there is a good reason otherwise, we prefer pull requests against master and will backport as needed.
- If submitting code, have you checked that your submission is for an [OS and architecture that we support](https://www.elastic.co/support/matrix#show_os)?

    return new SerializedForm<V>(map);
  }

  @GwtIncompatible
  @J2ktIncompatible
  /*
   * The mainline copy of ImmutableMapValues doesn't produce this serialized form anymore, though
   * the backport does. For now, we're keeping the class declaration in *both* flavors so that both
   * flavors can read old data or data from the other flavor. However, we strongly discourage

        return true;
      }
    }
  }

  @Override
  public int size() {
    return size;
  }

  // We're careful to put only E instances into the array in the mainline.
  // (In the backport, we don't need this suppression, but we keep it to minimize diffs.)
  @SuppressWarnings("unchecked")
  @Override
  public UnmodifiableIterator<E> iterator() {
    return asList().iterator();
  }

  @Override

        return true;
      }
    }
  }

  @Override
  public int size() {
    return elements.length;
  }

  // We're careful to put only E instances into the array in the mainline.
  // (In the backport, we don't need this suppression, but we keep it to minimize diffs.)
  @SuppressWarnings("unchecked")
  @Override
  public UnmodifiableIterator<E> iterator() {
    return (UnmodifiableIterator<E>) Iterators.forArray(elements);

    return super.writeReplace();
  }

  @GwtIncompatible
  @J2ktIncompatible
  /*
   * The mainline copy of ImmutableMapValues doesn't produce this serialized form anymore, though
   * the backport does. For now, we're keeping the class declaration in *both* flavors so that both
   * flavors can read old data or data from the other flavor. However, we strongly discourage