*
     * @return an {@link Optional} containing the directory path, or empty if not specified
     */
    @Nonnull
    Optional<String> directory();

    /**
     * Should use inference when upgrading (remove redundant information).
     *
     * @return an {@link Optional} containing the boolean value {@code true} if specified, or empty
     */
    @Nonnull
    Optional<Boolean> infer();

    /**

```

Breaking changes and new features are added in "MINOR" versions.

/// tip

The "MINOR" is the number in the middle, for example, in `0.2.3`, the MINOR version is `2`.

///

## Upgrading the FastAPI versions { #upgrading-the-fastapi-versions }

You should add tests for your app.

With **FastAPI** it's very easy (thanks to Starlette), check the docs: [Testing](../tutorial/testing.md){.internal-link target=_blank}

 * under the License.
 */

/**
 * Provides the API for the Maven Upgrade tool ({@code mvnup}).
 *
 * <p>This package contains interfaces and classes for the Maven upgrade tool,
 * which provides functionality for upgrading Maven projects and dependencies.</p>
 *
 * <p>Key features include:</p>
 * <ul>
 *   <li>Project upgrade capabilities</li>
 *   <li>Dependency version management</li>
 *   <li>Configuration migration</li>

Upgrading to OkHttp 4
=====================

OkHttp 4.x upgrades our implementation language from Java to Kotlin and keeps everything else the
same. We’ve chosen Kotlin because it gives us powerful new capabilities while integrating closely
with Java.

We spent a lot of time and energy on retaining strict compatibility with OkHttp 3.x. We’re even
keeping the package name the same: `okhttp3`!

There are three kinds of compatibility we’re tracking:

  - 'Works with OkHttp': works_with_okhttp.md
  - 'API': 5.x/okhttp/okhttp3/
  - 'Change Logs':
    - 'Change Log': changelogs/changelog.md
    - '4.x Change Log': changelogs/changelog_4x.md
    - 'Upgrading to OkHttp 4': changelogs/upgrading_to_okhttp_4.md
    - '3.x Change Log': changelogs/changelog_3x.md
    - '2.x Change Log': changelogs/changelog_2x.md
    - '1.x Change Log': changelogs/changelog_1x.md
  - 'Contributing':

## Upgrading MinIO

Upgrades require zero downtime in MinIO, all upgrades are non-disruptive, all transactions on MinIO are atomic. So upgrading all the servers simultaneously is the recommended way to upgrade MinIO.

> [!NOTE]

failed_count_site2=$(./s3-check-md5 -versions -access-key minioadmin -secret-key minioadmin -endpoint http://site2-nginx:9002 -bucket testbucket 2>&1 | grep FAILED | wc -l)

## we do not need to fail here, since we are going to test
## upgrading to master, healing and being able to recover
## the last version.
if [ $failed_count_site1 -ne 0 ]; then
	echo "failed with multipart on site1 uploads ${failed_count_site1}"
fi

if [ $failed_count_site2 -ne 0 ]; then

Якщо у Вас стара версія, при спробі використати `Annotated` можуть виникати помилки.

Переконайтеся, що Ви [оновили версію FastAPI](../deployment/versions.md#upgrading-the-fastapi-versions){.internal-link target=_blank} принаймні до версії 0.95.1 перед використанням `Annotated`.

///

## Оголошення метаданих

Ви можете оголошувати всі ті ж параметри, що і для `Query`.

allowing flexibility in the independent management of root accounts across sites and the ability to disable root accounts eventually.

However, this means that STS tokens signed previously by root credentials will no longer be valid upon upgrading to the latest version with this change. Please re-generate them as you usually do. Additionally, if site replication is ever removed - the STS tokens will become invalid, regenerate them as you usually do....

    - [Other notable changes](#other-notable-changes-9)
- [v1.3.0](#v130)
  - [Downloads](#downloads-9)
  - [Highlights](#highlights)
  - [Known Issues and Important Steps before Upgrading](#known-issues-and-important-steps-before-upgrading)
      - [ThirdPartyResource](#thirdpartyresource)
      - [kubectl](#kubectl)
      - [kubernetes Core Known Issues](#kubernetes-core-known-issues)