Skip to content
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

Bump the python-dependencies group with 3 updates #269

Closed
wants to merge 1 commit into from
Closed

Bump the python-dependencies group with 3 updates #269

wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jul 31, 2023 •
edited
Loading

Updates the requirements on pydantic-settings, sqlalchemy and sphinx-jsonschema to permit the latest version.
Updates pydantic-settings to 2.0.2

Release notes

Sourced from pydantic-settings's releases.

v2.0.2

What's Changed

New Contributors

Full Changelog: pydantic/pydantic-settings@v2.0.1...v2.0.2

Commits
  • 04ec4c7 Prepare release 2.0.2 (#129)
  • 7ebb3bf Separate decoding of complex values into specific method (#128)
  • 5acbdeb Add documentation about compatibility with pydantic 1.x BaseSettings when usi...
  • 2572a18 fix typos in pydantic settings module (#124)
  • b7478d6 Fix typo (fiel_value -> field_value) (#123)
  • 5af2188 Fix a bug when using BaseSettings with RootModel (#120)
  • 14ea54c Fix error when no secret file provided for a complex field. (#118)
  • 5912eb0 Add documentation link to README.md (#121)
  • 1da9fab Use pydantic_settings.SettingsConfigDict instead of pydantic.ConfigDict i...
  • 2303f50 Add support for adding config through class kwargs (#112)
  • Additional commits viewable in compare view

Updates sqlalchemy to 2.0.19

Release notes

Sourced from sqlalchemy's releases.

2.0.19

Released: July 15, 2023

orm

  • [orm] [bug] Fixed issue where setting a relationship collection directly, where an object in the new collection were already present, would not trigger a cascade event for that object, leading to it not being added to the _orm.Session if it were not already present. This is similar in nature to #6471 and is a more apparent issue due to the removal of cascade_backrefs in the 2.0 series. The _orm.AttributeEvents.append_wo_mutation() event added as part of #6471 is now also emitted for existing members of a collection that are present in a bulk set of that same collection.

    References: #10089

  • [orm] [bug] Fixed issue where objects that were associated with an unloaded collection via backref, but were not merged into the _orm.Session due to the removal of cascade_backrefs in the 2.0 series, would not emit a warning that these objects were not being included in a flush, even though they were pending members of the collection; in other such cases, a warning is emitted when a collection being flushed contains non-attached objects which will be essentially discarded. The addition of the warning for backref-pending collection members establishes greater consistency with collections that may be present or non-present and possibly flushed or not flushed at different times based on different relationship loading strategies.

    References: #10090

  • [orm] [bug] [regression] Fixed additional regression caused by #9805 where more aggressive propagation of the "ORM" flag on statements could lead to an internal attribute error when embedding an ORM Query construct that nonetheless contained no ORM entities within a Core SQL statement, in this case ORM-enabled UPDATE and DELETE statements.

    References: #10098

engine

  • [engine] [bug] Renamed _result.Row.t and _result.Row.tuple() to _result.Row._t and _result.Row._tuple(); this is to suit the policy that all methods and pre-defined attributes on Row should be in the style of Python standard library namedtuple where all fixed names have a leading underscore, to avoid name conflicts with existing column names. The previous method/attribute is now deprecated and will

... (truncated)

Commits

Updates sphinx-jsonschema to 1.19.1

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
Bump the python-dependencies group with 3 updates
46ab2c8 
Updates the requirements on [pydantic-settings](https://github.com/pydantic/pydantic-settings), [sqlalchemy](https://github.com/sqlalchemy/sqlalchemy) and [sphinx-jsonschema](https://github.com/lnoor/sphinx-jsonschema) to permit the latest version.

Updates `pydantic-settings` to 2.0.2
- [Release notes](https://github.com/pydantic/pydantic-settings/releases)
- [Commits](pydantic/pydantic-settings@v2.0.1...v2.0.2)

Updates `sqlalchemy` to 2.0.19
- [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)

Updates `sphinx-jsonschema` to 1.19.1
- [Commits](lnoor/sphinx-jsonschema@v1.15...v.1.19.1)

---
updated-dependencies:
- dependency-name: pydantic-settings
  dependency-type: direct:production
  dependency-group: python-dependencies
- dependency-name: sqlalchemy
  dependency-type: direct:production
  dependency-group: python-dependencies
- dependency-name: sphinx-jsonschema
  dependency-type: direct:development
  dependency-group: python-dependencies
...

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 Jul 31, 2023
@dependabot dependabot bot force-pushed the dependabot/pip/python-dependencies-19bae8c0e5 branch from e9dc3b9 to 46ab2c8 Compare July 31, 2023 15:05
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Jul 31, 2023

Looks like these dependencies are updatable in another way, so this is no longer needed.

@dependabot dependabot bot closed this Jul 31, 2023
@dependabot dependabot bot deleted the dependabot/pip/python-dependencies-19bae8c0e5 branch July 31, 2023 15:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
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.
0 participants