],
      "allowedVersions": "<10.0",
      "description": "JDK 11 requirement"
    },
    {
      "extends": [
        "monorepo:junit5"
      ],
      "allowedVersions": "<5.14.0",
    },
    {
      "matchPackageNames": [
        "org.junit-pioneer:junit-pioneer"
      ],
      "allowedVersions": "<2.0.0",
      "description": "JDK 11 requirement"
    },
    {
      "matchPackageNames": [

  PROFILE_JSON_PATH="$PROFILE_JSON_PATH/profile.json.gz"
else
  PROFILE_JSON_PATH="$TFCI_OUTPUT_DIR/profile.json.gz"
fi

# TODO(b/361369076) Remove the following block after TF NumPy 1 is dropped
# Move hermetic requirement lock files for NumPy 1 to the root
if [[ "$TFCI_WHL_NUMPY_VERSION" == 1 ]]; then
  cp ./ci/official/requirements_updater/numpy1_requirements/*.txt .
fi

if [[ $TFCI_PYCPP_SWAP_TO_BUILD_ENABLE == 1 ]]; then

* **Professional appearance**: Consistent APIs and documentation appear more polished
* **Clearer contribution guidelines**: [CONTRIBUTING.md](../../CONTRIBUTING.md) now includes this requirement

### Negative Consequences

* **Historical inconsistencies**: Existing code may contain British English spellings that cannot be changed due to backward compatibility

### Migration and Enforcement

Additionally, in instructional sentences, prefer the present tense for obligations:

- Prefer `vous devez …` over `vous devrez …`, unless the English source explicitly refers to a future requirement.

- When translating “make sure (that) … is …”, prefer the indicative after `vous assurer que` (e.g. `Vous devez vous assurer qu'il est …`) instead of the subjunctive (e.g. `qu'il soit …`).

### Quotes

During the development, I also contributed to [**Starlette**](https://www.starlette.dev/), the other key requirement.

## Development { #development }

By the time I started creating **FastAPI** itself, most of the pieces were already in place, the design was defined, the requirements and tools were ready, and the knowledge about the standards and specifications was clear and fresh.

## Future { #future }

     * that other project must support the runtimes of the project with requirements.
     *
     * @return A mapping of project paths to their computed runtimes, including
     * the specific projects that triggered each requirement.
     */
    private fun computeTargetRuntimes(projects: Map<String, ProjectInfo>): Map<String, Map<TargetRuntime, Set<String>>> {

     * </p>
     */
    public DataSerializer() {
        kryoThreadLocal = ThreadLocal.withInitial(() -> {
            final Kryo kryo = new Kryo();
            // Enable registration requirement for security - only registered classes can be deserialized
            kryo.setRegistrationRequired(true);
            if (logger.isDebugEnabled()) {
                kryo.setWarnUnregisteredClasses(true);
            }

But OAuth2 with scopes can be nicely integrated into your API (with OpenAPI) and your API docs.

Nevertheless, you still enforce those scopes, or any other security/authorization requirement, however you need, in your code.

In many cases, OAuth2 with scopes can be an overkill.

But if you know you need it, or you are curious, keep reading.

///

     * When enabled, additional parameters are added to search result URLs.
     */
    @Size(max = 10)
    public String appendQueryParameter;

    /**
     * Enable or disable login requirement for search access.
     * When enabled, users must authenticate before performing searches.
     */
    @Size(max = 10)
    public String loginRequired;

    /**

    }

    // ========== Security Tests ==========

    /**
     * Security test: Verify that unregistered classes are rejected during serialization.
     * This test ensures that the Kryo registration requirement is working correctly.
     * Unregistered classes should throw an exception to prevent potential RCE attacks.
     */
    @Test
    public void test_security_unregisteredClassRejected() {