Bump sqlalchemy from 1.4.52 to 2.0.35

[dependabot]

Bumps sqlalchemy from 1.4.52 to 2.0.35.

Release notes

Sourced from sqlalchemy's releases.

2.0.35

Released: September 16, 2024

orm

• [orm] [bug] [typing] Fixed issue where it was not possible to use typing.Literal with Mapped[] on Python 3.8 and 3.9. Pull request courtesy Frazer McLean.

  References: #11820

• [orm] [bug] Fixed issue in ORM evaluator where two datatypes being evaluated with the SQL concatenator operator would not be checked for UnevaluatableError based on their datatype; this missed the case of _postgresql.JSONB values being used in a concatenate operation which is supported by PostgreSQL as well as how SQLAlchemy renders the SQL for this operation, but does not work at the Python level. By implementing UnevaluatableError for this combination, ORM update statements will now fall back to "expire" when a concatenated JSON value used in a SET clause is to be synchronized to a Python object.

  References: #11849

• [orm] [bug] An warning is emitted if _orm.joinedload() or _orm.subqueryload() are used as a top level option against a statement that is not a SELECT statement, such as with an insert().returning(). There are no JOINs in INSERT statements nor is there a "subquery" that can be repurposed for subquery eager loading, and for UPDATE/DELETE joinedload does not support these either, so it is never appropriate for this use to pass silently.

  References: #11853

• [orm] [bug] Fixed issue where using loader options such as _orm.selectinload() with additional criteria in combination with ORM DML such as _sql.insert() with RETURNING would not correctly set up internal contexts required for caching to work correctly, leading to incorrect results.

  References: #11855

mysql

• [mysql] [bug] Fixed issue in mariadbconnector dialect where query string arguments that weren't checked integer or boolean arguments would be ignored, such as string arguments like unix_socket, etc. As part of this change, the argument parsing for particular elements such as client_flags, compress, local_infile has been made more consistent across all

... (truncated)

Commits

• See full diff in compare view

You can trigger a rebase of this PR 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 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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[jezdez]

@dependabot rebase

[jezdez]

@dependabot rebase

[Copilot]

Pull Request Overview

This PR bumps SQLAlchemy from 1.4.52 to 2.0.35 and updates various dependency versions and configuration settings to support a new development domain. Key changes include:

• Updating dependency versions in requirements.in and package.json.
• Refactoring configuration, admin views, and development scripts (docker-compose, Procfile.dev, and Makefile) for improved development setup.
• Removing embedded self‐signed certificates to reflect new infrastructure and domain settings.

Reviewed Changes

Copilot reviewed 15 out of 15 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
requirements.in	Updated dependency constraints to support SQLAlchemy 2.x and added several new packages.
package.json	Added a new devDependency for SASS transformation.
migrations/env.py	Minor syntax update with an added trailing comma.
jazzband/projects/views.py	Cleaned up error message string formatting.
jazzband/config.py	Updated SERVER_NAME and HOSTNAMES to use the new domain.
jazzband/admin.py	Refactored inline models and removed the explicit template_mode setting.
jazzband/account/views.py	Consolidated error message formatting.
docker-compose.yml	Added an environment variable for insecure OAuth transport and new service labels.
certs/*	Removed embedded self-signed certificate and key files.
README.md	Updated documentation to reflect the new development domain and tooling.
Procfile.dev	Removed certificate flags from the Flask run command for development.
Makefile	Removed mkcert trust and cert targets in line with certificate removal.

Comments suppressed due to low confidence (3)

jazzband/admin.py:92

• [nitpick] The removal of the explicit template_mode setting may affect the UI theme. Please confirm that adopting the default theme settings is intentional.

        template_mode="bootstrap4",

Makefile:57

• [nitpick] The removal of the mkcert trust and cert targets may affect new developer setup. Please update the README or setup instructions if this change is intentional.

trust:

Procfile.dev:1

• [nitpick] The removal of the certificate parameters from the Flask run command indicates a switch to HTTP in development. Confirm that this change aligns with your development and testing requirements.

web: flask run -h 0.0.0.0 -p 5000