chore: release 0.8.0#27
Merged
Merged
Conversation
Two type-precision fixes on the honest scoped-mutation facade, both observed as typecheck failures in a downstream consumer: - `.$unsafeUnscoped()` now returns a builder (UnscopedInsertBuilder) whose conflict/upsert chains preserve the table-precise `.returning(...)` row type via ForwardChainMethod, instead of widening to `Record<string, unknown>`. ForwardChainMethod is the return-rewriting sibling of the existing ForwardMethod: it keeps each conflict method's exact per-dialect argument types but retypes the return to ScopedInsertResult so a trailing `.returning()` infers columns from the target table. - Scoped `.values(...)` / `.set(...)` payloads accept Drizzle `sql` template expressions for individual column values, matching Drizzle's own mutation signatures (a raw SQL column value was previously rejected). No runtime change and no version bump — entries land under [Unreleased]; the release that ships them is cut separately. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Cut 0.8.0: bump the version and move the [Unreleased] section (the honest scoped-mutation facade plus the two type-precision fixes) into an immutable [0.8.0] section. No code changes beyond the release bookkeeping; the facade and the type fixes land via their own commits. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
1 participant
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.
Summary
Lands the 0.8.0 version bump + changelog cut onto
main.This is the release half of the stack. The previous release PR (#25) was based on the type-fix branch, so when it merged it landed on that branch instead of
main—mainis still0.7.0with everything in[Unreleased]. This PR puts the bump where it belongs.Changes (2 files)
package.json—0.7.0→0.8.0.CHANGELOG.md— move the[Unreleased]block (the honest scoped-mutation facade + fix: precise types for $unsafeUnscoped chains and sql() payloads #26's two type fixes) into an immutable[0.8.0]section.No code changes — the facade and the type fixes are already on
main(via #26). After this merges,0.8.0gets published to npm to unblock modem#4879.🤖 Generated with Claude Code