Bump alembic from 1.19.1 to 1.19.2 in /server

[dependabot]

Bumps alembic from 1.19.1 to 1.19.2.

Release notes

Sourced from alembic's releases.

1.19.2

Released: September 4, 2026

changed

• [changed] [autogenerate] The autogenerate plugin for CHECK constraint detection by name, added in 1.19.0. for #508, is no longer enabled by default. It has been renamed from alembic.autogenerate.checkconstraint_byname to alembic.ext.checkconstraint_byname and no longer matches on the "alembic.autogenerate.*" wildcard, which remains the default plugin specification. The previous name will still function as well if placed in the plugins list explicitly, both to enable the plugin and within a "~" exclusion, so that an env.py written against 1.19.0 or 1.19.1 requires no change.

  The plugin is now recommended only for schemas that ensure the naming of all constraints using a client side naming convention, otherwise there's a persistent risk of false positives. See autogenerate_check_constraints for background on things to be aware of when using this plugin.

  As part of this change "type bound" CHECK constraints, which include constraints generated for the Boolean and Enum datatypes when the create_constraint parameter is set to True, are no longer ignored in the metadata side, so that normal name-based matching can occur for these constraints.

  References: #1859

usecase

• [usecase] [autogenerate] [batch] The target of a ~sqlalchemy.schema.ForeignKey is now located using the ForeignKey.target_tokens and ForeignKey.target_table_key accessors added in SQLAlchemy 2.1, rather than by splitting the dotted string form of that target on ".". As a dot inside a schema, table or column name cannot be told apart from the separator between those names, a foreign key whose target name contained a dot was previously mis-parsed by autogenerate rendering as well as by batch migrations. The dotted string continues to be split when running against SQLAlchemy 2.0, where these accessors are not present. Thanks to Gyanu Mayank for the initial pull request.

  References: #1860

Commits

• See full diff in compare view

[github-actions]

Client V3 Test Results

39 tests   39 ✅  0s ⏱️
 4 suites   0 💤
 1 files     0 ❌

Results for commit bfab783.

♻️ This comment has been updated with latest results.

[github-actions]

Client Test Results

132 tests   132 ✅  0s ⏱️
  7 suites    0 💤
  1 files      0 ❌

Results for commit bfab783.

♻️ This comment has been updated with latest results.

[github-actions]

Python Test Results

  1 files    1 suites   2m 31s ⏱️
863 tests 863 ✅ 0 💤 0 ❌
868 runs  868 ✅ 0 💤 0 ❌

Results for commit bfab783.

♻️ This comment has been updated with latest results.

[github-actions]

Playwright E2E Results (chromium)

221 tests   221 ✅  2m 19s ⏱️
 14 suites    0 💤
  1 files      0 ❌

Results for commit bfab783.

♻️ This comment has been updated with latest results.

[github-actions]

Playwright E2E Results (firefox)

221 tests   221 ✅  2m 17s ⏱️
 14 suites    0 💤
  1 files      0 ❌

Results for commit bfab783.

♻️ This comment has been updated with latest results.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud