- [Server binaries](#server-binaries-12)
    - [Node binaries](#node-binaries-12)
  - [Changelog since v1.18.5](#changelog-since-v1185)
  - [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-13)
    - [API Change](#api-change-2)
    - [Bug or Regression](#bug-or-regression-12)

### Fixes

* 🎨 Fix types for lifespan, upgrade Starlette to 0.26.1. PR [#9245](https://github.com/tiangolo/fastapi/pull/9245) by [@tiangolo](https://github.com/tiangolo).

## 0.94.0 (2023-03-10)

### Upgrades

* ⬆ Upgrade python-multipart to support 0.0.6. PR [#9212](https://github.com/tiangolo/fastapi/pull/9212) by [@musicinmybrain](https://github.com/musicinmybrain).

        help.execute(context);

        // Verify that the plugins option is mentioned in the help output
        Mockito.verify(context.logger).info("      --plugins         Upgrade plugins known to fail with Maven 4");
    }

    @Test
    void testHelpIncludesAllOption() throws Exception {
        UpgradeContext context = createMockContext();

        help.execute(context);

                        .thenReturn(UpgradeResult.empty());

                applyGoal.execute(context);

                // Verify that the Apply-specific header is logged
                verify(context.logger).info("Maven Upgrade Tool - Apply");
            } finally {
                // Clean up - delete all files in the directory first
                try {
                    Files.walk(tempDir)

fi

# Install pip
wget --retry-connrefused --waitretry=1 --read-timeout=20 --timeout=15 --tries=5 https://bootstrap.pypa.io/get-pip.py
/usr/bin/$VERSION get-pip.py
/usr/bin/$VERSION -m pip install --no-cache-dir --upgrade pip
/usr/bin/$VERSION -m pip install -U setuptools


# For Python 3.13t, do not install twine as it does not have pre-built wheels
# for this Python version and building it from source fails. We only need twine

import org.apache.maven.cling.invoker.mvnup.UpgradeInvoker;
import org.apache.maven.cling.invoker.mvnup.UpgradeParser;
import org.codehaus.plexus.classworlds.ClassWorld;

/**
 * Maven upgrade CLI "new-gen".
 */
public class MavenUpCling extends ClingSupport {
    /**
     * "Normal" Java entry point. Note: Maven uses ClassWorld Launcher and this entry point is NOT used under normal
     * circumstances.

See also <<release-highlights>> and <<es-release-notes>>.
<% if (isElasticsearchSnapshot) { %>
coming[${version}]
<% } %>
//NOTE: The notable-breaking-changes tagged regions are re-used in the
//Installation and Upgrade Guide
<% if (breakingChangesByNotabilityByArea.isEmpty() == false) { %>
[discrete]
[[breaking-changes-${majorDotMinor}]]
=== Breaking changes

The following changes in {es} ${majorDotMinor} might affect your applications

        TYPE_LABELS.put("feature", "New features");
        TYPE_LABELS.put("new-aggregation", "New aggregation");
        TYPE_LABELS.put("regression", "Regressions");
        TYPE_LABELS.put("upgrade", "Upgrades");
    }

    static void update(File templateFile, File outputFile, Map<QualifiedVersion, Set<ChangelogEntry>> changelogs) throws IOException {
        final String templateString = Files.readString(templateFile.toPath());

            "deprecation",
            "enhancement",
            "feature",
            "known-issue",
            "new-aggregation",
            "regression",
            "security",
            "upgrade"
          ]
        },
        "summary": {
          "type": "string",
          "minLength": 1
        },
        "highlight": {
          "$ref": "#/definitions/Highlight"
        },

- kubeadm: `kubeadm upgrade node` now supports `addon` and `post-upgrade` phases. Users can use `kubeadm upgrade node phase addon` to execute the addon upgrade, or use `kubeadm upgrade node --skip-phases addon` to skip the addon upgrade. If you were previously skipping an addon subphase on `kubeadm init` you should now skip the same addon when calling `kubeadm upgrade apply` and `kubeadm upgrade node`. Currently, the `post-upgrade` phase is no-op, and it is mainly used to handle some release-specific...