Repository navigation
chore: version packages - #123
Merged
Merged
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
github-actions
Bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
October 25, 2026 23:30
6e498e7 to
93e9677
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
October 25, 2026 23:33
93e9677 to
db5c0a7
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@maple-dev/effect-orm@0.8.0
Minor Changes
Db.afterCommit(effect)queues work, such as an SMS or an HTTP call, to run after the outermost transaction commits, and never after a rollback. It delegates to Effect'sSqlClient.afterCommitand, likerequireTransaction, addsTransactionto the requirements, so queueing outside a transaction does not compile. A failing hook does not fail the committed transaction: its cause goes to theErrorReporters in context and to an error log, and the next hook still runs.effect ^4.0.6peer). Effect now fails a transaction whose COMMIT failedwith a
SqlErrorinstead of dying;transactionstill reports it asTransactionCommitFailed.ClickhouseHttpClientnames its driver"clickhouse-http"(SqlClient.driver), and Effect's ownstatement span is now named after the database (
db.namespace) rather thansql.execute./sqlitequery entry with SQLite codecs, functions and positional bindings. UsesqliteDialectwith an Effect SQLite SqlClient, ord1Dialectfor Cloudflare D1's binding limitand explicit refusal of interactive transactions.
timestampstores SQLite's ownYYYY-MM-DD HH:MM:SS.SSSUTC text, so it compares correctly with whatstrftimewrites;LIKEescapes with
\as on every dialect; text with U+0000 and integers past 2^53 are refused ratherthan silently changed.
effect-orm generatesupportsdialect: "sqlite". It diffsSQLite.tabledefinitions againstthe migrations folder and writes
<timestamp>_<name>/migration.sqlplussnapshot.json, thedrizzle-kit 1.0 layout that Alchemy's D1 resource applies.
ALTER TABLEadds, drops and renameswhere SQLite allows it; other column, primary key and UNIQUE changes rebuild the table. Renames
need a
confirm_renamehint.generate --baseline --from-drizzleadopts a drizzle-kit 1.0SQLite folder. Snapshots gain a
sqlitedialect./migraterefuses SQLite folders for now.SQLite.table(name, { columns, primaryKey, indexes })declares a SQLite table with its DDL:NOT NULLfrom the column type, single and composite primary keys, literal and expressiondefaults (
SQLite.timestampNowfor atimestampcolumn), unique columns, and named indexes andunique indexes.
sqliteEntitiesOfandrenderSqliteSchemafrom/schemacheck a schema and write itsCREATE TABLEandCREATE INDEXstatements.table(name, columns, options?)andtable(name, { external: true, columns })stay query-only.Patch Changes
unionAllordered by a numeric column whose branches may differ in type (Id + 1and
Id - 1, or aUInt32and anInt64column) no longer fails with "Data types Variant/Dynamicare not allowed in ORDER BY keys". The union's ORDER BY sorts such a column by
CAST(x AS Nullable(Float64)), accurateCastOrNull(x, 'Int128'), which keeps integers past 2^53 in exact order; thevalues themselves are not converted.