Skip to content

Bump sqlalchemy from 2.0.48 to 2.0.49 in /flowdb/testdata/synthetic_data#7264

Open
dependabot[bot] wants to merge 1 commit intomasterfrom
dependabot-pip-flowdb-testdata-synthetic_data-sqlalchemy-2.0.49
Open

Bump sqlalchemy from 2.0.48 to 2.0.49 in /flowdb/testdata/synthetic_data#7264
dependabot[bot] wants to merge 1 commit intomasterfrom
dependabot-pip-flowdb-testdata-synthetic_data-sqlalchemy-2.0.49

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot bot commented on behalf of github Apr 6, 2026

Bumps sqlalchemy from 2.0.48 to 2.0.49.

Release notes

Sourced from sqlalchemy's releases.

2.0.49

Released: April 3, 2026

orm

  • [orm] [bug] Fixed issue where _orm.Session.get() would bypass the identity map and emit unnecessary SQL when with_for_update=False was passed, rather than treating it equivalently to the default of None. Pull request courtesy of Joshua Swanson.

    References: #13176

  • [orm] [bug] Fixed issue where chained _orm.joinedload() options would not be applied correctly when the final relationship in the chain is declared on a base mapper and accessed through a subclass mapper in a _orm.with_polymorphic() query. The path registry now correctly computes the natural path when a property declared on a base class is accessed through a path containing a subclass mapper, ensuring the loader option can be located during query compilation.

    References: #13193

  • [orm] [bug] [inheritance] Fixed issue where using _orm.Load.options() to apply a chained loader option such as _orm.joinedload() or _orm.selectinload() with _orm.PropComparator.of_type() for a polymorphic relationship would not generate the necessary clauses for the polymorphic subclasses. The polymorphic loading strategy is now correctly propagated when using a call such as joinedload(A.b).options(joinedload(B.c.of_type(poly))) to match the behavior of direct chaining e.g. joinedload(A.b).joinedload(B.c.of_type(poly)).

    References: #13202

  • [orm] [bug] [inheritance] Fixed issue where using chained loader options such as _orm.selectinload() after _orm.joinedload() with _orm.PropComparator.of_type() for a polymorphic relationship would not properly apply the chained loader option. The loader option is now correctly applied when using a call such as joinedload(A.b.of_type(poly)).selectinload(poly.SubClass.c) to eagerly load related objects.

    References: #13209

typing

  • [typing] [bug] Fixed a typing issue where the typed members of :data:.func would return the appropriate class of the same name, however this creates an issue for

... (truncated)

Commits

Dependabot compatibility score

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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [sqlalchemy](https://github.com/sqlalchemy/sqlalchemy) from 2.0.48 to 2.0.49.
- [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: sqlalchemy
  dependency-version: 2.0.49
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the FlowDB Issues related to FlowDB label Apr 6, 2026
@cypress
Copy link
Copy Markdown

cypress bot commented Apr 6, 2026

FlowAuth    Run #25899

Run Properties:  status check failed Failed #25899  •  git commit 1edadf4386: Bump sqlalchemy from 2.0.48 to 2.0.49 in /flowdb/testdata/synthetic_data
Project FlowAuth
Branch Review dependabot-pip-flowdb-testdata-synthetic_data-sqlalchemy-2.0.49
Run status status check failed Failed #25899
Run duration 03m 36s
Commit git commit 1edadf4386: Bump sqlalchemy from 2.0.48 to 2.0.49 in /flowdb/testdata/synthetic_data
Committer dependabot[bot]
View all properties for this run ↗︎

Test results
Tests that failed  Failures 2
Tests that were flaky  Flaky 2
Tests that did not run due to a developer annotating a test with .skip  Pending 0
Tests that did not run due to a failure in a mocha hook  Skipped 6
Tests that passed  Passing 35
View all changes introduced in this branch ↗︎

Tests for review

Failed  add_new_user.js • 1 failed test

View Output

Test Artifacts
User management > Add User Test Replay Screenshots
Failed  role_list.js • 1 failed test

View Output

Test Artifacts
role list screen > Add blank role Test Replay Screenshots
Flakiness  add_new_server.js • 1 flaky test

View Output

Test Artifacts
Server management > Add server Test Replay Screenshots
Flakiness  two_factor_auth.js • 1 flaky test

View Output

Test Artifacts
Two-factor setup > Two factor setup flow. Test Replay Screenshots

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

Labels

FlowDB Issues related to FlowDB

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants