Skip to content

chore: release 0.8.0#25

Merged
benvinegar merged 1 commit into
fix/scoped-mutation-payload-typesfrom
release/0.8.0
Jun 28, 2026
Merged

chore: release 0.8.0#25
benvinegar merged 1 commit into
fix/scoped-mutation-payload-typesfrom
release/0.8.0

Conversation

@benvinegar

@benvinegar benvinegar commented Jun 27, 2026

Copy link
Copy Markdown
Member

Summary

Cuts the 0.8.0 release of @modemdev/drizzle-scoped-db. Stacked on #26 (the type-precision fixes) — review/merge that first; this PR is just the release bookkeeping.

The honest scoped-mutation facade (.$unsafeUnscoped(), hidden conflict/upsert methods on scoped inserts, dialect-native .returning()/.$returningId() forwarding) is currently unreleased in [Unreleased] on main — npm's latest is 0.7.0, which predates it. This release ships that facade plus #26's two type fixes.

Changes (2 files)

  • package.json0.7.00.8.0.
  • CHANGELOG.md — move the [Unreleased] block into an immutable [0.8.0] section.

No code changes here; the facade and the type fixes land via their own commits.

Note on the diff

While stacked, this PR's base is fix/scoped-mutation-payload-types, so it shows only the release bookkeeping. Once #26 merges to main, I'll retarget this to main (the diff stays the same 2 files).

Downstream

Unblocks modem #4879, which adopts .$unsafeUnscoped().onConflictDoUpdate(...).returning() and sql fragments in scoped .set(...). After this publishes as 0.8.0, modem bumps off 0.6.0.

🤖 Generated with Claude Code

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>
@benvinegar benvinegar changed the base branch from main to fix/scoped-mutation-payload-types June 28, 2026 01:21
@benvinegar benvinegar merged commit 25331dd into fix/scoped-mutation-payload-types Jun 28, 2026
4 checks passed
@benvinegar benvinegar mentioned this pull request Jun 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant