During bazel build all TensorFlow's Python dependencies are pinned to their
specific versions. This is necessary to ensure reproducibility of the build.
The pinned versions of the full transitive closure of TensorFlow's dependencies
together with their corresponding hashes are specified in
`requirements_lock_<python version>.txt` files (e.g.
`requirements_lock_3_12.txt` for `Python 3.12`).

To update the lock files, make sure

//       purge:
//           # retainVersions: 0 # (default) delete all versions of the object. This option is the fastest.
//           # retainVersions: 5 # keep the latest 5 versions of the object.
//
//     - type: deleted # objects with delete marker as their latest version
//       name: NAME # match object names that satisfy the wildcard expression.

<?xml version="1.0" encoding="UTF-8"?>
<metadata>
  <groupId>org.codelibs.fess</groupId>
  <artifactId>fess-crawler-smbj</artifactId>
  <versioning>
    <latest>14.15.0</latest>
    <release>14.15.0</release>
    <versions>
      <version>14.14.0</version>
      <version>14.15.0</version>
    </versions>
    <lastUpdated>20240526053206</lastUpdated>
  </versioning>

     * @since 3.0-alpha-3
     */
    Artifact find(Artifact artifact);

    /**
     * Finds the versions of the specified artifact that are available in this repository.
     *
     * @param artifact The artifact whose available versions should be determined, must not be {@code null}.
     * @return The available versions of the artifact or an empty list if none, never {@code null}.
     * @since 3.0-alpha-3
     */

<?xml version="1.0" encoding="UTF-8"?>
<metadata>
    <groupId>org.codelibs.fess</groupId>
    <artifactId>fess-ds-atlassian</artifactId>
    <versioning>
        <latest>13.2.0</latest>
        <release>13.2.0</release>
        <versions>
            <version>12.2.0</version>
            <version>12.5.0</version>
            <version>12.6.0</version>
            <version>12.7.0</version>
            <version>13.0.0</version>

<?xml version="1.0" encoding="UTF-8"?>
<metadata>
  <groupId>org.codelibs.fess</groupId>
  <artifactId>fess-crawler-db</artifactId>
  <versioning>
    <latest>1.0.12</latest>
    <release>1.0.12</release>
    <versions>
      <version>1.0.0</version>
      <version>1.0.1</version>
      <version>1.0.2</version>
      <version>1.0.3</version>
      <version>1.0.4</version>
      <version>1.0.5</version>
      <version>1.0.6</version>

import org.apache.maven.artifact.repository.ArtifactRepository;
import org.apache.maven.artifact.versioning.ArtifactVersion;

/**
 * Provides some metadata operations, like querying the remote repository for a list of versions available for an
 * artifact.
 *
 */
@Deprecated
public interface ArtifactMetadataSource {

    ResolutionGroup retrieve(MetadataResolutionRequest request) throws ArtifactMetadataRetrievalException;

connection to an HTTPS server, OkHttp needs to know which [TLS versions](https://square.github.io/okhttp/4.x/okhttp/okhttp3/-tls-version/) and [cipher suites](https://square.github.io/okhttp/4.x/okhttp/okhttp3/-cipher-suite/) to offer. A client that wants to maximize connectivity would include obsolete TLS versions and weak-by-design cipher suites. A strict client that wants to maximize security would be limited to only the latest TLS version and strongest cipher suites.

Specific security vs....

Because of that, versions of FastAPI previous to 0.99.0 still used versions of OpenAPI lower than 3.1.0.

///

### Pydantic and FastAPI `examples` { #pydantic-and-fastapi-examples }

Wildcards can be used, for example `mc support inspect ALIAS/bucket/path/**/xl.meta` will collect all `xl.meta` recursively. `mc support inspect ALIAS/bucket/path/to/file.txt/*/part.*` will collect parts for all versions for the object located at `bucket/path/to/file.txt`.

`xl-meta` accepts zip files as input and will output all `xl.meta` files found within the archive. For example:

```
$ mc support inspect play/test123/test*/xl.meta