- [Server binaries](#server-binaries-7)
    - [Node binaries](#node-binaries-7)
  - [Changelog since v1.17.8](#changelog-since-v1178)
  - [Urgent Upgrade Notes](#urgent-upgrade-notes)
    - [(No, really, you MUST read this before you upgrade)](#no-really-you-must-read-this-before-you-upgrade)
  - [Changes by Kind](#changes-by-kind-8)
    - [Bug or Regression](#bug-or-regression-7)
  - [Dependencies](#dependencies-8)
    - [Added](#added-8)

This way, in case there was a breaking change for your code in one of the releases, you can still benefit from the previous upgrades. ✨

### Breaking Changes - Upgrade

* ⬆️ Upgrade Starlette to 0.16.0. PR [#4016](https://github.com/tiangolo/fastapi/pull/4016) by [@tiangolo](https://github.com/tiangolo).

Also upgrades the ranges of optional dependencies:

* `"jinja2 >=2.11.2,<4.0.0"`
* `"itsdangerous >=1.1.0,<3.0.0"`

## Changelog since v1.28.0

## Urgent Upgrade Notes 

### (No, really, you MUST read this before you upgrade)

    - [Server binaries](#server-binaries-2)
    - [Node binaries](#node-binaries-2)
  - [Changelog since v1.16.12](#changelog-since-v11612)
  - [Urgent Upgrade Notes](#urgent-upgrade-notes)
    - [(No, really, you MUST read this before you upgrade)](#no-really-you-must-read-this-before-you-upgrade)
  - [Changes by Kind](#changes-by-kind-2)
    - [Bug or Regression](#bug-or-regression-2)
  - [Dependencies](#dependencies-2)
    - [Added](#added-2)

# shellcheck disable=SC2120
cleanup() {
	MINIO_VERSION=dev /tmp/gopath/bin/docker-compose \
		-f "buildscripts/upgrade-tests/compose.yml" \
		down || true

	MINIO_VERSION=dev /tmp/gopath/bin/docker-compose \
		-f "buildscripts/upgrade-tests/compose.yml" \
		rm || true

	for volume in $(docker volume ls -q | grep upgrade); do
		docker volume rm ${volume} || true
	done

	docker volume prune -f
	docker system prune -f || true

name: Upgrade to latest wrapper

on:
  schedule:
    - cron: '0 4 * * *'
  workflow_dispatch:

permissions:
  contents: write

jobs:
  upgrade-latest-wrapper:
    runs-on: ubuntu-latest

    if: github.repository == 'gradle/gradle'

    steps:
      - name: Checkout repository
        uses: actions/checkout@v6
        with:
          ref: devprod/upgrade-to-latest-wrapper
          token: ${{ secrets.GITHUB_TOKEN }}

---
- job:
    name: elastic+elasticsearch+%BRANCH%+multijob+packaging-tests-upgrade
    display-name: "elastic / elasticsearch # %BRANCH% - packaging upgrade tests"
    description: "Testing of the Elasticsearch %BRANCH% branch packaging test upgrade support matrix.\n"
    project-type: matrix
    node: master
    scm:
      - git:
          wipe-workspace: false
    axes:
      - axis:
          type: label-expression
          name: os

 *   <li>{@link org.apache.maven.cling.invoker.mvnup.goals.Apply} - Applies upgrades to project files</li>
 *   <li>{@link org.apache.maven.cling.invoker.mvnup.goals.Help} - Displays usage information</li>
 * </ul>
 *
 * <h3>Upgrade Strategies</h3>
 * <p>The tool uses a strategy pattern to handle different types of upgrades:</p>
 * <ul>

---
- job:
    name: "elastic+elasticsearch+pull-request+packaging-upgrade-tests"
    display-name: "elastic / elasticsearch - pull request packaging-upgrade-tests"
    description: "Testing of Elasticsearch pull requests - packaging-upgrade-tests"
    project-type: matrix
    node: master
    child-workspace: "/dev/shm/elastic+elasticsearch+pull-request+packaging-upgrade-tests"
    scm:
      - git:

        context.info("Maven Upgrade Tool - Help");
        context.println();
        context.info("Upgrades Maven projects to be compatible with Maven 4.");
        context.println();
        context.info("Available goals:");
        context.indent();
        context.info("help  - display this help message");
        context.info("check - check for available upgrades");