Repository navigation
chore: version packages - #28
Merged
Merged
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
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. Comment |
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.6.0
Minor Changes
fromSqlClient/layerSqlClienttakerequireTenantScope: true, which refuses an undeclared"cross-tenant"statement with aTenantScopeViolationdefect. Compiled queries carrycrossTenantDeclaredwhen the opt-out was explicit, and unions, inserts, updates and deletes gain.crossTenant().rawCompiledQuery'stenantScopeis now optional and defaults to"cross-tenant".PG.enumType(name, labels, { schema? })is a column type (rows decode to its labels; inserts and comparisons take only them;nullableandarraywrap it, and enum arrays decode from the text form drivers send) and a schema object:generatecreates the type before the tables that use it, adds labels withADD VALUE ... BEFORE, renames one behind aconfirm_renamehint, asks before dropping the type, and reports removing or reordering labels, or using a label in the migration that adds it, as unsupported.PG.unique(name, columns, { nullsNotDistinct? })in a table'suniqueConstraints, oruniqueinPG.column(named<table>_<column>_uniqueby default), declares anADD CONSTRAINT ... UNIQUEconstraint, diffed as a constraint rather than an index.verifyreads enums frompg_enumand unique constraints frompg_constraint, and resolves types of the current schema during its scratch rebuild, soPG.custom("public.x", ...)enums no longer report false drift.generate --baseline --from-drizzleconverts drizzle-kit enums, enum columns and unique constraints.Patch Changes
Runnable(from/database) and accepted bycompileunder TypeScript 5.x again. Both tookCHInsert<any, ...>, which TypeScript 5 compares method by method, and the genericonConflictDoUpdatefailed that comparison; they now take an insert by its tag, state and phantom (AnyInsert). A workaround such astype Runnable = Orm.Runnable | { readonly _tag: "CHInsert" }can be removed.Need help on this PR? Tag
@codesmith-botwith what you need.