Skip to content

fix(deps): update auth-api updates#3679

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/auth-api-auth-api-updates
Open

fix(deps): update auth-api updates#3679
renovate[bot] wants to merge 1 commit intomainfrom
renovate/auth-api-auth-api-updates

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 3, 2026

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence Type Update Pending
CacheControl 0.14.00.14.4 age confidence dependencies patch
MarkupSafe (changelog) 2.1.12.1.5 age confidence dependencies patch
attrs (changelog) 24.2.024.3.0 age confidence dependencies minor
cachetools 5.5.05.5.2 age confidence dependencies patch
certifi 2026.1.42026.2.25 age confidence dependencies minor
google-cloud-core 2.4.32.5.0 age confidence dependencies minor
google-cloud-pubsub 2.29.02.35.0 age confidence dependencies minor
google-cloud-storage 3.0.03.9.0 age confidence dependencies minor
jsonschema (changelog) 4.17.34.26.0 age confidence dependencies minor
launchdarkly-server-sdk 9.5.09.15.0 age confidence dependencies minor
pytest-asyncio (changelog) ^0.23.8^0.26.0 age confidence test minor
requests (source, changelog) 2.32.42.32.5 age confidence dependencies patch
ruff (source, changelog) ^0.14.1^0.15.0 age confidence dev minor 0.15.4
sqlalchemy-utils ^0.41.2^0.42.0 age confidence dependencies minor
stoplight/prism 3.3.03.3.7 age confidence patch

Release Notes

psf/cachecontrol (CacheControl)

v0.14.4

Compare Source

What's Changed

New Contributors

Full Changelog: psf/cachecontrol@v0.14.3...v0.14.4

v0.14.3

Compare Source

  • Drop support for Python 3.8.

v0.14.2

Compare Source

  • Eliminate a race condition when overwriting cache entries.
  • Fix a requests object leak when doing caching on a streamed response

v0.14.1

Compare Source

What's Changed

New Contributors

Full Changelog: psf/cachecontrol@v0.14.0...v0.14.1

pallets/markupsafe (MarkupSafe)

v2.1.5

Compare Source

Released 2024-02-02

  • Fix striptags not collapsing spaces. :issue:417

v2.1.4

Compare Source

Released 2024-01-19

  • Don't use regular expressions for striptags, avoiding a performance
    issue. :pr:413

v2.1.3

Compare Source

Released 2023-06-02

  • Implement format_map, casefold, removeprefix, and removesuffix
    methods. :issue:370
  • Fix static typing for basic str methods on Markup. :issue:358
  • Use Self for annotating return types. :pr:379

v2.1.2

Compare Source

Released 2023-01-17

  • Fix striptags not stripping tags containing newlines.
    :issue:310
python-attrs/attrs (attrs)

v24.3.0

Compare Source

Backwards-incompatible Changes
Changes
  • Introduce attrs.NothingType, for annotating types consistent with attrs.NOTHING.
    #​1358
  • Allow mutating __suppress_context__ and __notes__ on frozen exceptions.
    #​1365
  • attrs.converters.optional() works again when taking attrs.converters.pipe() or another Converter as its argument.
    #​1372
  • attrs instances now support copy.replace().
    #​1383
  • attrs.validators.instance_of()'s type hints now allow for union types.
    For example: instance_of(str | int)
    #​1385
certifi/python-certifi (certifi)

v2026.2.25

Compare Source

googleapis/python-cloud-core (google-cloud-core)

v2.5.0

Compare Source

Features
Bug Fixes
  • Remove setup.cfg configuration for creating universal wheels (#​332) (78ce8a6)
  • Resolve issue where pre-release versions of dependencies are installed (#​329) (ab9785d)
googleapis/python-pubsub (google-cloud-pubsub)

v2.35.0

Compare Source

Documentation
Features

v2.34.0

Compare Source

Features

v2.33.0

Compare Source

Features
  • Add AwsKinesisFailureReason.ApiViolationReason (ac68093)
  • Add tags to Subscription, Topic, and CreateSnapshotRequest messages for use in CreateSubscription, CreateTopic, and CreateSnapshot requests respectively (ac68093)
  • Annotate some resource fields with their corresponding API types (ac68093)
Bug Fixes
  • Deprecate credentials_file argument (ac68093)
Documentation
  • A comment for field received_messages in message .google.pubsub.v1.StreamingPullResponse is changed (ac68093)

v2.32.0

Compare Source

Features
Bug Fixes

v2.31.1

Compare Source

Bug Fixes

v2.31.0

Compare Source

Features
  • Add MessageTransformationFailureReason to IngestionFailureEvent (#​1427) (8ab13e1)
Bug Fixes
  • Surface Fatal Stream Errors to Future; Adjust Retryable Error Codes (#​1422) (e081beb)

v2.30.0

Compare Source

Features

v2.29.1

Compare Source

Bug Fixes
  • Remove setup.cfg configuration for creating universal wheels (#​1376) (60639c4)
Documentation
  • sample: Add samples for topic and subscription SMTs (#​1386) (4d072e0)
  • Update documentation for JavaScriptUDF to indicate that the message_id metadata field is optional instead of required (#​1380) (be90054)
  • Update readme links (#​1409) (77ba05d)
googleapis/python-storage (google-cloud-storage)

v3.9.0

Compare Source

Features
Bug Fixes

v3.8.0

Compare Source

Features
Bug Fixes

v3.7.0

Compare Source

Features
Bug Fixes

v3.6.0

Compare Source

Features
  • Add support for partial list buckets (#​1606) (92fc2b0)
  • Make return_partial_success and unreachable fields public for list Bucket (#​1601) (323cddd)
  • zb-experimental: Add async write object stream (5ab8103)
  • zb-experimental: Add async write object stream (#​1612) (5ab8103)
Bug Fixes

v3.5.0

Compare Source

Features
Bug Fixes
  • Deprecate credentials_file argument (74415a2)
  • Flaky system tests for resumable_media (#​1592) (7fee3dd)
  • Make download_ranges compatible with asyncio.create_task(..) (#​1591) (faf8b83)
  • Make download_ranges compatible with asyncio.create_task(..) (#​1591) (faf8b83)
  • Redact sensitive data from OTEL traces and fix env var parsing (#​1553) (a38ca19)
  • Redact sensitive data from OTEL traces and fix env var parsing (#​1553) (a38ca19)
  • Use separate header object for each upload in Transfer Manager MPU (#​1595) (0d867bd)

v3.4.1

Compare Source

Bug Fixes
  • Fixes #​1561 by adding an option to specify the entire object checksum for resumable uploads via the upload_from_string, upload_from_file, and upload_from_filename methods (acb918e)

v3.4.0

Compare Source

Features
Bug Fixes

v3.3.1

Compare Source

Bug Fixes
  • Provide option to user to set entire object checksum at "initiate a resumable upload session" and send the same (#​1525) (a8109e0)
  • Send part's checksum for XML MPU part upload (#​1529) (2ad77c7)

v3.3.0

Compare Source

Features
Bug Fixes
Documentation

v3.2.0

Compare Source

Features

v3.1.1

Compare Source

Bug Fixes
  • Add a check for partial response data (#​1487) (7e0412a)
  • Add trove classifier for Python 3.13 (0100916)
  • deps: Require google-crc32c >= 1.1.3 (0100916)
  • deps: Require protobuf >= 3.20.2, < 7.0.0 (0100916)
  • deps: Require requests >= 2.22.0 (0100916)
  • Remove setup.cfg configuration for creating universal wheels (#​1448) (d3b6b3f)
  • Resolve issue where pre-release versions of dependencies are installed (0100916)
  • Segmentation fault in tink while writing data (#​1490) (2a46c0b)
Documentation

v3.1.0

Compare Source

Features
python-jsonschema/jsonschema (jsonschema)

v4.26.0

Compare Source

=======

  • Decrease import time by delaying importing of urllib.request (#​1416).

v4.25.1

Compare Source

=======

  • Fix an incorrect required argument in the Validator protocol's type annotations (#​1396).

v4.25.0

Compare Source

=======

  • Add support for the iri and iri-reference formats to the format-nongpl extra via the MIT-licensed rfc3987-syntax.
    They were alread supported by the format extra. (#​1388).

v4.24.1

Compare Source

=======

  • Properly escape segments in ValidationError.json_path (#​139).

v4.24.0

Compare Source

=======

  • Fix improper handling of unevaluatedProperties in the presence of additionalProperties (#​1351).
  • Support for Python 3.8 has been dropped, as it is end-of-life.

v4.23.0

Compare Source

=======

  • Do not reorder dictionaries (schemas, instances) that are printed as part of validation errors.
  • Declare support for Py3.13

v4.22.0

Compare Source

=======

  • Improve best_match (and thereby error messages from jsonschema.validate) in cases where there are multiple sibling errors from applying anyOf / allOf -- i.e. when multiple elements of a JSON array have errors, we now do prefer showing errors from earlier elements rather than simply showing an error for the full array (#​1250).
  • (Micro-)optimize equality checks when comparing for JSON Schema equality by first checking for object identity, as == would.

v4.21.1

Compare Source

=======

  • Slightly speed up the contains keyword by removing some unnecessary validator (re-)creation.

v4.21.0

Compare Source

=======

  • Fix the behavior of enum in the presence of 0 or 1 to properly consider True and False unequal (#​1208).
  • Special case the error message for {min,max}{Items,Length,Properties} when they're checking for emptiness rather than true length.

v4.20.0

Compare Source

=======

  • Properly consider items (and properties) to be evaluated by unevaluatedItems (resp. unevaluatedProperties) when behind a $dynamicRef as specified by the 2020 and 2019 specifications.
  • jsonschema.exceptions.ErrorTree.__setitem__ is now deprecated.
    More broadly, in general users of jsonschema should never be mutating objects owned by the library.

v4.19.2

Compare Source

=======

  • Fix the error message for additional items when used with heterogeneous arrays.
  • Don't leak the additionalItems keyword into JSON Schema draft 2020-12, where it was replaced by items.

v4.19.1

Compare Source

=======

  • Single label hostnames are now properly considered valid according to the hostname format.
    This is the behavior specified by the relevant RFC (1123).
    IDN hostname behavior was already correct.

v4.19.0

Compare Source

=======

  • Importing the Validator protocol directly from the package root is deprecated.
    Import it from jsonschema.protocols.Validator instead.
  • Automatic retrieval of remote references (which is still deprecated) now properly succeeds even if the retrieved resource does not declare which version of JSON Schema it uses.
    Such resources are assumed to be 2020-12 schemas.
    This more closely matches the pre-referencing library behavior.

v4.18.6

Compare Source

=======

  • Set a jsonschema specific user agent when automatically retrieving remote references (which is deprecated).

v4.18.5

Compare Source

=======

  • Declare support for Py3.12

v4.18.4

Compare Source

=======

  • Improve the hashability of wrapped referencing exceptions when they contain hashable data.

v4.18.3

Compare Source

=======

  • Properly preserve applicable_validators in extended validators.
    Specifically, validators extending early drafts where siblings of $ref were ignored will properly ignore siblings in the extended validator.

v4.18.2

Compare Source

=======

  • Fix an additional regression with the deprecated jsonschema.RefResolver and pointer resolution.

v4.18.1

Compare Source

=======

  • Fix a regression with jsonschema.RefResolver based resolution when used in combination with a custom validation dialect (via jsonschema.validators.create).

v4.18.0

Compare Source

=======

This release majorly rehauls the way in which JSON Schema reference resolution is configured.
It does so in a way that should be backwards compatible, preserving old behavior whilst emitting deprecation warnings.

  • jsonschema.RefResolver is now deprecated in favor of the new referencing library <https://github.com/python-jsonschema/referencing/>_.
    referencing will begin in beta, but already is more compliant than the existing $ref support.
    This change is a culmination of a meaningful chunk of work to make $ref resolution more flexible and more correct.
    Backwards compatibility should be preserved for existing code which uses RefResolver, though doing so is again now deprecated, and all such use cases should be doable using the new APIs.
    Please file issues on the referencing tracker if there is functionality missing from it, or here on the jsonschema issue tracker if you have issues with existing code not functioning the same, or with figuring out how to change it to use referencing.
    In particular, this referencing change includes a change concerning automatic retrieval of remote references (retrieving http://foo/bar automatically within a schema).
    This behavior has always been a potential security risk and counter to the recommendations of the JSON Schema specifications; it has survived this long essentially only for backwards compatibility reasons, and now explicitly produces warnings.
    The referencing library itself will not automatically retrieve references if you interact directly with it, so the deprecated behavior is only triggered if you fully rely on the default $ref resolution behavior and also include remote references in your schema, which will still be retrieved during the deprecation period (after which they will become an error).
  • Support for Python 3.7 has been dropped, as it is nearing end-of-life.
    This should not be a "visible" change in the sense that requires-python has been updated, so users using 3.7 should still receive v4.17.3 when installing the library.
  • On draft 2019-09, unevaluatedItems now properly does not consider items to be evaluated by an additionalItems schema if items is missing from the schema, as the specification says in this case that additionalItems must be completely ignored.
  • Fix the date format checker on Python 3.11 (when format assertion behavior is enabled), where it was too liberal (#​1076).
  • Speed up validation of unevaluatedProperties (#​1075).

Deprecations

  • jsonschema.RefResolver -- see above for details on the replacement
  • jsonschema.RefResolutionError -- see above for details on the replacement
  • relying on automatic resolution of remote references -- see above for details on the replacement
  • importing jsonschema.ErrorTree -- instead import it via jsonschema.exceptions.ErrorTree
  • importing jsonschema.FormatError -- instead import it via jsonschema.exceptions.FormatError
launchdarkly/python-server-sdk (launchdarkly-server-sdk)

v9.15.0

Compare Source

⚠ BREAKING CHANGES

Note: The following breaking changes apply only to FDv2 (Flag Delivery v2) early access features, which are not subject to semantic versioning and may change without a major version bump.


Configuration

📅 Schedule: Branch creation - "before 6am every weekday" in timezone America/Vancouver, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested review from Jxio, ochiu and seeker25 as code owners March 3, 2026 18:46
@renovate renovate bot added the dependencies Pull requests that update a dependency file label Mar 3, 2026
@sonarqubecloud
Copy link

sonarqubecloud bot commented Mar 3, 2026

@@ -1,4 +1,4 @@
FROM python:3.12.5-bookworm as development_build
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NO

@renovate
Copy link
Contributor Author

renovate bot commented Mar 5, 2026

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: auth-api/pyproject.toml
Artifact update for ruff resolved to version 0.15.4, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 0.15.3
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant