chore(deps): bump drizzle-orm from 1.0.0-beta.16-ea816b6 to 1.0.0-rc.2

[dependabot]

Bumps drizzle-orm from 1.0.0-beta.16-ea816b6 to 1.0.0-rc.2.

Release notes

Sourced from drizzle-orm's releases.

v1.0.0-rc.2

Updates

• Disabled default codec type selectors for custom columns (fixes #5711)
• Сallback type overload for codec selector in custom pg columns (codec: (config) => config?.withTimeZone ? 'timestamptz' : 'timestamp')
• Extended list of postgis types for codecs (improvement for #5711)
• Updated codecs: geometry -> geometry(point), geometry:tuple -> geometry(point):tuple
• Switched PG transactions from class properties back to class methods (fixes #5709)
• Updated AWS Data Api codecs, removed query typings, improved input param mapping
• Removed prepared query typings field from all builders
• Added column argument to CastParam,CastArrayParam codecs

Migration updates in SQLite

• Added migration conflict detection for SQLite. When migration history has multiple open branches, drizzle-kit generate now checks whether those branches can be merged safely before creating the next migration. This helps catch cases where two migrations were created from the same parent and then changed the same SQLite object in incompatible ways, for example two branches changing the same table, index, or view.

npx drizzle-kit generate

• If the conflict is expected and you want to continue anyway, pass --ignore-conflicts to skip the conflict check for that command.

npx drizzle-kit generate --ignore-conflicts
npx drizzle-kit check --ignore-conflicts

• Added proper SQLite migration tree merging. New snapshots now collect all open leaf snapshot IDs and write them as parents, instead of keeping only one latest parent. This means a new migration generated after branching can merge all open leaves and use the combined SQLite state for the next snapshot diff.

{
  "prevIds": ["first-open-leaf-id", "second-open-leaf-id"]
}

• Fixed DrizzleQueryError and TransactionRollbackError constructors to properly set the error name for better instanceof checks
• Fixed error handling in aws-data-api to properly show database error messages

v1.0.0-rc.1

⚠️ This release introduced a breaking change into our casing API(see below) and removes RQB v1 ._query for postgres

JIT mappers

Drizzle ORM now has an opt-in API for JIT(just in time compilated) mappers which make most expensive part of the db request pipeline(row mapping) as fast as humanly possible.

const db = drizzle({ ..., jit: true })
const query = db.select().from(users).prepare();
// ^ here drizzle generates a jit mapper which will then be reused during each invocation
server.get('users', (c) => {
const users = await query.execute(); // as fast as using raw driver
</tr></table>

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

---

Summary by cubic

Upgrade drizzle-orm from 1.0.0-beta.16-ea816b6 to 1.0.0-rc.2. Updates deps and overrides in packages/opencode/package.json to pick up RC fixes, SQLite migration conflict checks, and PG transaction API changes.

• Migration
  • If you use the old casing API or Postgres RQB v1 ._query, move to the new casing API and remove ._query calls.
  • For SQLite, run npx drizzle-kit generate; resolve any reported conflicts or pass --ignore-conflicts only if intentional.

^{Written for commit b4113b6. Summary will update on new commits. Review in cubic}

[claude]

Claude Code Review

This repository is configured for manual code reviews. Comment @claude review to trigger a review and subscribe this PR to future pushes, or @claude review once for a one-time review.

_{Tip: disable this comment in your organization's Code Review settings.}

[github-actions]

This PR doesn't fully meet our contributing guidelines and PR template.

What needs to be fixed:

• PR description is missing required template sections. Please use the PR template.

Please edit this PR description to address the above within 2 hours, or it will be automatically closed.

If you believe this was flagged incorrectly, please let a maintainer know.

[github-actions]

Thanks for your contribution!

This PR doesn't have a linked issue. All PRs must reference an existing issue.

Please:

1. Open an issue describing the bug/feature (if one doesn't exist)
2. Add Fixes #<number> or Closes #<number> to this PR description

See CONTRIBUTING.md for details.

[cubic-dev-ai]

1 issue found across 1 file

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="packages/opencode/package.json">

<violation number="1" location="packages/opencode/package.json:51">
P2: Regenerate bun.lock alongside this bump; the committed lockfile still pins the old drizzle-orm version, so the repo’s dependency graph is inconsistent until it’s updated.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
Re-trigger cubic}

[cubic-dev-ai]

P2: Regenerate bun.lock alongside this bump; the committed lockfile still pins the old drizzle-orm version, so the repo’s dependency graph is inconsistent until it’s updated.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At packages/opencode/package.json, line 51:

<comment>Regenerate bun.lock alongside this bump; the committed lockfile still pins the old drizzle-orm version, so the repo’s dependency graph is inconsistent until it’s updated.</comment>

<file context>
@@ -48,7 +48,7 @@
     "@typescript/native-preview": "catalog:",
     "drizzle-kit": "1.0.0-beta.16-ea816b6",
-    "drizzle-orm": "1.0.0-beta.16-ea816b6",
+    "drizzle-orm": "1.0.0-rc.2",
     "duckdb": "1.4.4",
     "playwright-core": "1.58.2",
</file context>

[dev-punia-altimate]

Multi-Persona Review — Verdict: ship

This PR introduces a well-scoped feature to root lineage graphs at source nodes when source YAML files are active, matching dbt Cloud IDE behavior. The implementation is thoroughly tested, aligns with best practices, and has no critical or high-severity findings. A low-severity architecture suggestion was noted but does not block shipping.

14/14 agents completed · 229s · 1 findings (0 critical, 0 high, 0 medium)

Low

• [cto] The PR adds a new code path for source YAML lineage rooting that is tightly coupled to the editor's active text selection. While functional, this introduces a new dependency on cursor position for core graph behavior, which may complicate future state management or multi-editor scenarios. → src/webview_provider/newLineagePanel.ts:94
  • 💡 Consider abstracting the source resolution logic into a standalone service that can be invoked by cursor events but also supports programmatic invocation (e.g., via command palette), to decouple UI interaction from core lineage resolution.

---

_{Multi-Persona Review · vllm:qwen3-next-80b (waves) + vllm-fallback (synth) ·}