* «query parameter»: «paramètre de requête»

* «the `Request`»: «`Request`» (keep as code identifier)
* «the `Response`»: «`Response`» (keep as code identifier)

* «deployment»: «déploiement»
* «to upgrade»: «mettre à niveau»

* «deprecated»: «déprécié»
* «to deprecate»: «déprécier»

* «cheat sheet»: «aide-mémoire»

        return builder(Tools.MVNSHELL_CMD, Tools.MVNSHELL_NAME, args, messageBuilderFactory);
    }

    /**
     * Creates a new Builder instance for constructing a Maven Upgrade Tool ParserRequest.
     *
     * @param args the command-line arguments
     * @param messageBuilderFactory the factory for creating message builders
     * @return a new Builder instance
     */
    @Nonnull

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}

After you have tests, then you can upgrade the **FastAPI** version to a more recent one, and make sure that all your code is working correctly by running your tests.

 * under the License.
 */
package org.apache.maven.cling.invoker.mvnup;

import java.nio.charset.Charset;

import org.jline.terminal.Terminal;

/**
 * Console icons for Maven upgrade tool output.
 * Each icon has a Unicode character and an ASCII fallback.
 * The appropriate representation is chosen based on the terminal's charset capabilities.
 */
public enum ConsoleIcon {
    /**

 * for exclusive consumption by the repository system and is opaque to the cache implementation.
 *
 */
@Deprecated
//
// Used by Tycho and will break users and force them to upgrade to Maven 3.1 so we should really leave
// this here, possibly indefinitely.
//
public interface RepositoryCache {

    /**

<div class="termy">

```console
$ python -m pip install --upgrade pip

---> 100%
```

</div>

/// tip | Подсказка

Иногда при попытке обновить pip вы можете получить ошибку **`No module named pip`**.

Если это произошло, установите и обновите pip с помощью команды ниже:

<div class="termy">

```console
$ python -m ensurepip --upgrade

---> 100%
```

</div>

errors.no_user_for_changing_password=Kata sandi saat ini tidak benar.
errors.failed_to_change_password=Gagal mengubah kata sandi Anda.
errors.unknown_version_for_upgrade=Versi untuk upgrade tidak diketahui.
errors.failed_to_upgrade_from=Gagal melakukan upgrade dari {0}.
errors.failed_to_reindex=Gagal memulai pengindeksan ulang dari {0} ke {1}.
errors.failed_to_read_request_file=Gagal membaca berkas permintaan: {0}

///

<details>
<summary>Dockerfile Preview 👀</summary>

```Dockerfile
FROM python:3.9

WORKDIR /code

COPY ./requirements.txt /code/requirements.txt

RUN pip install --no-cache-dir --upgrade -r /code/requirements.txt

COPY ./app /code/app

CMD ["uvicorn", "app.main:app", "--host", "0.0.0.0", "--port", "80"]

# If running behind a proxy like Nginx or Traefik add --proxy-headers

  maven occur, the maven inheritance model must be pinned against a particular
  modelVersion. This is required so that a change from modelVersion 4.0.0 to
  4.1.0 doesn't cause compatibility problems with users who have not upgraded
  their projects. It also allows for a certain amount of legacy support into the
  future. Therefore, we should rename this file from pom.xml in the maven-core

                    .desc("Launch the Maven Encryption tool (script option).")
                    .get());
            options.addOption(Option.builder()
                    .longOpt(UPGRADE)
                    .desc("Launch the Maven Upgrade tool (script option).")
                    .get());
            options.addOption(Option.builder()
                    .longOpt(SHELL)