schemathesis 3.25.6__tar.gz → 3.26.0__tar.gz

{schemathesis-3.25.6 → schemathesis-3.26.0}/.github/workflows/build.yml

@@ -26,7 +26,7 @@ jobs:
     name: Generic pre-commit checks
     runs-on: ubuntu-22.04
     steps:
-      - uses: actions/checkout@v4.1.1
+      - uses: actions/checkout@v4.1.2
         with:
           fetch-depth: 1
 
@@ -41,7 +41,7 @@ jobs:
     name: Documentation
     runs-on: ubuntu-22.04
     steps:
-      - uses: actions/checkout@v4.1.1
+      - uses: actions/checkout@v4.1.2
         with:
           fetch-depth: 1
       - uses: ammaraskar/sphinx-action@master
@@ -66,7 +66,7 @@ jobs:
     name: Tests (Python ${{ matrix.python }} on ${{ matrix.os }} ${{ matrix.tox_env }})
     runs-on: ${{ matrix.os }}
     steps:
-      - uses: actions/checkout@v4.1.1
+      - uses: actions/checkout@v4.1.2
         with:
           fetch-depth: 1
 
@@ -83,6 +83,6 @@ jobs:
         run: python -m tox
 
       - name: Upload coverage to Codecov
-        uses: codecov/codecov-action@v4.0.2
+        uses: codecov/codecov-action@v4.1.0
         with:
           token: ${{ secrets.CODECOV_TOKEN }}

{schemathesis-3.25.6 → schemathesis-3.26.0}/.github/workflows/codeql-analysis.yml

@@ -30,7 +30,7 @@ jobs:
 
     steps:
       - name: Checkout repository
-        uses: actions/checkout@v4.1.1
+        uses: actions/checkout@v4.1.2
         with:
           # We must fetch at least the immediate parents so that if this is
           # a pull request then we can checkout the head.
@@ -38,7 +38,7 @@ jobs:
 
       # Initializes the CodeQL tools for scanning.
       - name: Initialize CodeQL
-        uses: github/codeql-action/init@v3.24.5
+        uses: github/codeql-action/init@v3.24.7
         with:
           languages: ${{ matrix.language }}
           # If you wish to specify custom queries, you can do so here or in a config file.
@@ -49,7 +49,7 @@ jobs:
       # Autobuild attempts to build any compiled languages  (C/C++, C#, or Java).
       # If this step fails, then you should remove it and run the build manually (see below)
       - name: Autobuild
-        uses: github/codeql-action/autobuild@v3.24.5
+        uses: github/codeql-action/autobuild@v3.24.7
 
       # ℹ️ Command-line programs to run using the OS shell.
       # 📚 https://git.io/JvXDl
@@ -63,4 +63,4 @@ jobs:
       #   make release
 
       - name: Perform CodeQL Analysis
-        uses: github/codeql-action/analyze@v3.24.5
+        uses: github/codeql-action/analyze@v3.24.7

{schemathesis-3.25.6 → schemathesis-3.26.0}/.github/workflows/codspeed.yml

@@ -11,7 +11,7 @@ jobs:
   benchmarks:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v4.1.1
+      - uses: actions/checkout@v4.1.2
       - uses: actions/setup-python@v5
         with:
           # Python 3.12 for flamegraph support

{schemathesis-3.25.6 → schemathesis-3.26.0}/.github/workflows/commit.yml

@@ -12,7 +12,7 @@ jobs:
     runs-on: ubuntu-22.04
     steps:
       - name: Check out code
-        uses: actions/checkout@v4.1.1
+        uses: actions/checkout@v4.1.2
         with:
           fetch-depth: 0
       - name: Run commitsar

{schemathesis-3.25.6 → schemathesis-3.26.0}/.github/workflows/example-build.yml

@@ -16,7 +16,7 @@ jobs:
     runs-on: ubuntu-22.04
 
     steps:
-      - uses: actions/checkout@v4.1.1
+      - uses: actions/checkout@v4.1.2
 
       - name: Start containers
         run: docker compose up -d --build

{schemathesis-3.25.6 → schemathesis-3.26.0}/.github/workflows/master_update.yml

@@ -20,7 +20,7 @@ jobs:
             tag: "latest-bookworm"
 
     steps:
-      - uses: actions/checkout@v4.1.1
+      - uses: actions/checkout@v4.1.2
 
       - name: Set up QEMU
         uses: docker/setup-qemu-action@v3

{schemathesis-3.25.6 → schemathesis-3.26.0}/.github/workflows/release.yml

@@ -19,7 +19,7 @@ jobs:
             tag-suffix: "-bookworm"
 
     steps:
-      - uses: actions/checkout@v4.1.1
+      - uses: actions/checkout@v4.1.2
 
       - name: Docker meta
         id: meta
@@ -68,7 +68,7 @@ jobs:
     name: Build and publish package to pypi.org
     runs-on: ubuntu-22.04
     steps:
-      - uses: actions/checkout@v4.1.1
+      - uses: actions/checkout@v4.1.2
         with:
           fetch-depth: 1
 

{schemathesis-3.25.6 → schemathesis-3.26.0}/.github/workflows/test-corpus.yml

@@ -15,7 +15,7 @@ jobs:
     name: Corpus tests
     runs-on: ubuntu-22.04
     steps:
-      - uses: actions/checkout@v4.1.1
+      - uses: actions/checkout@v4.1.2
         with:
           fetch-depth: 1
           submodules: true

{schemathesis-3.25.6 → schemathesis-3.26.0}/.github/workflows/test-hypothesis.yml

@@ -11,7 +11,7 @@ jobs:
     name: Hypothesis tests with CI profile
     runs-on: ubuntu-22.04
     steps:
-      - uses: actions/checkout@v4.1.1
+      - uses: actions/checkout@v4.1.2
         with:
           fetch-depth: 1
 

{schemathesis-3.25.6 → schemathesis-3.26.0}/.github/workflows/update-corpus.yml

@@ -10,7 +10,7 @@ jobs:
     name: Update test corpus
     runs-on: ubuntu-22.04
     steps:
-      - uses: actions/checkout@v4.1.1
+      - uses: actions/checkout@v4.1.2
         with:
           fetch-depth: 1
           submodules: true
@@ -27,3 +27,4 @@ jobs:
           commit-message: 'chore: Update test corpus'
           committer: 'CI on behalf of the Schemathesis team <team@schemathesis.io>'
           author: 'CI on behalf of the Schemathesis team <team@schemathesis.io>'
+          branch: "create-pull-request/update-test-corpus"

{schemathesis-3.25.6 → schemathesis-3.26.0}/.github/workflows/update-pre-commit.yml

@@ -10,7 +10,7 @@ jobs:
     name: Update pre-commit
     runs-on: ubuntu-22.04
     steps:
-      - uses: actions/checkout@v4.1.1
+      - uses: actions/checkout@v4.1.2
         with:
           fetch-depth: 1
           submodules: true
@@ -28,3 +28,4 @@ jobs:
           commit-message: 'chore: Update pre-commit'
           committer: 'CI on behalf of the Schemathesis team <team@schemathesis.io>'
           author: 'CI on behalf of the Schemathesis team <team@schemathesis.io>'
+          branch: "create-pull-request/update-pre-commit"

{schemathesis-3.25.6 → schemathesis-3.26.0}/.pre-commit-config.yaml

@@ -20,7 +20,7 @@ repos:
       - id: gitlint
 
   - repo: https://github.com/adrienverge/yamllint
-    rev: v1.34.0
+    rev: v1.35.1
     hooks:
       - id: yamllint
 
@@ -30,7 +30,7 @@ repos:
       - id: relint
 
   - repo: https://github.com/pre-commit/mirrors-mypy
-    rev: v1.8.0
+    rev: v1.9.0
     hooks:
       - id: mypy
         exclude: ^(docs/|test/|test-corpus/|example/|benches/).*$
@@ -38,12 +38,12 @@ repos:
         additional_dependencies: [types-click, types-requests, types-PyYAML]
 
   - repo: https://github.com/astral-sh/ruff-pre-commit
-    rev: v0.2.1
+    rev: v0.3.3
     hooks:
       - id: ruff-format
 
   - repo: https://github.com/astral-sh/ruff-pre-commit
-    rev: v0.2.1
+    rev: v0.3.3
     hooks:
       - id: ruff
 

{schemathesis-3.25.6 → schemathesis-3.26.0}/PKG-INFO

@@ -1,14 +1,14 @@
 Metadata-Version: 2.1
 Name: schemathesis
-Version: 3.25.6
+Version: 3.26.0
 Summary: Property-based testing framework for Open API and GraphQL based apps
 Project-URL: Documentation, https://schemathesis.readthedocs.io/en/stable/
 Project-URL: Changelog, https://schemathesis.readthedocs.io/en/stable/changelog.html
 Project-URL: Bug Tracker, https://github.com/schemathesis/schemathesis
 Project-URL: Funding, https://github.com/sponsors/Stranger6667
 Project-URL: Source Code, https://github.com/schemathesis/schemathesis
-Author-email: Dmitry Dygalo <dadygalo@gmail.com>
-Maintainer-email: Dmitry Dygalo <dadygalo@gmail.com>
+Author-email: Dmitry Dygalo <dmitry@dygalo.dev>
+Maintainer-email: Dmitry Dygalo <dmitry@dygalo.dev>
 License-Expression: MIT
 License-File: LICENSE
 Keywords: graphql,hypothesis,openapi,pytest,testing
@@ -35,7 +35,8 @@ Requires-Dist: colorama<1.0,>=0.4
 Requires-Dist: httpx<1.0,>=0.22.0
 Requires-Dist: hypothesis-graphql<1,>=0.11.0
 Requires-Dist: hypothesis-jsonschema<0.24,>=0.23.1
-Requires-Dist: hypothesis<7,>=6.84.3
+Requires-Dist: hypothesis<7,>=6.84.3; python_version > '3.8'
+Requires-Dist: hypothesis[zoneinfo]<7,>=6.84.3; python_version == '3.8'
 Requires-Dist: jsonschema<5.0,>=4.18.0
 Requires-Dist: junit-xml<2.0,>=1.9
 Requires-Dist: pyrate-limiter<3.0,>=2.10
@@ -224,7 +225,9 @@ Receive automatic comments in your pull requests and updates on GitHub checks st
 
 ### Software as a Service
 
-If you prefer an all-in-one solution with quick setup, we have a [free tier](https://schemathesis.io/#pricing) available.
+Schemathesis CLI integrates with Schemathesis.io to enhance bug detection by optimizing test case generation for efficiency and realism. It leverages various techniques to infer appropriate data generation strategies, provide support for uncommon media types, and adjust schemas for faster data generation. The integration also detects the web server being used to generate more targeted test data. 
+
+Schemathesis.io offers a user-friendly UI that simplifies viewing and analyzing test results. If you prefer an all-in-one solution with quick setup, we have a [free tier](https://schemathesis.io/#pricing) available.
 
 ## How it works
 

{schemathesis-3.25.6 → schemathesis-3.26.0}/README.md

@@ -146,7 +146,9 @@ Receive automatic comments in your pull requests and updates on GitHub checks st
 
 ### Software as a Service
 
-If you prefer an all-in-one solution with quick setup, we have a [free tier](https://schemathesis.io/#pricing) available.
+Schemathesis CLI integrates with Schemathesis.io to enhance bug detection by optimizing test case generation for efficiency and realism. It leverages various techniques to infer appropriate data generation strategies, provide support for uncommon media types, and adjust schemas for faster data generation. The integration also detects the web server being used to generate more targeted test data. 
+
+Schemathesis.io offers a user-friendly UI that simplifies viewing and analyzing test results. If you prefer an all-in-one solution with quick setup, we have a [free tier](https://schemathesis.io/#pricing) available.
 
 ## How it works
 

{schemathesis-3.25.6 → schemathesis-3.26.0}/changelog.py

@@ -1,4 +1,5 @@
 """Simple CLI for changelog management."""
+
 from __future__ import annotations
 import argparse
 import datetime

{schemathesis-3.25.6 → schemathesis-3.26.0}/docs/api.rst

@@ -92,6 +92,10 @@ Custom strategies for Open API "format" keyword
 
 .. autofunction:: schemathesis.openapi.format
 
+Custom strategies for Open API media types
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+.. autofunction:: schemathesis.openapi.media_type
 
 Custom scalars for GraphQL
 ~~~~~~~~~~~~~~~~~~~~~~~~~~

{schemathesis-3.25.6 → schemathesis-3.26.0}/docs/changelog.rst

@@ -1,9 +1,28 @@
 Changelog
 =========
 
-:version:`Unreleased <v3.25.6...HEAD>` - TBD
+:version:`Unreleased <v3.26.0...HEAD>` - TBD
 --------------------------------------------
 
+.. _v3.26.0:
+
+:version:`3.26.0 <v3.25.6...v3.26.0>` - 2024-03-21
+--------------------------------------------------
+
+**Added**
+
+- Support for per-media type data generators. :issue:`962`
+- Support for ``application/yaml`` & ``text/yml`` media types in ``YAMLSerializer``.
+- **EXPERIMENTAL**: Run automatic schema optimization & format inference if CLI is authenticated in Schemathesis.io.
+
+**Fixed**
+
+- Not resolving references in nested security schemes. :issue:`2073`
+
+**Changed**
+
+- Improve error message when the minimum possible example is too large.
+
 .. _v3.25.6:
 
 :version:`3.25.6 <v3.25.5...v3.25.6>` - 2024-03-02

{schemathesis-3.25.6 → schemathesis-3.26.0}/docs/data-generation.rst

@@ -12,6 +12,125 @@ Schemathesis converts Open API schemas to compatible JSON Schemas and passes the
     There are many tradeoffs in this process, and Hypothesis tries to give reasonable defaults for a typical case
     and not be too slow for pathological cases.
 
+.. _data-generation-overview:
+
+Overview
+--------
+
+For each API operation, Schemathesis follows a strict order in its test generation process, which includes several phases: explicit examples usage, rerunning previously failed tests, random test generation, and test case minimization (shrinking).
+Each phase targets distinct testing aspects:
+
+- **Explicit examples** (`explicit`): Uses predefined examples from the schema.
+- **Rerunning known failures** (`reuse`): Reuses previously failed test cases to check whether they are still failing.
+- **Random generation** (`generate`): Generates random test cases based on the schema.
+- **Shrinking** (`shrink`): Minimizes the failing test cases to make them easier to understand and debug.
+
+These phases can be selectively enabled or disabled to configure the testing process:
+
+.. code:: shell
+
+    # To disable the shrinking phase
+    --hypothesis-no-phases=shrink
+
+    # To only include the generate and shrink phases
+    --hypothesis-phases=generate,shrink
+
+Additionally, you can control the upper limit of generated test cases (only for the ``generate`` phase) via the ``--hypothesis-max-examples`` option.
+
+.. code:: shell
+
+    # Raise the upper cap for generated test cases per operation
+    --hypothesis-max-examples=1000
+
+The generation process is inherently randomized and is designed for efficient testing, favoring speed and maintaining reasonable coverage over exhaustive testing. 
+It also means that Schemathesis does not guarantee the full coverage of all possible variants, but will do its best to generate a diverse set of test cases with minimal duplication.
+
+The number of generated tests is affected by the schema's complexity and the distinctness of possible test cases.
+Simple schemas with a clear set of distinct values, like a boolean, naturally limit the total number of unique test cases.
+Conversely, complex schemas with many nested objects and arrays can produce a large number of unique test cases.
+
+When Schemathesis finds a minimal failing test case, it stops the test case generation process and verifies whether the failure could be consistently reproduced by rerunning it one more time.
+It also caches distinct minimized failures for reuse in subsequent runs, aiding in catching regressions.
+
+Explicit examples
+~~~~~~~~~~~~~~~~~
+
+This phase uses examples directly from the API schema, filling missing parts with random data.
+If the schema specifies multiple examples for a parameter, then Schemathesis will use a round-robin strategy to ensure all examples are tested.
+
+.. code:: shell
+
+   # Schema
+  {
+    "type": "object",
+    "properties": {
+      "name": {"type": "string", "example": "John"},
+      "age": {"type": "integer", "examples": [42, 43]},
+      "street": {"type": "string"}
+    }
+  }
+  # Test cases
+  {"name": "John", "age": 42, "street": "<RANDOM STRING>"}
+  {"name": "John", "age": 43, "street": "<ANOTHER RANDOM STRING>"}
+
+Reusing known failures
+~~~~~~~~~~~~~~~~~~~~~~
+
+Schemathesis stores failed test cases in a cache (the ``.hypothesis`` directory) and reruns them in subsequent runs to detect regressions.
+This phase may reduce the total number of generated test cases as Schemathesis may find failures earlier.
+
+Generating random test cases
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The generation process is governed by the ``--data-generation-method`` CLI option, and creates valid (``positive``) or guaranteed invalid (``negative``) test cases based on the schema. 
+If negative testing is inapplicable (e.g., when any input is accepted), the tests are skipped.
+
+Example:
+
+.. code:: shell
+
+    # Schema
+    {
+      "type": "object",
+      "properties": {
+        "name": {"type": "string"}
+      }
+    }
+
+    # Positive testing
+    {"name": "John"}
+
+    # Negative testing
+    {"name": 42}
+
+The upper limit of generated test cases could be controlled via the ``--hypothesis-max-examples`` option.
+
+Test case minimization
+~~~~~~~~~~~~~~~~~~~~~~
+
+This phase focuses on reducing the complexity of failing test cases to make them easier to understand and debug.
+
+While beneficial for isolating issues in complex schemas, it can be time-consuming.
+Disabling shrinking (``--hypothesis-no-phases=shrink``) may be advantageous when the source of an error is apparent and can be debugged straightforwardly.
+
+.. code:: shell
+
+    # Schema
+    {
+      "type": "object",
+      "properties": {
+        "name": {"type": "string", "minLength": 5}
+      }
+    }
+
+    # Failing test case
+    {"name": "Very long name"}
+
+    # Minimized test case
+    {"name": "aaaaa"}
+
+Shrinking works for arbitrary complex structures allowing to avoid digging through large payloads.
+
 Generating strings
 ------------------
 

{schemathesis-3.25.6 → schemathesis-3.26.0}/docs/experimental.rst

@@ -110,7 +110,35 @@ To enable OpenAPI 3.1 support via environment variables, you can set:
 
     export SCHEMATHESIS_EXPERIMENTAL_OPENAPI_3_1=true
 
-For more details, join the `GitHub Discussion <https://github.com/schemathesis/schemathesis/discussions/1822>`_.
+For more details, join the `GitHub Discussion #1822 <https://github.com/schemathesis/schemathesis/discussions/1822>`_.
+
+Schema Analysis
+~~~~~~~~~~~~~~~
+
+Enables integration with Schemathesis.io to optimize test case generation for better bug detection.
+This feature infers appropriate data generation strategies, supports uncommon media types, adjusts schemas for faster data generation, and detects the web server to generate more targeted test data. 
+
+.. _schema-analysis-cli:
+
+In CLI
+~~~~~~
+
+.. code-block:: bash
+
+  st run https://example.schemathesis.io/openapi.json --experimental=schema-analysis
+
+.. _schema-analysis-env-vars:
+
+Using Environment Variables
+~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+To enable schema analysis support via environment variables, you can set:
+
+.. code-block:: bash
+
+    export SCHEMATHESIS_EXPERIMENTAL_SCHEMA_ANALYSIS=true
+
+For more details, join the `GitHub Discussion #2056 <https://github.com/schemathesis/schemathesis/discussions/2056>`_.
 
 Stabilization of Experimental Features
 --------------------------------------

{schemathesis-3.25.6 → schemathesis-3.26.0}/docs/extending.rst

@@ -645,6 +645,35 @@ In the example above, when Schemathesis detects a string with the "card_number"
 
 For more details about creating strategies, refer to the `Hypothesis documentation <https://hypothesis.readthedocs.io/en/latest/data.html>`_.
 
+Generating payloads for unknown media types
+-------------------------------------------
+
+Each request payload in Open API is associated with a media type, which defines the format of the payload content.
+Schemathesis allows you to manage the generation of payloads by registering Hypothesis strategies for specific media types.
+
+Schemathesis generates request payload, it first checks whether there is a custom generation strategy registered for the media type.
+If a strategy is registered, it will be used to generate the payload content; otherwise, it will generate payloads based on the schema.
+
+- **Create a Hypothesis Strategy**: Create a strategy that generates binary payloads compliant with the media type.
+- **Register the Strategy**: Make it known to Schemathesis using ``schemathesis.openapi.media_type``.
+
+.. code-block:: python
+
+    from hypothesis import strategies as st
+    import schemathesis
+
+    # Define your own strategy for generating PDFs
+    # NOTE: This is a simplified example, actual PDF generation is much more complex
+    pdfs = st.sampled_from([b"%PDF-1.5...", b"%PDF-1.6..."])
+
+    # Register the strategy for "application/pdf" media type
+    schemathesis.openapi.media_type("application/pdf", pdfs)
+    # You can also specify one or more additional aliases for the media type
+    schemathesis.openapi.media_type("application/pdf", pdfs, aliases=["application/x-pdf"])
+
+In this example, ``pdfs`` would be a Hypothesis strategy that generates binary data compliant with the PDF format.
+When Schemathesis encounters a request payload with the "application/pdf" media type, it uses the registered strategy to generate the payload content.
+
 Schemathesis test runner
 ------------------------
 

{schemathesis-3.25.6 → schemathesis-3.26.0}/docs/faq.rst

@@ -15,6 +15,13 @@ This data consists of all possible data types from the JSON schema specification
 We can't guarantee that the generated data will always be accepted by the application under test since there could be validation rules not covered by the API schema.
 If you found that Schemathesis generated something that doesn't fit the API schema, consider `reporting a bug <https://github.com/schemathesis/schemathesis/issues/new?assignees=Stranger6667&labels=Status%3A+Review+Needed%2C+Type%3A+Bug&template=bug_report.md&title=%5BBUG%5D>`_
 
+How many tests does Schemathesis execute for an API operation?
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The total number of tests Schemathesis executes is influenced by the API schema's complexity, user-defined settings like ``--hypothesis-max-examples`` for the maximum tests generated, and the test generation phases (``explicit``, ``generate``, ``reuse``, and ``shrink``). 
+The process is designed to optimize coverage within a reasonable test budget rather than aiming for exhaustive coverage. 
+For detailed insights and customization options, refer to our :ref:`data generation docs <data-generation-overview>`.
+
 What kind errors Schemathesis is capable to find?
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 

{schemathesis-3.25.6 → schemathesis-3.26.0}/docs/service.rst

@@ -7,6 +7,27 @@ Schemathesis as a Service on `Schemathesis.io <https://app.schemathesis.io/auth/
 
     For a step-by-step guide on getting started with Schemathesis.io, visit our `Quick Start Guide <https://docs.schemathesis.io/quick-start/>`_.
 
+Schema Analysis (Experimental)
+------------------------------
+
+Schemathesis CLI now includes an experimental feature that integrates with Schemathesis.io to improve the efficiency and realism of generated test cases for better bug detection. This feature optimizes test case generation by:
+
+- Inferring "format" keywords for appropriate string data generation
+- Providing data generation strategies for uncommon media types (e.g., application/pdf)
+- Inferring data generation strategies for GraphQL scalars
+- Adjusting schemas for faster data generation in Schemathesis
+- Detecting the web server to generate more targeted test data and avoid rejected inputs
+
+By enabling this feature, you can potentially benefit from faster achievement of higher edge case coverage and tests that reach deeper into your API implementation.
+
+To enable schema analysis, use the ``--experimental=schema-analysis`` CLI option. It is also automatically enabled when the ``--report`` CLI option is used.
+
+.. note::
+ 
+    During the experimental phase, schema analysis is available free of charge and does not require signup. By using this feature, you automatically agree to Schemathesis.io's `Terms of Service <https://schemathesis.io/legal/terms>`_ and `Privacy Policy`_.
+
+Please note that this feature is still experimental, and its effectiveness may vary depending on the API being tested. We are actively refining the algorithms and techniques used. If you encounter any issues or have suggestions, please open an issue on our GitHub repository or reach out via our support channels.
+
 Uploading Reports to Schemathesis.io
 ------------------------------------
 

{schemathesis-3.25.6 → schemathesis-3.26.0}/pyproject.toml

@@ -4,11 +4,11 @@ build-backend = "hatchling.build"
 
 [project]
 name = "schemathesis"
-version = "3.25.6"
+version = "3.26.0"
 description = "Property-based testing framework for Open API and GraphQL based apps"
 keywords = ["pytest", "hypothesis", "openapi", "graphql", "testing"]
-authors = [{ name = "Dmitry Dygalo", email = "dadygalo@gmail.com" }]
-maintainers = [{ name = "Dmitry Dygalo", email = "dadygalo@gmail.com" }]
+authors = [{ name = "Dmitry Dygalo", email = "dmitry@dygalo.dev" }]
+maintainers = [{ name = "Dmitry Dygalo", email = "dmitry@dygalo.dev" }]
 requires-python = ">=3.8"
 license = "MIT"
 readme = "README.md"
@@ -36,7 +36,8 @@ dependencies = [
     "click>=7.0,<9.0",
     "colorama>=0.4,<1.0",
     "httpx>=0.22.0,<1.0",
-    "hypothesis>=6.84.3,<7",
+    "hypothesis>=6.84.3,<7; python_version > '3.8'",
+    "hypothesis[zoneinfo]>=6.84.3,<7; python_version == '3.8'",
     "hypothesis_graphql>=0.11.0,<1",
     "hypothesis_jsonschema>=0.23.1,<0.24",
     "jsonschema>=4.18.0,<5.0",

{schemathesis-3.25.6 → schemathesis-3.26.0}/src/schemathesis/_dependency_versions.py

@@ -1,4 +1,5 @@
 """Compatibility flags based on installed dependency versions."""
+
 from packaging import version
 
 from importlib import metadata

{schemathesis-3.25.6 → schemathesis-3.26.0}/src/schemathesis/_hypothesis.py

@@ -1,4 +1,5 @@
 """High-level API for creating Hypothesis tests."""
+
 from __future__ import annotations
 
 import asyncio

{schemathesis-3.25.6 → schemathesis-3.26.0}/src/schemathesis/_xml.py

@@ -1,4 +1,5 @@
 """XML serialization."""
+
 from __future__ import annotations
 from io import StringIO
 from typing import Any, Dict, List, Union

{schemathesis-3.25.6 → schemathesis-3.26.0}/src/schemathesis/auths.py

@@ -1,4 +1,5 @@
 """Support for custom API authentication mechanisms."""
+
 from __future__ import annotations
 import inspect
 import threading