chore(main): release 1.11.0

[github-actions]

🤖 I have created a release beep boop

1.11.0 (2026-10-12)

Added

• python: declare Python 3.15 support (#807) (92d79eb)

Fixed

• packaging: cap SQLAlchemy below 2.2 to match the documented support matrix (#777) (715349a), refs #774

Documentation

• agents: add support-claim review checklist (#784) (a8ffc4b)
• agents: replace stale performance planning snapshot with pointers (#757) (f2b838a)
• ci: clarify SQLAlchemy pre-release canary coverage (#788) (85817ca)
• correct the older closing-guard CHANGELOG notes (#819) (a508694)
• driver: clarify CUBRIDdb support and deprecated extras (#781) (d20a6b2)
• drop the stale nightly full-integration wording (#792) (b0e95b2)
• i18n: update the Python requirement in the Chinese README (#825) (6430aad)
• label the compliance-lane pycubrid pin as the declared floor (#801) (ea9392e), refs #479
• name private vulnerability reporting as the preferred security channel (#796) (98b746f)
• python: state the Python 3.11+ requirement in connection, driver and PRD docs (#803) (8a6fb60)
• release: record live release-please evidence and candidate regeneration (#817) (27134e0)
• remove stale test_dml.py and unguarded counts from PRD/DEVELOPMENT (#759) (c59c7db)
• review: distinguish agent review routes and dispositions (#802) (24743d6)
• support: distinguish current guarantees from historical evidence (#783) (92307cf)
• types: identify pycubrid 1.9.0 collection binding (#782) (81fc4ff)

---

This PR was generated with Release Please. See documentation.

[Copilot]

🟢 Approval recommended

Version metadata and release notes are consistent with the repository’s guarded release process.

0 open findings

What changed in this PR

Prepares the guarded 1.10.1 patch release, primarily shipping the SQLAlchemy <2.2 compatibility cap.

Changes:

• Bumps package and release-manifest versions to 1.10.1.
• Finalizes curated and generated release notes.

File	Description
sqlalchemy_cubrid/​__init__.py	Bumps the package version.
.release-please-manifest.json	Advances Release Please state.
CHANGELOG.md	Adds the curated 1.10.1 release section.
RELEASE_CHANGELOG.md	Adds generated Conventional Commit notes.

🧠 Review effort: Balanced

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[yeongseon]

Candidate made merge-ready (not merged; merging publishes and needs the maintainer's approval).

• Regenerated with Prepare release run 38196143622 (success) at main 31853ae, after docs(release): record live release-please evidence and candidate regeneration #817 and ci: check PR titles, commit messages and underscore owners for foreign closures #818. Behind main: 0. The diff is limited to the manifest, CHANGELOG.md, RELEASE_CHANGELOG.md and __version__ (all 1.11.0, section ## [1.11.0] - 2026-10-12).
• autorelease: review was re-applied after regeneration. Commit c3d6452 again removes the generated "closes test: adopt and verify pycubrid DB-API contract changes across SQLAlchemy #479" from the docs: label the compliance-lane pycubrid pin as the declared floor #801 entry, because that commit only says Refs #479. The one remaining generated closes (fix(packaging): align the SQLAlchemy dependency range with the documented support matrix #774 on 715349a) matches its commit's Closes #774.
• make release-check VERSION=1.11.0 passed at c3d6452: version, CHANGELOG lint, release notes, build and twine check.
• A close/reopen started the pull request checks at the final head c3d6452. CI, CodeQL, Security Scans, docs-sync and PR title all succeeded, and the merge state is clean. The earlier push-triggered runs were cancelled by concurrency and superseded.
• The full compatibility matrix, integration-full.yml run 38196242732, passed at main 31853ae (35/35 jobs).
• Any further merge to main makes this candidate stale again: unfreeze, regenerate and repeat the steps above, as described in RELEASING.md step 2.

🤖 Generated with Claude Code

[yeongseon]

Candidate refreshed at the final main c2e2586, after #819 and #820. It is still not merged: merging publishes, and needs the maintainer's approval.

• Regenerated with Prepare release run 38198635325, which succeeded. It is 0 commits behind main, and autorelease: review was re-applied afterwards.
• No hand edit is needed on the branch any more. Since ci(release): write generated issue references as refs, not closes #820, the composer writes generated references as refs, so the docs: label the compliance-lane pycubrid pin as the declared floor #801 entry now reads refs [#479] and the fix(packaging): align the SQLAlchemy dependency range with the documented support matrix #774 entry reads refs [#774]. RELEASE_CHANGELOG.md keeps release-please's raw closes wording, but publication reads only CHANGELOG.md. History from 1.10.0 down is byte for byte the same as on main.
• make release-check VERSION=1.11.0 passed at f84c5a2. The manifest, __version__ and ## [1.11.0] - 2026-10-12 agree.
• A close/reopen started the checks at the final head f84c5a2. CI, CodeQL, Security Scans, docs-sync and PR title all passed, and the merge state is clean. The bot-created runs from before the reopen started no jobs and are recorded as failed; that is the expected symptom.
• The full compatibility matrix, run 38198717872 at c2e2586, passed 35 of 35 jobs.
• Closing issue references on this PR: test: adopt and verify pycubrid DB-API contract changes across SQLAlchemy #479 and fix(packaging): align the SQLAlchemy dependency range with the documented support matrix #774, both already closed. Merging will not close an open issue.

🤖 Generated with Claude Code

[paikend]

Release 1.11.0, regenerated after the earlier conflict: manifest and sqlalchemy_cubrid/__init__.py agree with both changelogs, the branch is mergeable and the checks on this head are green.