Repository navigation
v1.11.5
This release fixes SQL compilation and connection-handling issues, improves inline-literal safety, and strengthens development and test workflows. Versions 1.11.1–1.11.4 were not published; upgrade directly from v1.11.0 and review the notes below.
Upgrade notes
-
Unpublished release candidates (1.11.1–1.11.4; #838, #910, #1005, #1011) — None has a tag, GitHub Release, or PyPI version. Their gates failed on Python 3.15, CUBRIDdb integration (#1003), cookbook verification, and
make integration(#1035), respectively. All their changes are included here; upgrade directly from v1.11.0 to v1.11.5. -
Development test and lint commands changed (#1009) —
make testnow runs all offline tests (previouslymake test-offline); the former fast suite ismake test-fast.make lintchecks Ruff lint only; usemake format-checkormake checkfor formatting.make checkalso runs type checking, security, and documentation checks. The oldmake test-offlineandmake check-allaliases still work (#1010) by @yeongseon. -
Local Docker cleanup and broker access changed (#1008) —
make docker-downnow preserves test data; usemake docker-cleanto remove volumes (the olddocker-downbehavior). The broker binds to127.0.0.1instead of all host interfaces.CUBRID_TEST_PORT(default 33000) controls the host port fordocker-up, Compose, and integration; Compose may use.envwhen not explicitly set.make integrationstill cleans up its own test project (#1017) by @yeongseon. -
MERGE assignment keys from other tables now raise
CompileError(#847) — A bound key inwhen_matched_then_update()orwhen_not_matched_then_insert()must be a column of the target (or its alias); a source-table column with the same name, previously resolved as the target column, now raisesCompileErrornaming that table. Use the target's column (target.c.name) or string key"name". String keys, unboundsa.column()keys and the column-list shorthandwhen_not_matched_then_insert([source.c.id, ...])are unchanged, as are valid SQL and bind order (#895) by @yeongseon. -
Other changes that can need action — Alembic
alter_column()nullability and comment changes now requireexisting_type(#861). Passingdisplay_widthorvaluesto the types listed under Deprecated emits aDeprecationWarning(#870). Unlesscreate_engine(no_backslash_escapes=...)is passed, the first connection probes the server's backslash mode and fails on an unexpected result (#863). Reflected string and date server defaults now come back as quoted SQL literals (#865).CUBRID_PORTis deprecated in favor ofCUBRID_TEST_PORT(#1008).
Added
-
Offline tests now save results (#1019) —
make testwritesjunit.xml,coverage.xmlandsummary.json(PASS/FAIL/INCOMPLETE) to the gitignoredtest-results/test/, whichmake cleanremoves. Failed suites still exit nonzero; test selection and the 95% coverage threshold are unchanged (#1022) by @yeongseon. -
Integration tests now save diagnostics (#1020) —
make integrationwrites JUnit results, a summary, redacted environment details and, on failure,service.logundertest-results/integration/(orINTEGRATION_RESULTS). Missing or all-skipped results reportINCOMPLETEand exit nonzero; cleanup failures and rejected runs reportFAIL, not a stale success. Credentials are masked in recorded commands and logs (#1032) by @yeongseon.
Changed
- Development commands are clearer and interrupted integration runs clean up predictably (#1009) — an interrupt during
docker compose up -dinmake integrationwaits oneINTEGRATION_STOP_GRACEinterval, then sends SIGTERM and allows a second interval before SIGKILL; other interrupted steps get SIGTERM, then SIGKILL after the grace period. Ordinary stalled Compose calls do not have a timeout. Newtest-fast,format-checkand offline-onlyverifytargets are added;make doctorchecks Python 3.11+, missing tools and the Ruff/Mypy pins, andmake formatverifies tool versions. Tool commands remain overrideable through Make variables (#1010) by @yeongseon.
Deprecated
-
make check-all(#1009) — now an alias ofmake checkthat prints a deprecation notice on stderr; it will be removed after the next minor release.make test-offlineremains an alias ofmake test(#1010) by @yeongseon. -
CUBRID_PORT(#1008) — useCUBRID_TEST_PORT, which wins when both are set. When it is unset,CUBRID_PORTis still honoured bydocker-compose.yml,make docker-upandmake integration(the last two print a deprecation warning); other targets ignore it, so a value exported for another CUBRID tool causes no warning (#1017) by @yeongseon. -
Unused
display_widthandvaluestype arguments (#870) —display_width(SMALLINT,BIGINT) andvalues(CHAR,VARCHAR,NCHAR,NVARCHAR,STRING) never changed the DDL or any behavior; passing them now emits aDeprecationWarning. They are still accepted and ignored, and will be removed in a future major release. The unused privateCubridTypeCompiler._gethelper is removed (#891) by @yeongseon.
Fixed
-
aggregate_order_by() on a filtered GROUP_CONCAT names FILTER in its error (#995) — on SQLAlchemy 2.1,
aggregate_order_by(func.group_concat(col).filter(cond), col)still raisesCompileError, but now says CUBRID has noFILTER (WHERE ...)clause instead of claiming the call is not aGROUP_CONCAT. Every other form renders as before (#996) by @yeongseon. -
aggregate_order_by() no longer drops its ORDER BY (#991) — on SQLAlchemy 2.1,
func.group_concat(col).aggregate_order_by(col.desc())silently renderedGROUP_CONCAT(col), returning values in an unspecified order; it now rendersGROUP_CONCAT(col ORDER BY col DESC), also withDISTINCTand inHAVING, with boolean items grouped (#970). Any other function, includingaggregate_strings(), raisesCompileError, as no other CUBRID aggregate takesORDER BY(verified forJSON_ARRAYAGG,COUNT,MAX,SUMandMEDIAN).within_group()and SQLAlchemy 2.0 are unchanged. Verified on CUBRID 11.4; not verified on 10.2, 11.0 or 11.2 (#994) by @yeongseon. -
GROUP_CONCAT DISTINCT, ORDER BY and SEPARATOR no longer fail (#990, #984) — an extra pair of argument parentheses made CUBRID reject the modifiers (-493).
func.group_concat(col.distinct())andliteral_column("col ORDER BY col DESC SEPARATOR ';'")now run, andGROUP_CONCAT((x))renders asGROUP_CONCAT(x). Boolean arguments are grouped once (#970); values are unchanged. Still unsupported (seeFEATURE_SUPPORT): a separateSEPARATORargument, more than one argument, and SQLAlchemy 2.1'saggregate_strings()(aggregate_order_by()is fixed by #991). Verified on CUBRID 11.4; not verified on 10.2, 11.0 or 11.2 (#989) by @yeongseon. -
EXISTS and AND/OR as a simple CASE value no longer fail (#987) — a bare
AND/OR/NOT/EXISTSvalue=operand ofcase(), such asvalue=and_(...)orvalue=exists(), is now parenthesized as CUBRID requires, likeTHEN/ELSEvalues (#982); columns, bind parameters, comparisons and every other rendering are unchanged. The documentation adds three CUBRID limits: a boolean-resultCASEwithout a non-NULLELSE(such as a singleWHEN) can fail with -495 with or without grouping, so passelse_=; CUBRID 11.4 evaluates aCASEwindowORDER BYorPARTITION BYitem as a constant, without an error; and a boolean-valuedCASEfails as aGROUP BYitem (-493). Verified on CUBRID 11.4; not verified on 10.2, 11.0 or 11.2 (#988) by @yeongseon. -
EXISTS and AND/OR as a CASE THEN or ELSE value no longer fail (#982) — a bare
AND/OR/NOT/EXISTSTHENorELSEvalue of a searched or simplecase(), such asand_(...)orexists(), is now parenthesized as CUBRID requires.WHENconditions and other renderings are unchanged. Verified on CUBRID 11.4; not verified on 10.2, 11.0 or 11.2 (#985) by @yeongseon. -
Boolean expressions now compile in CAST, function, and some window arguments (#970) — a bare
EXISTS,NOT,ANDorORused as a CAST or function argument (in SELECT, filters, joins or updates), andEXISTSorNOTin window andWITHIN GROUPordering or partitioning, are now parenthesized as CUBRID requires. SQLAlchemy splits a windowand_()oror_()into separate items, which can change the meaning; keep it with a list such asover(order_by=[and_(...)])or.self_group().WHERE/HAVING/ONare unchanged, and CUBRID still rejects BooleanGROUP BYitems, even function-wrapped;docs/FEATURE_SUPPORT.mdreplaces the earlier guidance (#971). Verified on CUBRID 11.4; not verified on 10.2, 11.0 or 11.2 (#972) by @paikend. -
EXISTS and AND/OR inside a CAST, a function or ORDER BY no longer fail (#968) — a bare
AND/OR/NOT/EXISTSexpression used as an ORDER BY item, or inside a CAST or function that is a SELECT column or ORDER BY item (also throughtype_coerce(), labels and sort modifiers), is now parenthesized instead of failing with -493; for exampleselect(cast(and_(...), Integer)),select(func.coalesce(exists(), False)), a BooleanTypeDecoratorwithcolumn_expression(), andorder_by(exists()).WHERE,HAVING,ON,GROUP BY,CASEconditions and windowORDER BYare unchanged. CUBRID rejects a booleanGROUP BYitem even in parentheses; group by a SELECT-list label instead (seedocs/FEATURE_SUPPORT.md) (#969) by @yeongseon. -
Boolean expressions in SELECT lists now compile (#966) — CUBRID rejects unparenthesized
EXISTS,NOT,AND, andORexpressions in SELECT results. The dialect now groups these expressions, including labeled columns, subqueries, and CTEs;select(exists().where(...))andsession.query(q.exists()).scalar()work. Their use inWHERE,HAVING, join conditions, andCASEconditions remains unchanged (#967) by @paikend. -
Repeated isolation re-apply failures no longer lose the retry marker (#937) — after a successful commit or rollback,
do_begin()retries a failed isolation-level re-apply. If that retry also failed, the pending marker was cleared too early, so a later direct dialectdo_begin()could start work without restoring the level. The marker now stays pending until a re-apply succeeds or a new level is set. SQLAlchemy's normalConnectionrollback had masked this gap in the observed reproduction. The preceding commit/rollback still succeeds and no work is replayed. Applies tocubrid+pycubrid://andcubrid+aiopycubrid://(#947) by @yeongseon. -
Server errors no longer cause false disconnects (#916) — With pycubrid 1.13's
error_source == "server", sync and async connections no longer treat unrelated server error codes (-1000 to -1200) or misleading error text as CAS connection failures. Actual CAS errors, unknown origins, and pycubrid versions before 1.13 retain previous behavior; the supported pycubrid range is unchanged (#938) by @yeongseon. -
boolJSON path indices are rejected (#914) — becauseboolis anintsubclass,json_col[True]orjson_col[("items", False)]rendered paths such as$[True], which CUBRID 10.2 and 11.4 reject (-494) only after the statement is sent.JSONIndexTypeandJSONPathTypenow raiseTypeErrorbefore any SQL is sent (sqlalchemy.exc.StatementErroron execution,sqlalchemy.exc.CompileErrorwithliteral_binds). Integer (including0,1and negative) and string components render byte for byte as before on SQLAlchemy 2.0 and 2.1 (#917) by @yeongseon.
- scripts: dispose reflection probe engine on every exit path (#977) (1303262) by @CloudCorpRecords
-
INSERT/REPLACE ... FROM SELECTover a CTE renders theWITHclause after the column list (#897) —insert(t).from_select([...], select(cte))and the dialect'sreplace()equivalent always failed, because CUBRID 10.2 and 11.4 reject a leadingWITH c AS (...) INSERT ...(-493). They now renderINSERT INTO t (...) WITH c AS (...) SELECT ...; recursive CTEs and bind order are unchanged, and live INSERT, recursive INSERT and REPLACE cases pass on CUBRID 10.2 and 11.4 (#899) by @yeongseon. -
Unique-constraint reflection fails closed on a catalog mismatch (#848) —
get_unique_constraints()silently omitted a unique index thatdb_indexlists butSHOW INDEXESdoes not, which Alembic autogenerate would read as a constraint to create. Such a mismatch now raisesInvalidRequestErrornaming the unresolved and resolved indexes; a verified-empty catalog still returns[]. No such mismatch has been seen on a live CUBRID server; this hardens the reflection invariant (#896) by @yeongseon. -
Garbage-collected async connections are terminated (#872) — on SQLAlchemy 2.0.44+, when a checked-out
cubrid+aiopycubrid://connection is garbage-collected, its socket is now closed and its pycubrid session retired, even after the connection's event loop has closed, instead of the pool logging "cannot be safely terminated" and the stream raising aResourceWarning. An invalidated connection closes withCLOSE_DATABASE. Earlier SQLAlchemy 2.0 releases keep the old behavior (#894) by @yeongseon. -
on_duplicate_key_update()is cacheable (#871) —INSERT ... ON DUPLICATE KEY UPDATEno longer emits SQLAlchemy's "will not make use of SQL compilation caching"SAWarningor recompiles on every execution; a cached statement binds each execution's own values, on SQLAlchemy 2.0 and 2.1 (#893) by @yeongseon. -
Reflection of names containing
:name, collection type classes and join linting (#870) — reflecting a table named likex :yorw (:z)no longer fails with "A value is required for bind parameter 'y'" (the SQL sent is unchanged);SET(Integer)with a type class no longer failscreate_all; and SQLAlchemy's join linter no longer reports a joined select as a cartesian product or misses a real one (#891) by @yeongseon. -
Expression, descending, filtered and prefix indexes reflect and autogenerate (#869) —
LOWER(a),b DESC,WHERE c > 3and the prefixa(5)now reflect asexpressions,column_sortingand the newcubrid_where/cubrid_lengthindex options; before, an expression index was dropped with "Skipping index" and re-proposed by autogenerate on every run, and the others reflected as plain columns.CREATE INDEXnow renders the two new options, previously ignored silently, and Alembic compares them after normalization, so an unchanged index is not proposed again; detecting a changed sort order, filter or prefix length needs Alembic 1.12+ (#885) by @yeongseon. -
Alembic renders CUBRID collection member types with the dialect prefix (#868) — autogenerate wrote members such as
cubrid_types.MULTISET(sa.MONETARY()), which raisedAttributeErrorwhen the migration file was loaded. Members fromsqlalchemy_cubrid.typesnow render ascubrid_types.MONETARY()and so on; generic SQLAlchemy members keepsa.(#884) by @yeongseon. -
Select.fetch()renders asLIMIT(#867) —select(...).fetch(2)and.offset(1).fetch(2)emittedOFFSET ... ROWS FETCH FIRST n ROWS ONLY, which CUBRID rejects (-493); they now render asLIMIT 2andLIMIT 1, 2.percent=Trueandwith_ties=TrueraiseCompileError, since CUBRID has noLIMITform for them (#880) by @yeongseon. -
JSON path keys use JSON string escaping (#866) — a key containing
"failed with -1200 "Invalid JSON path", and one containing\silently returnedNone. Keys are now built withjson.dumps(), so"and\are backslash-escaped and non-ASCII characters become\uXXXXescapes that do not depend on the connection charset (#879) by @yeongseon. -
String and date server defaults reflect as quoted SQL literals (#865) —
get_columns()dropped string defaults' quotes ('it''s'reflected asit''s;'', the string'NULL', dates and'CURRENT_USER'were also misreported), breaking reflectedCreateTableSQL and Alembic'sexisting_server_default. Non-numeric defaults are now read fromSHOW CREATE TABLE(one extra query per table that has one) and reflect as'it''s','','NULL',date '01/02/2020'or the function itself; a string column's'5'stays quoted, and numeric defaults of numeric columns are unchanged (#878) by @yeongseon. -
Alembic
alter_columnemits CUBRID-compatible SQL for nullability, dropped defaults and comments (#861) —nullable=andserver_default=Noneproduced syntax errors andcomment=could not be rendered, so autogenerated nullability changes failed atupgrade. Nullability and comment changes now useMODIFY/CHANGEand requireexisting_type(otherwiseValueError); a dropped default emitsALTER COLUMN c SET DEFAULT NULL, or twoMODIFYstatements for aNOT NULLcolumn. Because CUBRID 10.2/11.0 reset attributes thatMODIFYomits while 11.2+ keep them,NULL,DEFAULT NULLandCOMMENT ''are stated explicitly where needed, and an existing column without a default no longer getsDEFAULT NULL. In offline--sqlmode, a UNIQUEcreate_indexraises the documented "live connection"CompileErrorinstead ofNoInspectionAvailable(#877) by @yeongseon. -
literal_bindsand other compile options reach CAST operands, ON DUPLICATE KEY UPDATE values and collection members (#862) — these positions dropped the compile options, soliteral_bindsand Alembic--sqloutput kept?placeholders, a functionalIndexover aCASTrendered a?, andserver_default=cast(literal(5), String(10))failedcreate_allwith "wrong number of parameters". CUBRID itself still rejectsCASTin a function-based index on 10.2 and 11.4 (#875) by @yeongseon. -
has_table(),get_table_names()andget_view_names()see only the current owner's classes on CUBRID 11.2 and later (#864) — they also matched other owners' classes, although an unqualified name resolves only in the current user's schema: another user'sown_tmadecreate_all()skipdba.own_t(so the nextINSERTfailed),MetaData.reflect()abort withNoSuchTableError, and same-named tables appear twice. They now filter onowner_name = CURRENT_USER. CUBRID 10.2 and 11.0 are unchanged (#876) by @yeongseon.
Security
- Inline literals follow the server's backslash mode (#863) — on a server with
no_backslash_escapes=no,literal_bindsrendered the value\' OR 1=1 --as'\'' OR 1=1 -- ', producing SQL that matched every row, because the dialect assumedno_backslash_escapes=yes. Unlesscreate_engine(no_backslash_escapes=...)pins the mode (and skips the probe), the first connection now probes the server withSELECT CHAR_LENGTH('\\'), and literal rendering doubles backslashes when the server treats them as escapes; an unexpected probe result fails the connection. NativeENUMlabels use the same escaping. A dialect that has not connected still assumes the server default (#874) by @yeongseon.
Documentation
- The architecture pages show the end-to-end driver communication flow (#1013) —
docs/ARCHITECTURE.md(English and Korean) adds a Mermaid diagram tracing the three URL variants through their drivers to the Broker, CAS and database server, and the site now renders Mermaid diagrams instead of showing code. Documentation only (#1016) by @yeongseon.
-
agents: require repository-local issue authoring checks (#1012) (7a15ad7) by @yeongseon.
-
contributing: fix single-test pytest node example (c04a380), refs #881 (#1029) by @HarshRajSinghania
-
triage: clarify PR overlap and execution precedence (1d082cc), refs #1023 by @yeongseon.
-
Two CUBRIDdb result differences are documented (#1003) — because CUBRIDdb binds values on the server, a
CASEwhoseTHEN/ELSEvalues are all bound parameters returns a string ('10', not10), and bound parameters in aGROUP_CONCATargument andaggregate_order_by()item fail with -494. The Driver Compatibility guide gives workarounds (cast(..., Integer);aggregate_order_by(literal_column("1"))). The dialect is unchanged (#1004) by @yeongseon. -
Boolean expressions that still failed on CUBRID (#968) — the
docs/FEATURE_SUPPORT.mdnote and itscase()workaround are replaced, since the #970 fix makes those forms run. Do not use that workaround inside a window: CUBRID 11.4 evaluates aCASE(orif()) in a windowORDER BYorPARTITION BYas a constant (#971) by @yeongseon. -
The first-connection course has one page per lesson (#943) — Lessons 3 (save and read back a row), 4 (roll back a transaction) and 5 (cleanup and
docker rm -f -v) move from the Quick Start to their own English and Korean pages, and its old anchors point to them. Every command was rerun againstcubrid/cubrid:11.4with the published SQLAlchemy 2.1.4, sqlalchemy-cubrid 1.11.0 and pycubrid 1.13.0 (#956) by @yeongseon. -
The first-connection course starts with two lesson pages (#943) — preparing CUBRID and Python (
docs/LESSON_PREPARE.md) and running the first query (docs/LESSON_FIRST_QUERY.md) are separate English and Korean pages, and the site shows previous/next links. Every command was rerun as written againstcubrid/cubrid:11.4with the published SQLAlchemy 2.1.4, sqlalchemy-cubrid 1.11.0 and pycubrid 1.13.0 (#955) by @yeongseon. -
The documentation site is organized by reader question (#943) — the English and Korean navigation is now Start here, How-to guides, Reference, Help, and Project and internals. No page moved and no URL changed. Two accidental headings in the Connection guide and Feature Support are plain paragraphs again (#954) by @yeongseon.
-
Development documentation now identifies unreleased content (#946) — the documentation site says it is built from
mainand may describe candidate or abandoned changes, and records its exact source commit.RELEASING.mddistinguishes candidates, partial publication, abandoned versions and verified published packages, explains bot-PR CI states such asaction_required(observed on #910), and lists the evidence to record; a__version__value onmainis not proof of publication (#951) by @yeongseon. -
The quickstart removes the lab's Docker volume too (#948) — the English and Korean Quick Start now remove the lab with
docker rm -f -v sqlalchemy-cubrid-quickstart, deleting the anonymous volume with the tutorial'stestdbthatdocker rm -fleft behind (#949) by @yeongseon. -
The README async examples are complete programs (#941) — the
Asyncexamples used module-levelawait, aSyntaxErrorin a script; they now run throughasyncio.run(main()), always dispose their engine, and the insert example creates and drops its ownsqlalchemy_async_example_notestable. Both were run against CUBRID 11.4. The Korean README carries both programs and the German, Hindi, Russian and Chinese READMEs the corrected query example; an offline test in the always-running lint job checks them (#944) by @yeongseon. -
A first SQLAlchemy connection for CUBRID beginners (#940) — the Quick Start (English and Korean) is one recommended path from installing
sqlalchemy-cubrid[pycubrid]to a first query, a committed row, a rollback, cleanup and the real first-connection errors, run as written against CUBRID 11.4; the README and documentation home link to it. The CUBRIDdb C-extension driver built from source stays supported; only the[cubrid]and[cubriddb]extras are deprecated (#942) by @yeongseon. -
CAS error -4 is described as an interrupted statement (#873) — pycubrid 1.13.0 reports -4 (
ER_INTERRUPTED, aKILL QUERY) asInterruptedwith SQLSTATEHY008(earlier releases:08S01), and the guides now say so. The dialect still treats -4 as a non-disconnect, as since 1.9.0 (#572); the Driver Compatibility guide also explains why -671 (ER_CSS_RECV_OR_SEND) is not a disconnect code (#939) by @yeongseon. -
A maintainer's review is the standalone-agent alternative to Copilot (#926) —
AGENTS.mdand the contributor guides say a standalone agent PR waits for a substantive GitHub Copilot review or a maintainer's review recorded on the PR (maintainer decision, 2026-10-15); a reviewer agent run by the implementer does not count (#927) by @yeongseon. -
Agent guidance split into task guides (#907) — the root
AGENTS.mdkeeps every rule and gains a task routing table, while detailed context moved unchanged todocs/agents/;scripts/check_agents_docs.pychecks its links, commands and version pins, and with--retained-from REFthat no earlier line was dropped. No code, CI or release behavior changes (#918) by @yeongseon. -
Python 3.15 limitation of garbage-collected connection cleanup (#872) — with SQLAlchemy 2.1 (2.1.0 to 2.1.4 checked) on CPython 3.15, a pooled connection reclaimed by the cycle collector is never terminated: its socket closes only through Python's stream finalizer with a
ResourceWarning, and its pool slot stays checked out (python/cpython#136189). Every dialect is affected, sync pools included; SQLAlchemy 2.0 and Python 3.14 and earlier are not. The Connection Guide and Support Matrix describe it (#909) by @yeongseon.
-
contributing: clarify good-first-issue access for human contributors (#913) (7a2512f) by @yeongseon.
-
correct the documented boolean expression positions (#986) (7c7958b) by @SuellenQwQ (first contribution 🎉)
-
types: correct the namespace of reflected timezone types (#973) (9480036), refs #882 by @CloudCorpRecords (first contribution 🎉)
-
The README and the documentation site show the CUBRID Lab repository icon (#886) — the README, its translations and the site's logo and favicon use the sqlalchemy-cubrid icon from one immutable cubrid-lab/brand commit (#900) by @yeongseon.
-
ROADMAP.mdno longer presents shipped releases as plans (#833) — the Python 3.10 retirement (1.10.0) and Python 3.15 support (1.11.0) moved to Completed, and version numbers are replaced by links toCHANGELOG.md, PyPI anddocs/SUPPORT_MATRIX.md(#844) by @yeongseon. -
docs/PERFORMANCE.mdhas a current same-CUBRID baseline (#830) — raw pycubrid, SQLAlchemy Core and ORM timings on one CUBRID 11.4 server atmaina570ea4(dialect source as in v1.11.0; pycubrid 1.12.0, SQLAlchemy 2.1.4 and 2.0.54, Python 3.12; 5 trials each) from the newscripts/bench_dialect_baseline.py, with raw data inbenchmarks/2026-10-12-dialect-baseline/. No dialect hotspot or regression was found; runtime behavior is unchanged (#843) by @yeongseon. -
The dialect baseline now covers CUBRID 10.2, 11.0 and 11.2, CUBRIDdb, the async driver and concurrent connections (#830 follow-up) — a 2026-10-13 run through pycubrid, CUBRIDdb (built from cubrid-python v11.3.0.51) and the async driver on 1, 4 and 8 connections (
benchmarks/2026-10-13-dialect-baseline-followup/). Reads differ little; pycubrid and the async driver scale with connections, while CUBRIDdb, whose C extension never releases the GIL, does not scale across threads. Runtime behavior is unchanged (#860) by @yeongseon. -
The feature support table no longer marks CUBRID
BLOB/CLOBas fully supported (#829) — they now show⚠️ : DDL, type mapping, reflection, bindingbytes/strandNULLround trips work, but an ordinary Core/ORM read of a non-NULL value returns the driver's LOB locator oncubrid://,cubrid+pycubrid://andcubrid+aiopycubrid://(Known Issue 6 indocs/DRIVER_COMPAT.md). Documentation only (#842) by @yeongseon.
-
agents: correct stale entry points, integration commands and doc map in AGENTS.md (#846) (340a587) by @yeongseon.
-
i18n: update the Python requirement in the German README (#837) (fcdb443), refs #698 by @yeongseon.
-
i18n: update the Python requirement in the Hindi README (#839) (3f79d2d), refs #699 by @yeongseon.
-
i18n: update the Python requirement in the Russian README (#840) (793b6ef), refs #700 by @yeongseon.
CI
- release: restart release preparation after the abandoned 1.11.4 (#1037) (3184d9b), refs #1011 by @yeongseon.
-
CI publishes the offline test summary and uploads results on success and failure (#1021) — offline jobs write JUnit, coverage and
summary.json, add the summary to the job summary and uploadtest-results/, and integration jobs upload their pytest logs, all withif: always(); the live-lane summary follows #1020. Test selection, the 95% coverage floor and permissions are unchanged (#1027) by @yeongseon. -
The
make-integrationjobs also uploadtest-results/integration/(#1020) — the live results ofmake integrationjoinmake-integration.login the existingpytest-logs-make-integration-*artifact; nothing else in the workflows changes (#1032) by @yeongseon. -
A change to
docker-compose.ymlruns the test that pins it (#997) — thetoolingpath filter now listsdocker-compose.yml, so a pull request changing only that file runstest/test_make_integration.py(#999) by @yeongseon.
-
release: verify against the current cookbook and restart after the abandoned 1.11.3 (#1007) (72bf7be) by @yeongseon.
-
release: start release preparation after the abandoned 1.11.2 (#1006) (b1a2dfe) by @yeongseon.
-
The CUBRID 11.4 local Docker test database is kept in a named volume (#1000) — with
CUBRID_VERSION=11.4, whose image keeps databases in/home/cubrid/CUBRID/databases,docker compose downlost the data. A second named volume,cubrid-databases, now holds that path,make docker-downdeletes both, andmake integrationrefuses a pre-existing<project>_cubrid-databases. Checked on CUBRID 10.2, 11.2 and 11.4; opening a database created by another CUBRID version is not verified, so reset before switchingCUBRID_VERSION. Same fix as cubrid-lab/pycubrid#1004 (#1001) by @yeongseon. -
The local Docker test database keeps working after its container is recreated (#997) — the database was registered under the old container ID, so every connection failed with -353 after recreation.
docker-compose.ymlnow setsCUBRID_DB_HOST: localhost(for 11.4 see #1000 above); for an older volume,make docker-fix-db-hostrewrites onlytestdb's host and keeps the data and adatabases.txt.before-fix-db-hostbackup, ormake docker-down(docker compose down -v) deletes it.make integration, CI and the dialect were not affected. Same fix as cubrid-lab/pycubrid#1001 (#998) by @yeongseon. -
Repository-tooling tests run when only their inputs change (#964) — the
toolingpath filter now listsagent-evals/**, ten repository-tooling test modules andtest/conftest.py, andtest_workflow_path_impact.pychecks that everyREPO_TOOLING_MODULESentry selects the tooling lane (#965) by @yeongseon. -
Manual agent runs are recorded and summarized as distributions (#906) —
scripts/agent_eval.pygainsprompt,recordandsummarize, which record manual runs and summarize them per task and model with a 95% Wilson interval, never a bare pass percentage. Runs are manual-only, from an isolated clone without publish credentials; nothing runs an agent in CI, and no score gates a pull request (#963) by @yeongseon. -
Agent evaluation tasks for reflection and Alembic (#906) —
agent-evals/adds tasks from the #865 and #861 fixes. Neither has recorded live evidence; the Alembic task passes only a candidate that reports the live migration check as not run and says live behavior is not verified. No dialect source or CI lane changes (#962) by @yeongseon. -
Offline agent evaluation tasks and grader (#906) —
agent-evals/andscripts/agent_eval.pygrade a coding agent's patch for a frozen historical fix (the first task is the #914 fix) against hidden tests, allowed files, documentation, the CHANGELOG and its claims; a live CUBRID claim without a recorded live run, compiled or bound SQL reported as live evidence, or calling the supported CUBRIDdb driver deprecated fails.make agent-eval-checkre-grades recorded fixtures without a model or database, in therepolane; no agent score gates a pull request (#961) by @yeongseon. -
The documentation check's shell scanner matches pycubrid again (#959) —
scripts/_markdown.pytakes pycubrid's final_substitution_end()byte for byte (cubrid-lab/pycubrid#978), fixingcase/esac,;&/;;&and comment handling inside substitutions. No other checker rule changes (#960) by @yeongseon. -
The documentation check allocates site anchors as the site does (#957) — the shared
scripts/_markdown.pyuses the slugifier configured inmkdocs.ymland thetocextension's id-collision rules; ordinary headings keep their anchors. The change matches cubrid-lab/cubrid-cookbook-python#402 and cubrid-lab/pycubrid#976 (#958) by @yeongseon. -
The site build runs when the MkDocs provenance hook changes (#952) —
scripts/docs_provenance_hook.py, loaded bymkdocs.ymlsince #951, is now asitepath-filter input, so a pull request changing only the hook runsmkdocs build --strict(#953) by @yeongseon. -
Prepare release checks the
last-release-shabaseline override (#945) — preparation stops, asking for removal in a normal PR, when the override set after abandoning 1.11.1 is obsolete (a later release containing it passed the publication proof), malformed, unrelated or unreadable, so a stale override cannot make a recovery silently relist shipped commits. An API error is reported as unresolved, nothing is edited automatically, andRELEASING.mddocuments the rule; the current 1.11.1 override is active (#950) by @yeongseon. -
The documentation check handles shell substitutions as pycubrid does (#934) —
scripts/_markdown.pytakes pycubrid's substitution fixes (cubrid-lab/pycubrid#947):$(...),<(...)and>(...)belong to their word and their bodies are checked as commands, a#after a substitution is not a comment, and an unclosed quote is prose. Review added fixes forcasepatterns, quoted substitutions, arithmetic expansion and newlines, which pycubrid receives next (#935) by @yeongseon. -
agent-reviewno longer counts empty reply-only Copilot records as review rounds (#933) — such records could push a PR past the two-round budget and reject valid evidence; a record that opens a thread still counts. Ported unchanged from cubrid-lab/cubrid-mcp-server#349 (#936) by @yeongseon. -
Advisory review-evidence check added (#905) —
agent-review.ymlreads GitHub's actual review records with a read-only token and the base-branchscripts/agent_review_gate.py, not PR checkboxes or bot summaries. It accepts a substantive Copilot review within the two-round budget, a maintainerAPPROVEDreview, or a maintainerCOMMENTEDreview opening an inline thread; changes to literal rendering, identifiers, dialect connections/disconnects, Alembic, workflows, release configuration or gate scripts require maintainer approval. Stale reviews, incomplete API data, missing commit identities and unresolved or author-resolved critical/security threads do not pass: only maintainer resolution satisfies a critical/security finding. Release-please-only and Dependabot PRs are exempt. Adapted from cubrid-lab/cubrid-mcp-server#341, it remains advisory: PRs can spoof its check name, so it must not be required until a trusted identity posts it (#929) (#1015) by @yeongseon. -
Issue-number lines in block quotes inside list items are reported (#925) — the
#<digit>line check now covers quotes such as- > #750, which Python-Markdown renders as headings, and parses container prefixes in linear time (#930) by @yeongseon. -
The documentation check takes link lines from the source and masks inline HTML (#923) — link line numbers now come from each link's own source, and only what markdown-it actually parsed (inline HTML, autolinks, link tails) is masked before references are checked, so undefined references are no longer hidden or misplaced (#928) by @yeongseon.
-
The documentation check reports lines that the site renders as headings (#920) — a
docs/line starting with#and a digit is plain text on GitHub but an<h1>on the MkDocs site;scripts/check_docs_links.pynow reports it and asks for\#, and the 11 existing cases are escaped (#924) by @yeongseon. -
Documentation link checks handle more Markdown, HTML, Makefile and shell cases (#921) — line numbers across multi-line HTML, grouped and double-colon Makefile targets, references hidden by malformed links or comments, shell continuations and redirections, and HTML
<source src>links, matching the reviewed pycubrid parser (cubrid-lab/pycubrid#940, cubrid-lab/pycubrid#941) (#922) by @yeongseon. -
Deterministic documentation defects block the merge (#908) — a new
docs-checkjob, required bymatrix-resultwhen Markdown,scripts/or theMakefilechange, runsscripts/check_docs_links.pyandscripts/check_agents_docs.pyand fails withfile:lineon broken link targets or anchors, undefined references, unclosed code fences and nonexistentmakegoals orscripts/paths. It parses CommonMark with the pinnedmarkdown-it-py, as pycubrid's gate does (cubrid-lab/pycubrid#939), and never fetches external links; the shareddoc-lintworkflow stays advisory.<!-- docs-check: ignore -->marks a reviewed false positive (#919) by @yeongseon. -
Release preparation starts after the abandoned 1.11.1 —
release-please-config.jsonsetslast-release-shato the 1.11.1 merge, so release-please no longer proposes 1.12.0 with every commit since 1.8.0; RELEASING.md documents setting that override and removing it after the next release is tagged (#912) by @yeongseon. -
A release commit's
mainpush no longer repeats the release's runtime lanes (#737) — on a release commit,ci.ymlskips the typecheck, offline, Alembic, packaging and integration lanes thatintegration-full.ymlalready runs behind the fail-closedfull-matrix-result, andintegration-full.ymlgains the two pycubrid endpoint steps it lacked; lint, documentation and tooling checks still run. On the 1.11.0 release commit this would have saved 14.1 runner minutes for about 1.4 added;docs/CI_POLICY.mdrecords runner minutes after the #760 and #797 consolidation (#841) by @yeongseon.
Tests
-
The live test for garbage-collected async connections passes in
make integrationagain (#872) — after #1017 bound the Compose broker to127.0.0.1, hosts resolvinglocalhostto::1first (GitHub runners) kept the test's connection alive in an asyncio reference cycle, failing everymake integrationlane and stopping the 1.11.4 release matrix. The test now reuses a pre-opened pooled connection and still requires the leaked connection to be terminated, with no ResourceWarning (#1035) by @yeongseon. -
The CASE value and GROUP_CONCAT ORDER BY live tests pass with CUBRIDdb (#1003) — the tests added for #987 and #991 asserted pycubrid's results, so the release matrix's
make integration (cubriddb, …)lanes failed on CUBRID 10.2 and 11.4 and 1.11.2 was not published. They now pin the CUBRIDdb results above and keep the exact pycubrid assertions (#1004) by @yeongseon. -
ORDER BY output matches SQLAlchemy's for plain items (#968) — the dialect renders ORDER BY one item at a time, so a guard test compares its output with SQLAlchemy's own
order_by_clausefor ORDER BY items that need no grouping (#969) by @yeongseon. -
SHOW TRACE read failures release both result handles (#854) — a new mocked offline test checks that when reading the
SHOW TRACErows raises,trace_query()closes both results, still attemptsSET TRACE OFFand passes the read error to the caller; it does not replace integration coverage on a real server. No production code changes: the behaviour already held, so no failure could be demonstrated (#931) by @tnalbant (first contribution 🎉). -
Garbage-collection tests no longer depend on the cycle collector (#872) — the live async terminate and closed-event-loop tests now commit before losing the connection, so the pool terminates it when the last reference goes on every supported Python, including 3.15. The reference-cycle case is a separate expected failure where the pool cannot clean it up (SQLAlchemy 2.1 on CPython 3.15). Both had failed on all four Python 3.15 cells of the full compatibility matrix (#894) by @yeongseon.
-
Benchmark artifacts verify the measured dialect and carry their provenance in the report (#903) —
scripts/bench_dialect_baseline.pystops if the installedsqlalchemy_cubriddoes not match--source-sha, and records the package SHA-256, verification method, image digest, host label and comparable group. Contractsqlalchemy-cubrid-benchmark-artifact/2rejects an unverified install such as a PyPI wheel and in-place edits of those fields;/1manifests are rejected but kept unchanged, and the pair is re-recorded inbenchmarks/2026-10-14-artifact-pair-v2. Benchmark tooling only (#904) by @yeongseon. -
Benchmark results can now be archived and compared with provenance (#901) —
scripts/bench_artifact.pyexports and validates asqlalchemy-cubrid-benchmark-artifact/1manifest from a complete dialect benchmark report and compares baseline and candidate runs. It records dialect SHA, driver and SQLAlchemy versions, CUBRID image/server, Python/host, a password-redacted connection target (database user and URL query parameters are still recorded), pool settings, workload identity and every trial. Missing files, corrupt data or mixed source revisions are rejected, and differences other than the dialect make resultsnot comparable. Operator-supplied SHA, image digest and host labels are not independently verified (#903). The pinned v1.11.0-to-main CUBRID 11.4 pair is inbenchmarks/2026-10-14-artifact-pair; the older #830 archives are unchanged. Benchmark tooling only: no dialect change and no new CI gate (#902) by @yeongseon. -
Isolated live CTE coverage (#849) — SQLAlchemy's 14
CTETestcompliance nodes are strict xfails because their fixture cleanup fails on CUBRID's per-row foreign-key check, soTestIsolatedCTE849replays their scenarios on fresh tables against CUBRID 10.2 to 11.4: SELECT, recursive, bound-parameter, UPDATE/DELETE with a CTE subquery and values-via-CTE cases pass, UPDATE/DELETE ... FROM are asserted as documented limits, and INSERT FROM SELECT over a CTE passes since #897 (#898) by @yeongseon. -
Offline tests for identifier quoting, preflight engine disposal and the reflection probe report (#859, #858, #857) —
test/test_base.pycovers escaped and reserved identifier quoting,test/test_check_integration_connection.pypins disposal of the preflight sync engine on success and on errors, andtest/test_reflection_probe_shape.pypins thereflection_probereport shape with a fake inspector (#978, #979, #981) by @CloudCorpRecords. -
Offline tests for select attribute accessors, compile benchmark iterations and version-report fallbacks (#855, #850, #851) —
test/test_compiler.pycovers select attribute accessors,scripts/bench_compile.pyvalidates its iteration count (test/test_bench_compile.py), andtest/test_report_driver_versions.pycovers the version report fallbacks (#1025, #1026, #1031) by @WilliamK112 (first contribution 🎉).
Full Changelog: v1.11.0...v1.11.5