Skip to content

build(deps): bump the minor-and-patch group with 6 updates #667

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Jun 16, 2025
Merged

build(deps): bump the minor-and-patch group with 6 updates #667

merged 1 commit into from
Jun 16, 2025

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jun 9, 2025

Bumps the minor-and-patch group with 6 updates:

Package From To
stac-check 1.6.0 1.7.0
stac-validator 3.7.0 3.8.1
pytest 8.3.5 8.4.0
typeguard 4.4.2 4.4.3
ruamel-yaml 0.18.12 0.18.14
typing-extensions 4.13.2 4.14.0

Updates stac-check from 1.6.0 to 1.7.0

Release notes

Sourced from stac-check's releases.

v1.7.0

What's Changed

Added

  • Added validation for bounding boxes that cross the antimeridian (180°/-180° longitude) (#121)
    • Checks that bbox coordinates follow the GeoJSON specification for antimeridian crossing
    • Detects and reports cases where a bbox incorrectly "belts the globe" instead of properly crossing the antimeridian
    • Provides clear error messages to help users fix incorrectly formatted bboxes
  • Added sponsors and supporters section with logos (#122)
  • Added check to verify that bbox matches item's polygon geometry (#123)
  • Added configuration documentation to README (#124)
  • Added validation for geometry coordinates order to detect potentially reversed lat/lon coordinates (#125)
    • Checks that coordinates follow the GeoJSON specification with [longitude, latitude] order
    • Uses heuristics to identify coordinates that may be reversed or contain errors
    • Provides nuanced error messages acknowledging the uncertainty in coordinate validation
  • Added validation for definite geometry coordinate errors (#125)
    • Detects coordinates with latitude values exceeding ±90 degrees
    • Detects coordinates with longitude values exceeding ±180 degrees
    • Returns detailed information about invalid coordinates
  • Added dedicated geometry validation configuration section (#125)
    • Created a new geometry_validation section in the configuration file
    • Added a master enable/disable switch for all geometry validation checks
    • Reorganized geometry validation options into the new section
    • Separated geometry validation errors in CLI output with a [BETA] label
    • Added detailed documentation for geometry validation features
  • Added --pydantic option for validating STAC objects using stac-pydantic models, providing enhanced type checking and validation (#126)

Enhanced

  • Improved bbox validation output to show detailed information about mismatches between bbox and geometry bounds, including which specific coordinates differ and by how much (#126)

Fixed

  • Fixed collection summaries check incorrectly showing messages for Item assets (#121)

Full Changelog: stac-utils/stac-check@v1.6.0...v1.7.0

Changelog

Sourced from stac-check's changelog.

[v1.7.0] - 2025-06-01

Added

  • Added validation for bounding boxes that cross the antimeridian (180°/-180° longitude) (#121)
    • Checks that bbox coordinates follow the GeoJSON specification for antimeridian crossing
    • Detects and reports cases where a bbox incorrectly "belts the globe" instead of properly crossing the antimeridian
    • Provides clear error messages to help users fix incorrectly formatted bboxes
  • Added sponsors and supporters section with logos (#122)
  • Added check to verify that bbox matches item's polygon geometry (#123)
  • Added configuration documentation to README (#124)
  • Added validation for geometry coordinates order to detect potentially reversed lat/lon coordinates (#125)
    • Checks that coordinates follow the GeoJSON specification with [longitude, latitude] order
    • Uses heuristics to identify coordinates that may be reversed or contain errors
    • Provides nuanced error messages acknowledging the uncertainty in coordinate validation
  • Added validation for definite geometry coordinate errors (#125)
    • Detects coordinates with latitude values exceeding ±90 degrees
    • Detects coordinates with longitude values exceeding ±180 degrees
    • Returns detailed information about invalid coordinates
  • Added dedicated geometry validation configuration section (#125)
    • Created a new geometry_validation section in the configuration file
    • Added a master enable/disable switch for all geometry validation checks
    • Reorganized geometry validation options into the new section
    • Separated geometry validation errors in CLI output with a [BETA] label
    • Added detailed documentation for geometry validation features
  • Added --pydantic option for validating STAC objects using stac-pydantic models, providing enhanced type checking and validation (#126)

Enhanced

  • Improved bbox validation output to show detailed information about mismatches between bbox and geometry bounds, including which specific coordinates differ and by how much (#126)

Fixed

  • Fixed collection summaries check incorrectly showing messages for Item assets (#121)

Updated

  • Improved README with table of contents, better formatting, stac-check logo, and enhanced documentation (#122)
  • Enhanced Contributing guidelines with step-by-step instructions (#122)

Removed

  • Support for Python 3.8 (#121)
Commits

Updates stac-validator from 3.7.0 to 3.8.1

Release notes

Sourced from stac-validator's releases.

v3.8.1

What's Changed

Full Changelog: stac-utils/stac-validator@v3.8.0...v3.8.1

v3.8.0

What's Changed

  • Added --schema-config option to specify a YAML or JSON configuration file that maps remote schema URLs to local file paths, making it easier to validate against multiple local schemas, allowing offline validation and improved performance by @​jonhealy1 in stac-utils/stac-validator#253

Full Changelog: stac-utils/stac-validator@v3.7.0...v3.8.0

Changelog

Sourced from stac-validator's changelog.

[v3.8.1] - 2025-06-04

Fixed

  • Fixed the pydantic extra dependency in setup.py to properly install stac-pydantic when using pip install stac-validator[pydantic] #254

[v3.8.0] - 2025-06-03

Added

  • Added --schema-config option to specify a YAML or JSON configuration file that maps remote schema URLs to local file paths, making it easier to validate against multiple local schemas, allowing offline validation and improved performance #253
Commits

Updates pytest from 8.3.5 to 8.4.0

Release notes

Sourced from pytest's releases.

8.4.0

pytest 8.4.0 (2025-06-02)

Removals and backward incompatible breaking changes

  • #11372: Async tests will now fail, instead of warning+skipping, if you don't have any suitable plugin installed.

  • #12346: Tests will now fail, instead of raising a warning, if they return any value other than None.

  • #12874: We dropped support for Python 3.8 following its end of life (2024-10-07).

  • #12960: Test functions containing a yield now cause an explicit error. They have not been run since pytest 4.0, and were previously marked as an expected failure and deprecation warning.

    See the docs <yield tests deprecated>{.interpreted-text role="ref"} for more information.

Deprecations (removal in next major release)

  • #10839: Requesting an asynchronous fixture without a [pytest_fixture_setup]{.title-ref} hook that resolves it will now give a DeprecationWarning. This most commonly happens if a sync test requests an async fixture. This should have no effect on a majority of users with async tests or fixtures using async pytest plugins, but may affect non-standard hook setups or autouse=True. For guidance on how to work around this warning see sync-test-async-fixture{.interpreted-text role="ref"}.

New features

  • #11538: Added pytest.RaisesGroup{.interpreted-text role="class"} as an equivalent to pytest.raises{.interpreted-text role="func"} for expecting ExceptionGroup{.interpreted-text role="exc"}. Also adds pytest.RaisesExc{.interpreted-text role="class"} which is now the logic behind pytest.raises{.interpreted-text role="func"} and used as parameter to pytest.RaisesGroup{.interpreted-text role="class"}. RaisesGroup includes the ability to specify multiple different expected exceptions, the structure of nested exception groups, and flags for emulating except* <except_star>{.interpreted-text role="ref"}. See assert-matching-exception-groups{.interpreted-text role="ref"} and docstrings for more information.

  • #12081: Added capteesys{.interpreted-text role="fixture"} to capture AND pass output to next handler set by --capture=.

  • #12504: pytest.mark.xfail{.interpreted-text role="func"} now accepts pytest.RaisesGroup{.interpreted-text role="class"} for the raises parameter when you expect an exception group. You can also pass a pytest.RaisesExc{.interpreted-text role="class"} if you e.g. want to make use of the check parameter.

  • #12713: New [--force-short-summary]{.title-ref} option to force condensed summary output regardless of verbosity level.

    This lets users still see condensed summary output of failures for quick reference in log files from job outputs, being especially useful if non-condensed output is very verbose.

  • #12749: pytest traditionally collects classes/functions in the test module namespace even if they are imported from another file.

    For example:

    # contents of src/domain.py
class Testament: ...
contents of tests/test_testament.py
from domain import Testament
def test_testament(): ...

    In this scenario with the default options, pytest will collect the class [Testament]{.title-ref} from [tests/test_testament.py]{.title-ref} because it starts with [Test]{.title-ref}, even though in this case it is a production class being imported in the test module namespace.

    This behavior can now be prevented by setting the new collect_imported_tests{.interpreted-text role="confval"} configuration option to false, which will make pytest collect classes/functions from test files only if they are defined in that file.

... (truncated)

Commits
  • 315b3ae Prepare release version 8.4.0
  • 1498ba3 Merge pull request #13467 from pytest-dev/towncrier-create
  • e4389ac Remove resultlog from the docs (#13465)
  • 64b2301 scripts/release: add missing build to towncrier call
  • 4c205cf testing/plugins_integration: update Django (#13463)
  • 4dcbcc9 Merge pull request #13458 from pytest-dev/dup-param-error
  • 5293016 Merge pull request #13459 from pytest-dev/pyright-minor-fixes
  • 7a48181 Add pyright configuration
  • 9fc6db9 pytester: avoid confusing x self parameter
  • 9aa198b mark/expression: fix self -> cls
  • Additional commits viewable in compare view

Updates typeguard from 4.4.2 to 4.4.3

Release notes

Sourced from typeguard's releases.

4.4.3

  • Fixed @typechecked unable to find the target function or method if it or the containing class had PEP 695 type parameters on them (#500)
  • Fixed handling of union types on Python 3.14 (#522)
  • Fixed __type_params__ getting lost when a function is instrumented
Changelog

Sourced from typeguard's changelog.

Version history

This library adheres to Semantic Versioning 2.0 <https://semver.org/#semantic-versioning-200>_.

4.4.3 (2025-06-05)

  • Fixed @typechecked unable to find the target function or method if it or the containing class had PEP 695 type parameters on them ([#500](https://github.com/agronholm/typeguard/issues/500) <https://github.com/agronholm/typeguard/issues/500>_)
  • Fixed handling of union types on Python 3.14 ([#522](https://github.com/agronholm/typeguard/issues/522) <https://github.com/agronholm/typeguard/issues/522>_)
  • Fixed __type_params__ getting lost when a function is instrumented

4.4.2 (2025-02-16)

  • Fixed TypeCheckError in unpacking assignment involving properties of a parameter of the function ([#506](https://github.com/agronholm/typeguard/issues/506) <https://github.com/agronholm/typeguard/issues/506>_; regression introduced in v4.4.1)
  • Fixed display of module name for forward references ([#492](https://github.com/agronholm/typeguard/issues/492) <https://github.com/agronholm/typeguard/pull/492>_; PR by @​JelleZijlstra)
  • Fixed TypeError when using an assignment expression ([#510](https://github.com/agronholm/typeguard/issues/510) <https://github.com/agronholm/typeguard/issues/510>_; PR by @​JohannesK71083)
  • Fixed ValueError: no signature found for builtin when checking against a protocol and a matching attribute in the subject is a built-in function ([#504](https://github.com/agronholm/typeguard/issues/504) <https://github.com/agronholm/typeguard/issues/504>_)

4.4.1 (2024-11-03)

  • Dropped Python 3.8 support
  • Changed the signature of typeguard_ignore() to be compatible with typing.no_type_check() (PR by @​jolaf)
  • Avoid creating reference cycles when type checking uniontypes and classes
  • Fixed checking of variable assignments involving tuple unpacking ([#486](https://github.com/agronholm/typeguard/issues/486) <https://github.com/agronholm/typeguard/issues/486>_)
  • Fixed TypeError when checking a class against type[Self] ([#481](https://github.com/agronholm/typeguard/issues/481) <https://github.com/agronholm/typeguard/issues/481>_)
  • Fixed checking of protocols on the class level (against type[SomeProtocol]) ([#498](https://github.com/agronholm/typeguard/issues/498) <https://github.com/agronholm/typeguard/issues/498>_)
  • Fixed Self checks in instance/class methods that have positional-only arguments
  • Fixed explicit checks of PEP 604 unions against types.UnionType ([#467](https://github.com/agronholm/typeguard/issues/467) <https://github.com/agronholm/typeguard/issues/467>_)
  • Fixed checks against annotations wrapped in NotRequired not being run unless the NotRequired is a forward reference ([#454](https://github.com/agronholm/typeguard/issues/454) <https://github.com/agronholm/typeguard/issues/454>_)

4.4.0 (2024-10-27)

  • Added proper checking for method signatures in protocol checks

... (truncated)

Commits
  • d80f566 Added release date
  • 386d4f2 Updated the changelog
  • 0ee471e Updated typing-extensions dependency to fix Python 3.14 compatibility
  • a3f6144 Fixed Union-related test failure on Python 3.14
  • 455bf7b Removed the obsolete UnionTransformer class
  • 92618cd [pre-commit.ci] pre-commit autoupdate (#520)
  • ab02aba Update PyPy to v3.11 in CI
  • 37c6ab2 Migrated test and documentation extras to dependency groups
  • ca512c2 Restore type_params to function instrumented by @typechecked
  • c5d91e9 Fixed @typechecked unable to find the code when PEP 695 type parameters are...
  • Additional commits viewable in compare view

Updates ruamel-yaml from 0.18.12 to 0.18.14

Updates typing-extensions from 4.13.2 to 4.14.0

Release notes

Sourced from typing-extensions's releases.

4.14.0

This release adds several new features, including experimental support for inline typed dictionaries (PEP 764) and sentinels (PEP 661), and support for changes in Python 3.14. In addition, Python 3.8 is no longer supported.

Changes since 4.14.0rc1:

  • Remove __or__ and __ror__ methods from typing_extensions.Sentinel on Python versions <3.10. PEP 604 was introduced in Python 3.10, and typing_extensions does not generally attempt to backport PEP-604 methods to prior versions.
  • Further update typing_extensions.evaluate_forward_ref with changes in Python 3.14.

Changes included in 4.14.0rc1:

  • Drop support for Python 3.8 (including PyPy-3.8). Patch by Victorien Plot.
  • Do not attempt to re-export names that have been removed from typing, anticipating the removal of typing.no_type_check_decorator in Python 3.15. Patch by Jelle Zijlstra.
  • Update typing_extensions.Format, typing_extensions.evaluate_forward_ref, and typing_extensions.TypedDict to align with changes in Python 3.14. Patches by Jelle Zijlstra.
  • Fix tests for Python 3.14 and 3.15. Patches by Jelle Zijlstra.

New features:

  • Add support for inline typed dictionaries (PEP 764). Patch by Victorien Plot.
  • Add typing_extensions.Reader and typing_extensions.Writer. Patch by Sebastian Rittau.
  • Add support for sentinels (PEP 661). Patch by Victorien Plot.

4.14.0rc1

Major changes:

  • Drop support for Python 3.8 (including PyPy-3.8). Patch by Victorien Plot.
  • Do not attempt to re-export names that have been removed from typing, anticipating the removal of typing.no_type_check_decorator in Python 3.15. Patch by Jelle Zijlstra.
  • Update typing_extensions.Format, typing_extensions.evaluate_forward_ref, and typing_extensions.TypedDict to align with changes in Python 3.14. Patches by Jelle Zijlstra.
  • Fix tests for Python 3.14 and 3.15. Patches by Jelle Zijlstra.

New features:

  • Add support for inline typed dictionaries (PEP 764). Patch by Victorien Plot.
  • Add typing_extensions.Reader and typing_extensions.Writer. Patch by Sebastian Rittau.
  • Add support for sentinels (PEP 661). Patch by

... (truncated)

Changelog

Sourced from typing-extensions's changelog.

Release 4.14.0 (June 2, 2025)

Changes since 4.14.0rc1:

  • Remove __or__ and __ror__ methods from typing_extensions.Sentinel on Python versions <3.10. PEP 604 was introduced in Python 3.10, and typing_extensions does not generally attempt to backport PEP-604 methods to prior versions.
  • Further update typing_extensions.evaluate_forward_ref with changes in Python 3.14.

Release 4.14.0rc1 (May 24, 2025)

  • Drop support for Python 3.8 (including PyPy-3.8). Patch by Victorien Plot.
  • Do not attempt to re-export names that have been removed from typing, anticipating the removal of typing.no_type_check_decorator in Python 3.15. Patch by Jelle Zijlstra.
  • Update typing_extensions.Format, typing_extensions.evaluate_forward_ref, and typing_extensions.TypedDict to align with changes in Python 3.14. Patches by Jelle Zijlstra.
  • Fix tests for Python 3.14 and 3.15. Patches by Jelle Zijlstra.

New features:

  • Add support for inline typed dictionaries (PEP 764). Patch by Victorien Plot.
  • Add typing_extensions.Reader and typing_extensions.Writer. Patch by Sebastian Rittau.
  • Add support for sentinels (PEP 661). Patch by Victorien Plot.
Commits

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

@dependabot
build(deps): bump the minor-and-patch group with 6 updates
336930d 
Bumps the minor-and-patch group with 6 updates:

| Package | From | To |
| --- | --- | --- |
| [stac-check](https://github.com/stac-utils/stac-check) | `1.6.0` | `1.7.0` |
| [stac-validator](https://github.com/stac-utils/stac-validator) | `3.7.0` | `3.8.1` |
| [pytest](https://github.com/pytest-dev/pytest) | `8.3.5` | `8.4.0` |
| [typeguard](https://github.com/agronholm/typeguard) | `4.4.2` | `4.4.3` |
| ruamel-yaml | `0.18.12` | `0.18.14` |
| [typing-extensions](https://github.com/python/typing_extensions) | `4.13.2` | `4.14.0` |


Updates `stac-check` from 1.6.0 to 1.7.0
- [Release notes](https://github.com/stac-utils/stac-check/releases)
- [Changelog](https://github.com/stac-utils/stac-check/blob/main/CHANGELOG.md)
- [Commits](stac-utils/stac-check@v1.6.0...v1.7.0)

Updates `stac-validator` from 3.7.0 to 3.8.1
- [Release notes](https://github.com/stac-utils/stac-validator/releases)
- [Changelog](https://github.com/stac-utils/stac-validator/blob/main/CHANGELOG.md)
- [Commits](stac-utils/stac-validator@v3.7.0...v3.8.1)

Updates `pytest` from 8.3.5 to 8.4.0
- [Release notes](https://github.com/pytest-dev/pytest/releases)
- [Changelog](https://github.com/pytest-dev/pytest/blob/main/CHANGELOG.rst)
- [Commits](pytest-dev/pytest@8.3.5...8.4.0)

Updates `typeguard` from 4.4.2 to 4.4.3
- [Release notes](https://github.com/agronholm/typeguard/releases)
- [Changelog](https://github.com/agronholm/typeguard/blob/master/docs/versionhistory.rst)
- [Commits](agronholm/typeguard@4.4.2...4.4.3)

Updates `ruamel-yaml` from 0.18.12 to 0.18.14

Updates `typing-extensions` from 4.13.2 to 4.14.0
- [Release notes](https://github.com/python/typing_extensions/releases)
- [Changelog](https://github.com/python/typing_extensions/blob/main/CHANGELOG.md)
- [Commits](python/typing_extensions@4.13.2...4.14.0)

---
updated-dependencies:
- dependency-name: stac-check
  dependency-version: 1.7.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: stac-validator
  dependency-version: 3.8.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: pytest
  dependency-version: 8.4.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: typeguard
  dependency-version: 4.4.3
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
- dependency-name: ruamel-yaml
  dependency-version: 0.18.14
  dependency-type: indirect
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
- dependency-name: typing-extensions
  dependency-version: 4.14.0
  dependency-type: indirect
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file python Pull requests that update Python code labels Jun 9, 2025
@gadomski gadomski merged commit 5fc328d into main Jun 16, 2025
8 checks passed
@gadomski gadomski deleted the dependabot/pip/minor-and-patch-2f768c3dfc branch June 16, 2025 11:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@github-actions github-actions[bot] github-actions[bot] approved these changes

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file python Pull requests that update Python code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@gadomski