return gitWrapper.listVersions(tagPattern)
            .filter(v -> v.isBefore(version));
    }

    /**
     * Used to make it possible to mock destructive operations in tests.
     */
    @VisibleForTesting
    @FunctionalInterface
    interface DeleteHelper {
        Set<File> deleteFiles(Set<File> filesToDelete);
    }

   */
  open fun isDuplex(): Boolean = false

  /**
   * Returns true if this body expects at most one call to [writeTo] and can be transmitted
   * at most once. This is typically used when writing the request body is destructive and it is not
   * possible to recreate the request body after it has been sent.
   *
   * This method returns false unless it is overridden by a subclass.
   *

`PATCH` est moins utilisé et moins connu que `PUT`.

Et de nombreuses équipes n’utilisent que `PUT`, même pour les mises à jour partielles.

Vous êtes libre de les utiliser comme vous le souhaitez, **FastAPI** n’impose aucune restriction.

Mais ce guide vous montre, plus ou moins, la façon dont ils sont censés être utilisés.

///

### Utiliser le paramètre `exclude_unset` de Pydantic { #using-pydantics-exclude-unset-parameter }

 *
 * <ul>
 *   <li><b>Finite:</b> Many operations, such as {@link #length()} and {@link #read()}, will either
 *       block indefinitely or fail if the source creates an infinite reader.
 *   <li><b>Non-destructive:</b> A <i>destructive</i> reader will consume or otherwise alter the
 *       source as they are read from it. A source that provides such readers will not be reusable,

	MOVWP	4(R5), R4		// a4040024
	MOVWP	(R5), R4		// a4000024
	MOVVP	32764(R5), R4		// a4fc7f26
	MOVVP	32(R5), R4		// a4200026
	MOVVP	4(R5), R4		// a4040026
	MOVVP	(R5), R4		// a4000026

	// ADDU16I.D instruction
	ADDV16	$(-32768<<16), R4, R5	// ADDV16	$-2147483648, R4, R5	// 85000012
	ADDV16	$(0<<16), R4, R5	// ADDV16	$0, R4, R5		// 85000010
	ADDV16	$(8<<16), R4, R5	// ADDV16	$524288, R4, R5		// 85200010

{* ../../docs_src/events/tutorial003_py310.py hl[1,13] *}

Un **gestionnaire de contexte** en Python est quelque chose que vous pouvez utiliser dans une instruction `with`. Par exemple, `open()` peut être utilisé comme gestionnaire de contexte :

```Python
with open("file.txt") as file:
    file.read()
```

///

/// warning

Make sure to **always** use the **exec form** of the `CMD` instruction, as explained below.

///

#### Use `CMD` - Exec Form { #use-cmd-exec-form }

The [`CMD`](https://docs.docker.com/reference/dockerfile/#cmd) Docker instruction can be written using two forms:

✅ **Exec** form:

```Dockerfile
# ✅ Do this

#
# Macosx options
#     darwin_arm64:
#
# Compiler options:
#     cuda_clang:             Use Clang when building CUDA code.
#     avx_linux:              Build with avx instruction set on linux.
#     avx_win:                Build with avx instruction set on windows
#
# Other build options:
#     short_logs:       Only log errors during build, skip warnings.
#     verbose_logs:     Show all compiler warnings during build.

governed by this License along with a term that is a further
restriction, you may remove that term.  If a license document contains
a further restriction but permits relicensing or conveying under this
License, you may add to a covered work material governed by the terms
of that license document, provided that the further restriction does
not survive such relicensing or conveying.

  virtual ~AbstractOperation() {}

 public:
  AbstractOperationKind getKind() const { return kind_; }

  // Release any underlying resources, including the interface object.
  //
  // WARNING: The destructor of this class is marked as protected to disallow
  // clients from directly destroying this object since it may manage it's own
  // lifetime through ref counting. Thus this must be allocated on the heap and