[bgunebakan]

Summary of the changes / Why this is an improvement

Drops support for SQLAlchemy 1.3, and adds deprecate warning for SQLAlchemy 1.4. SQLAlchemy 1.3 has been EOL since March 2021. It has no wheels for Python versions (>=3.10).

• Package requires sqlalchemy>=1.4,<2.2
• Removed the 1.3 compiler (compat/core10.py) and the 1.3 helpers (compat/api13.py)
• Added FutureWarning for SQLAlchemy 1.4, that is planned to drop support in future
• Removed skip test for SQLAlchemy 1.3 and removed patches
• Removed CI workflows
• Updated docs

Checklist

• Link to issue this PR refers to (if applicable): Fixes CI: Test against real CrateDB versions, and drop SQLAlchemy 1.3/1.4 #303

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: 290ea1a5-58fa-45c5-abc1-d05f9476c792

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.