Skip to content

deps(app): bump the production-dependencies group across 1 directory with 7 updates - #339

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/uv/production-dependencies-c43dea2224
Open

deps(app): bump the production-dependencies group across 1 directory with 7 updates#339
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/uv/production-dependencies-c43dea2224

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 5, 2026

Copy link
Copy Markdown
Contributor

Bumps the production-dependencies group with 7 updates in the / directory:

Package From To
psycopg[binary] 3.3.4 3.3.5
pydantic-settings 2.14.2 2.15.0
pydantic 2.13.4 2.13.5
pydis-core 11.10.0 11.10.1
rapidfuzz 3.14.5 3.14.6
sentry-sdk 2.66.1 2.68.1
sqlalchemy 2.0.51 2.0.52

Updates psycopg[binary] from 3.3.4 to 3.3.5

Changelog

Sourced from psycopg[binary]'s changelog.

.. currentmodule:: psycopg

.. index:: single: Release notes single: News

psycopg release notes

Current release

Psycopg 3.3.5 ^^^^^^^^^^^^^

  • Discard prepared statements upon :sql:ALTER * or DISCARD * (:ticket:[#1307](https://github.com/psycopg/psycopg/issues/1307)).
  • Fix !ProgrammingError when dumping non-!None values with no !NoneType dumper registered in python implementation (:ticket:[#1325](https://github.com/psycopg/psycopg/issues/1325)).
  • Fix !wait_selector wait function to not raise !KeyError (:ticket:[#1327](https://github.com/psycopg/psycopg/issues/1327)).
  • Fix !DataError messages leaking the literal {...} placeholder instead of the offending value when loading a pre-year-1 :sql:timestamp or a malformed binary :sql:jsonb value (:ticket:[#1372](https://github.com/psycopg/psycopg/issues/1372)).
  • Raise !DataError instead of !ValueError when ~psycopg.rows.namedtuple_row receives duplicate column names (:ticket:[#1348](https://github.com/psycopg/psycopg/issues/1348)).
  • Raise !DataError on inconsistent copy data (:tickets:[#1359](https://github.com/psycopg/psycopg/issues/1359), [#1360](https://github.com/psycopg/psycopg/issues/1360)).
  • Handle client encodings aliases (:ticket:[#1363](https://github.com/psycopg/psycopg/issues/1363)).
  • Fix building C extension with Cython 3.3.

Psycopg 3.3.4 ^^^^^^^^^^^^^

  • Fix possible spurious connection timeout in systems with very long uptimes in C extension (:ticket:[#1280](https://github.com/psycopg/psycopg/issues/1280)).
  • Fix client-side adaptation of enums whose name require quotes (:ticket:[#1298](https://github.com/psycopg/psycopg/issues/1298)).
  • Consistently populate ~Cursor.statusmessage after ~Cursor.executemany() (:ticket:[#1302](https://github.com/psycopg/psycopg/issues/1302)).

Psycopg 3.3.3 ^^^^^^^^^^^^^

  • Retain Error.pgconn when raising a single exception for multiple connection attempt errors (:ticket:[#1246](https://github.com/psycopg/psycopg/issues/1246)).
  • Return a proper error when server sends ErrorResponse for a Sync after a Parse (:ticket:[#1260](https://github.com/psycopg/psycopg/issues/1260)).

... (truncated)

Commits
  • ea542c9 chore: bump psycopg package version to 3.3.5
  • 8d31e47 chore(deps): bump the actions group across 1 directory with 4 updates
  • 268f863 Merge pull request #1370 from Sanjays2402/fix/truncated-binary-copy-error
  • a412fa4 docs: put together different issues fixed around copy parsing
  • f757307 fix: clearer error messages according to truncated copy message part
  • b1f17c4 test: move existing COPY format parsing tests into a single module
  • 21eba57 test: drop useless parametrization of copy binary parsigh test
  • 6780e17 fix(copy): handle truncated binary row headers
  • 2f2fcfb Merge pull request #1364 from DylanYoung/fix_client_encoding_aliases
  • ccc351e refactor: don't store the encodings raw table as a dict
  • Additional commits viewable in compare view

Updates pydantic-settings from 2.14.2 to 2.15.0

Release notes

Sourced from pydantic-settings's releases.

v2.15.0

Highlights

Behavior changes

  • case_sensitive now applies to init kwargs and config-file sources (#900). InitSettingsSource and the JSON/TOML/YAML config sources previously ignored case_sensitive. Since it defaults to False, case-insensitive matching is now the default for these sources — e.g. Settings(TeSt=...) now populates a test field where it previously did not. Nested keys are still matched case-sensitively.
  • Fields with unresolved forward references now emit a warning (#901). Settings sources can silently fail to resolve such fields; they now raise IncompleteFieldDefinitionWarning telling you to call model_rebuild(). If you have filterwarnings = error configured, this may surface as a new failure.
  • Non-JSON env values for strict fields now raise ValidationError (#926) instead of a less specific error.

New features

  • Show environment variable names in CLI help via cli_show_env_vars=True (#860), so generated --help output doubles as configuration documentation.
  • PYDANTIC_SETTINGS_DEBUG for debugging settings resolution (#906, #913). Set it to a truthy value with DEBUG logging enabled to see each source's contribution in priority order, which source won for each value, and which env_file/secret files were probed, loaded, or skipped — the long-standing "why isn't my .env being picked up?" question.
  • toml_table_header for regular TOML files (#882, #886, #887), letting you root settings at a nested table in any TOML file, not just pyproject.toml.
  • Traversable support for JSON/TOML/YAML file sources (#902), so you can load config packaged inside a distribution — including files inside a zip or wheel — via importlib.resources.files(...) without casting to Path.
  • GCP: project_id can come from an earlier settings source (#878), rather than only from the constructor or GOOGLE_CLOUD_PROJECT.

Bug fixes

  • Fix env vars not loading on Windows with case_sensitive=True (#894). Windows upper-cases os.environ keys, so fields raised Field required instead of picking up their values.
  • Read secret files as UTF-8 instead of the platform locale encoding (#917). On Windows code pages such as cp1252 this silently corrupted non-ASCII secrets.
  • Fix AliasPath on nested model fields not JSON-decoding env values (#898).
  • Fix case-insensitive matching for optional nested models (#905).
  • Fix dotenv extras being wrongly claimed by a complex field sharing a name prefix (#912) — e.g. dbx_token being swallowed by a db: dict field.
  • Fix nested_model_default_partial_update=True corrupting discriminated unions (#876).
  • Fix Secret subclasses crashing when loaded from the environment (#920).
  • Fix enum names not parsing through nested annotations such as Optional[Annotated[MyEnum, ...]] with env_parse_enums=True (#910).
  • An empty yaml_config_section now falls back to defaults instead of raising AttributeError: 'NoneType' object has no attribute 'keys' (#914).
  • NestedSecretsSettingsSource no longer follows symlinks pointing outside secrets_dir (#889).
  • GCP: skip the list_secrets call when case_sensitive=True (#862), lowering the required IAM permissions to just roles/secretmanager.secretAccessor.
  • AWS: types-boto3[secretsmanager] is no longer required at runtime (#880).

Documentation

  • Document JSON parsing of complex env values, plus a comma-separated-values recipe (#919).
  • Recommend an async settings loading pattern (#908).
  • Clarify behavior when an unprefixed value is present in a dotenv file (#895).
  • Clarify environment variable helper descriptions (#867) and fix assorted typos (#904).

What's Changed

... (truncated)

Commits
  • f725ca1 Prepare release 2.15.0 (#930)
  • 28f35c2 Bump the python-packages group with 4 updates (#929)
  • 9056db0 test: move function-local imports to the top of test modules (#927)
  • f077e3a fix: raise ValidationError for non-JSON env values on strict fields (#926)
  • ae25d70 fix: treat Secret subclasses as non-complex fields (#716) (#920)
  • 798dcea Bump the python-packages group with 4 updates (#924)
  • a190041 Bump the github-actions group with 4 updates (#925)
  • 5d93332 Bump the python-packages group with 4 updates (#921)
  • d2fdeda fix: read secret files as UTF-8 instead of the locale encoding (#917)
  • 2256a4e Bump the python-packages group with 3 updates (#915)
  • Additional commits viewable in compare view

Updates pydantic from 2.13.4 to 2.13.5

Release notes

Sourced from pydantic's releases.

v2.13.5 (2026-08-28)

What's Changed

Fixes

  • Allow reuse of validators when plugins are set by @​Viicos in #13535
  • Fix missing GC traversal on some pydantic-core struct fields by @​Viicos in #13624
  • Fix missing GC traversal in pydantic-core for GeneralFieldsSerializer by @​Viicos in #13629
  • Count validated model fields once in smart unions by @​tamird in #13731
Changelog

Sourced from pydantic's changelog.

v2.13.5 (2026-08-28)

GitHub release

What's Changed

Fixes

  • Allow reuse of validators when plugins are set by @​Viicos in #13535
  • Fix missing GC traversal on some pydantic-core struct fields by @​Viicos in #13624
  • Fix missing GC traversal in pydantic-core for GeneralFieldsSerializer by @​Viicos in #13629
  • Count validated model fields once in smart unions by @​tamird in #13731
Commits
  • 001dea0 Bump pypa/gh-action-pypi-publish action to v1.14.2
  • 558379f Bump twine to v7.0.0
  • 2cfd5d3 Do not check for docs build
  • a735bee Fix more Clippy lints
  • 7eed4a1 Fix Clippy 0.1.95 warnings
  • b353bbb Prepare release v2.13.5
  • 63d2ccc Count validated model fields once in smart unions
  • a53ec2e Speed up PyPy CI tests
  • d65e0f9 Workaround circular import error in Mypy
  • 47a6dbf Fix missing GC traversal in pydantic-core for GeneralFieldsSerializer
  • Additional commits viewable in compare view

Updates pydis-core from 11.10.0 to 11.10.1

Changelog

Sourced from pydis-core's changelog.

.. See docs for details on formatting your entries https://releases.readthedocs.io/en/latest/concepts.html

Changelog

  • :release:11.10.1 <5th March 2026>

  • :feature:313 Update :obj:pydis_core.utils.regex.DISCORD_INVITE to also match a "。" (HALFWIDTH IDEOGRAPHIC FULL STOP)

  • :release:11.10.0 <17th May 2026>

  • :feature:312 Update format of :obj:pydis_core.utils.logging.log_format to include the function & line number in the output

  • :feature:312 Log when all cogs are done loading

  • :release:11.9.0 <5th March 2026>

  • :breaking:- Drop support for Python 3.11.

  • :breaking:- Remove sphinx-multiversion as it's unmaintained and causes issues with our docs builds.

  • :feature:311 Introduce :obj:pydis_core.utils.converters.ISODateTime converter for parsing ISO 8601 formatted date-time strings in commands.

  • :release:11.8.0 <17th October 2025>

  • :feature:305 Update :obj:pydis_core.utils.checks.in_whitelist_check to check against the parent channel, if one exists, instead of the ctx.channel.id.

  • :release:11.7.0 <10th August 2025>

  • 🐛304 major Update Discord invite regex to handle new protocol.

  • :release:11.6.1 <13th July 2025>

  • 🐛303 Update Discord invite regex to handle cases with additional slashes.

  • :release:11.6.0 <18th February 2025>

  • 🐛302 major Bump Discord.py to :literal-url:2.5.0 <https://discordpy.readthedocs.io/en/stable/whats_new.html#v2-5-0>.

  • :release:11.5.1 <23rd November 2024>

  • 🐛295 Update :obj:pydis_core.utils.regex.DISCORD_INVITE to not be overly strict.

  • :release:11.5.0 <17th October 2024>

  • :feature:282 Update :obj:pydis_core.utils.regex.DISCORD_INVITE to cover more edge cases.

  • :release:11.4.0 <11th September 2024>

  • :feature:269 Update :obj:pydis_core.utils.regex.DISCORD_INVITE to also match backslash before the invite code.

  • :release:11.3.1 <25th July 2024>

  • 🐛- Correct the docstring of :obj:pydis_core.utils.interactions.ViewWithUserAndRoleCheck.

  • :release:11.3.0 <17th July 2024>

  • :feature:254 Add a py.typed file for :literal-url:PEP 561 <https://peps.python.org/pep-0561/> compliance.

... (truncated)

Commits

Updates rapidfuzz from 3.14.5 to 3.14.6

Release notes

Sourced from rapidfuzz's releases.

Release 3.14.6

Fixed

  • fix some divergences in the pure Python fallback
  • fix compatibility with new Cython versions
  • fixed potential out of bound access inside Editops.remove_subsequence
  • fixed handling python fallback implementation of Editops.remove_subsequence

Removed

  • dropped support for Python 3.10
  • dropped wheels for experimental Python 3.13 free threaded
Changelog

Sourced from rapidfuzz's changelog.

Changelog

[3.14.6] - 2026-08-30 ^^^^^^^^^^^^^^^^^^^^^ Fixed

* fix some divergences in the pure Python fallback
* fix compatibility with new Cython versions
* fixed potential out of bound access inside Editops.remove_subsequence
* fixed handling python fallback implementation of Editops.remove_subsequence

Removed

  • dropped support for Python 3.10
  • dropped wheels for experimental Python 3.13 free threaded

[3.14.5] - 2026-04-07 ^^^^^^^^^^^^^^^^^^^^^ Fixed

* fix release ci attempting to upload a pyodide wheel

[3.14.4] - 2026-04-06 ^^^^^^^^^^^^^^^^^^^^^ Added

  • add risc64 wheels
  • add support for taskflow 4.0.0

Changed

* upgrade to ``Cython==3.2.4``.

Fixed

* fix type hints for extractOne when no score_cutoff is provided

[3.14.3] - 2025-11-01
^^^^^^^^^^^^^^^^^^^^^
Fixed

  • add missing pypy and freethreaded linux wheels

Removed

  • drop s390x and ppc64le wheels since they are virtually unused and require extremely long to build under emulation

[3.14.2] - 2025-10-30 ^^^^^^^^^^^^^^^^^^^^^

... (truncated)

Commits
  • d1b4a18 fix cython call
  • f7be71b fix typo
  • 3199c87 fix version tag
  • 7b57e51 update date
  • 15e68d7 update rapidfuzz-cpp
  • b637f9f don't hand out references to internal elements
  • 868a451 fix Editops.remove_subsequence
  • 83b8b84 fix compatibility with new Cython versions
  • 24f2ac5 Bump pypa/cibuildwheel from 4.1.1 to 4.2.0 in the github-actions group
  • 03a5137 Bump pypa/gh-action-pypi-publish in the github-actions group
  • Additional commits viewable in compare view

Updates sentry-sdk from 2.66.1 to 2.68.1

Release notes

Sourced from sentry-sdk's releases.

2.68.1

enable_logs

  • (logs) Don't stop sending auto-collected logs when enable_logs=True by @​sentrivana in #7237

    If you have enable_logs set to True, our logging integrations for the standard library logging module as well as Loguru will auto-collect logs and send them to Sentry as Sentry logs by default, preserving old behavior. Turning automatic collection off for a specific integration can still be achieved using the capture_sentry_logs integration option.

    import sentry_sdk
    from sentry_sdk.integrations.logging import LoggingIntegration
    from sentry_sdk.integrations.loguru import LoguruIntegration
    sentry_sdk.init(
    enable_logs=True,
    integrations=[
    LoggingIntegration(capture_sentry_logs=True),
    LoguruIntegration(capture_sentry_logs=False),
    ],
    )

    Please note that the enable_logs option is deprecated and will be removed in the next major release. The sentry_sdk.logger.X API now works regardless of it, and auto-collection can be opted into via the capture_sentry_logs integration-level options, which are False by default, unless you have enable_logs=True. We've added this compatibility layer to make the transition to a enable_logs-free world easier.

Bug Fixes 🐛

2.68.0

Important

  • We're making enable_logs and enable_metrics no-op with this release (#7177), and they'll be dropped in the next major.

    Previously, enable_logs also controlled automatic logs collection from the logging and Loguru integrations. These integrations now get an integration-level capture_sentry_logs boolean option to allow for more control over the auto-collection. These options are False by default, i.e., nothing is auto-collected without your explicit opt-in.

    Action Needed

    If you had enable_logs set to True:

    • If you were using the sentry_sdk.logger.X API, no action necessary, the API will just work.
    • If you were auto-collecting logs from either LoggingIntegration or LoguruIntegration, the auto-collection will be turned off in this release. You can switch auto-collection on explicitly with:
    import sentry_sdk
    from sentry_sdk.integrations.logging import LoggingIntegration
    from sentry_sdk.integrations.loguru import LoguruIntegration

... (truncated)

Changelog

Sourced from sentry-sdk's changelog.

2.68.1

enable_logs

  • (logs) Don't stop sending auto-collected logs when enable_logs=True by @​sentrivana in #7237

    If you have enable_logs set to True, our logging integrations for the standard library logging module as well as Loguru will auto-collect logs and send them to Sentry as Sentry logs by default, preserving old behavior. Turning automatic collection off for a specific integration can still be achieved using the capture_sentry_logs integration option.

    import sentry_sdk
    from sentry_sdk.integrations.logging import LoggingIntegration
    from sentry_sdk.integrations.loguru import LoguruIntegration
    sentry_sdk.init(
    enable_logs=True,
    integrations=[
    LoggingIntegration(capture_sentry_logs=True),
    LoguruIntegration(capture_sentry_logs=False),
    ],
    )

    Please note that the enable_logs option is deprecated and will be removed in the next major release. The sentry_sdk.logger.X API now works regardless of it, and auto-collection can be opted into via the capture_sentry_logs integration-level options, which are False by default, unless you have enable_logs=True. We've added this compatibility layer to make the transition to a enable_logs-free world easier.

Bug Fixes 🐛

2.68.0

Important

  • We're making enable_logs and enable_metrics no-op with this release (#7177), and they'll be dropped in the next major.

    Previously, enable_logs also controlled automatic logs collection from the logging and Loguru integrations. These integrations now get an integration-level capture_sentry_logs boolean option to allow for more control over the auto-collection. These options are False by default, i.e., nothing is auto-collected without your explicit opt-in.

    Action Needed

    If you had enable_logs set to True:

    • If you were using the sentry_sdk.logger.X API, no action necessary, the API will just work.
    • If you were auto-collecting logs from either LoggingIntegration or LoguruIntegration, the auto-collection will be turned off in this release. You can switch auto-collection on explicitly with:

... (truncated)

Commits
  • 98f7d91 Update changelog
  • 8f886ff release: 2.68.1
  • df4ec02 fix(logs): Don't stop sending auto-collected logs when enable_logs=True (#7...
  • e320318 test(pyramid): Add tests for data_collection gating of request body (#7218)
  • 7b8a385 test(bottle): Add tests for data_collection gating of request body (#7217)
  • cbcadc9 test(sanic): Add tests for data_collection gating of request body (#7216)
  • e42c798 feat(tornado): Gate request body collection on data_collection option (#7215)
  • d05bb60 test(django): Add tests for data_collection gating of request body (#7213)
  • bcce67b feat(wsgi): Gate request body collection on data_collection option (#7212)
  • 41220c4 fix(google_genai): Gate streaming gen_ai.response.tool_calls on outputs, no...
  • Additional commits viewable in compare view

Updates sqlalchemy from 2.0.51 to 2.0.52

Release notes

Sourced from sqlalchemy's releases.

2.0.52

Released: August 11, 2026

platform

  • [platform] [bug] Python 3.15 support has been added and tested, including minimal changes for full compatibility.

    References: #13477

orm

  • [orm] [bug] Fixed a result-column misalignment bug in ORM-enabled UPDATE statements where synchronize_session="fetch" is in use, either explicitly or because the statement uses constructs such as CTEs that implicitly select for it. Columns in rows returned by .returning() could be returned under incorrect keys (e.g. row[SomeClass.a] returning the value of a different column), a problem most likely to manifest under concurrent workloads. ORM DELETE statements were not affected.

    References: #13439

  • [orm] [bug] Fixed bug where a failed _orm.Session.bulk_insert_mappings(), _orm.Session.bulk_update_mappings() or _orm.Session.bulk_save_objects() call could leave the _orm.Session permanently in a "flushing" state, such as when the transaction could not be begun because a previous flush had left it needing a rollback. Unlike _orm.Session.flush(), the bulk methods set the internal flushing flag and began the transaction outside of the try/finally block that resets it, so that neither _orm.Session.rollback() nor _orm.Session.close() would clear it, and every subsequent flush would raise InvalidRequestError: Session is already flushing. Pull request courtesy Hamody We.

    References: #13485

  • [orm] [bug] Fixed issue where unpickling an ORM object that were loaded using loader options making use of wildcard tokens, such as _orm.load_only() or _orm.raiseload() with "*", would fail with KeyError or IndexError if the process doing the unpickling had not yet constructed a loader path making use of that same token. This would typically be observed when the object were unpickled in a separate process, such as with the spawn or forkserver multiprocessing start methods, the latter of which became the default on POSIX platforms as of Python 3.14. The internal collection of these tokens is now established up front, so that it is identical in every process.

... (truncated)

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 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

…with 7 updates

Bumps the production-dependencies group with 7 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [psycopg[binary]](https://github.com/psycopg/psycopg) | `3.3.4` | `3.3.5` |
| [pydantic-settings](https://github.com/pydantic/pydantic-settings) | `2.14.2` | `2.15.0` |
| [pydantic](https://github.com/pydantic/pydantic) | `2.13.4` | `2.13.5` |
| [pydis-core](https://github.com/python-discord/bot-core) | `11.10.0` | `11.10.1` |
| [rapidfuzz](https://github.com/rapidfuzz/RapidFuzz) | `3.14.5` | `3.14.6` |
| [sentry-sdk](https://github.com/getsentry/sentry-python) | `2.66.1` | `2.68.1` |
| [sqlalchemy](https://github.com/sqlalchemy/sqlalchemy) | `2.0.51` | `2.0.52` |



Updates `psycopg[binary]` from 3.3.4 to 3.3.5
- [Changelog](https://github.com/psycopg/psycopg/blob/master/docs/news.rst)
- [Commits](psycopg/psycopg@3.3.4...3.3.5)

Updates `pydantic-settings` from 2.14.2 to 2.15.0
- [Release notes](https://github.com/pydantic/pydantic-settings/releases)
- [Commits](pydantic/pydantic-settings@v2.14.2...v2.15.0)

Updates `pydantic` from 2.13.4 to 2.13.5
- [Release notes](https://github.com/pydantic/pydantic/releases)
- [Changelog](https://github.com/pydantic/pydantic/blob/v2.13.5/HISTORY.md)
- [Commits](pydantic/pydantic@v2.13.4...v2.13.5)

Updates `pydis-core` from 11.10.0 to 11.10.1
- [Release notes](https://github.com/python-discord/bot-core/releases)
- [Changelog](https://github.com/python-discord/bot-core/blob/main/docs/changelog.rst)
- [Commits](python-discord/bot-core@v11.10.0...v11.10.1)

Updates `rapidfuzz` from 3.14.5 to 3.14.6
- [Release notes](https://github.com/rapidfuzz/RapidFuzz/releases)
- [Changelog](https://github.com/rapidfuzz/RapidFuzz/blob/main/CHANGELOG.rst)
- [Commits](rapidfuzz/RapidFuzz@v3.14.5...v3.14.6)

Updates `sentry-sdk` from 2.66.1 to 2.68.1
- [Release notes](https://github.com/getsentry/sentry-python/releases)
- [Changelog](https://github.com/getsentry/sentry-python/blob/master/CHANGELOG.md)
- [Commits](getsentry/sentry-python@2.66.1...2.68.1)

Updates `sqlalchemy` from 2.0.51 to 2.0.52
- [Release notes](https://github.com/sqlalchemy/sqlalchemy/releases)
- [Changelog](https://github.com/sqlalchemy/sqlalchemy/blob/main/CHANGES.rst)
- [Commits](https://github.com/sqlalchemy/sqlalchemy/commits)

---
updated-dependencies:
- dependency-name: psycopg[binary]
  dependency-version: 3.3.5
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-dependencies
- dependency-name: pydantic-settings
  dependency-version: 2.15.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-dependencies
- dependency-name: pydantic
  dependency-version: 2.13.5
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-dependencies
- dependency-name: pydis-core
  dependency-version: 11.10.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-dependencies
- dependency-name: rapidfuzz
  dependency-version: 3.14.6
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-dependencies
- dependency-name: sentry-sdk
  dependency-version: 2.68.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-dependencies
- dependency-name: sqlalchemy
  dependency-version: 2.0.52
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github

dependabot Bot commented on behalf of github Sep 5, 2026

Copy link
Copy Markdown
Contributor Author

Labels

The following labels could not be found: apps. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Sep 5, 2026
@dependabot
dependabot Bot requested review from a team as code owners September 5, 2026 09:43
@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Sep 5, 2026
@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatedpsycopg@​3.3.4 ⏵ 3.3.5100 +110010010070
Updatedsentry-sdk@​2.66.1 ⏵ 2.68.193 +1100100100100
Updatedsqlalchemy@​2.0.51 ⏵ 2.0.5296100100100100
Updatedrapidfuzz@​3.14.5 ⏵ 3.14.699100100100100
Updatedpydis-core@​11.10.0 ⏵ 11.10.199100100100100
Updatedpydantic@​2.13.4 ⏵ 2.13.5100 +1100100100100
Updatedpydantic-settings@​2.14.2 ⏵ 2.15.0100 +1100100100100

View full report

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.

0 participants