Skip to content

fix(webapp): route OrganizationDataStoresRegistry writes through the writer prisma#3722

Merged
matt-aitken merged 1 commit into
mainfrom
fix-org-data-stores-registry-write-path
May 23, 2026
Merged

fix(webapp): route OrganizationDataStoresRegistry writes through the writer prisma#3722
matt-aitken merged 1 commit into
mainfrom
fix-org-data-stores-registry-write-path

Conversation

@matt-aitken
Copy link
Copy Markdown
Member

Bug

The OrganizationDataStoresRegistry singleton in apps/webapp/app/services/dataStores/organizationDataStoresRegistryInstance.server.ts was constructed with $replica. That client was then used by both the polling read path and by addDataStore / updateDataStore / deleteDataStore (and their backing SecretStore.setSecret upserts). The write methods route through the read replica, which Postgres rejects with error code 25006:

Invalid prisma.secretStore.upsert() invocation:
ConnectorError(ConnectorError { user_facing_error: None, kind: QueryError(PostgresError {
  code: "25006",
  message: "cannot execute INSERT in a read-only transaction",
  ...
}), transient: false })

User-visible symptom: the admin /admin/data-stores "Add data store" form returns a 400 with this error wrapped, so no OrganizationDataStore row can ever be created via the UI.

The read path (loadFromDatabase polling + SecretStore.getSecret) is unaffected because findMany + secret read are read-only.

Fix

Change the registry constructor to take both a writer and a replica:

constructor(writer: PrismaClient, replica: PrismaClient | PrismaReplicaClient)
  • loadFromDatabase() keeps using _replica (and its SecretStore.getSecret calls) — these are background cache-fillers, not on user-latency-sensitive paths.
  • addDataStore / updateDataStore / deleteDataStore (and their SecretStore.setSecret / deleteSecret calls) now use _writer.

organizationDataStoresRegistryInstance.server.ts passes (prisma, $replica) from ~/db.server. Test sites that constructed with (prisma) now pass (prisma, prisma) — the testcontainer exposes a single client, so the writer/replica split collapses to one connection.

Files

  • apps/webapp/app/services/dataStores/organizationDataStoresRegistry.server.ts — constructor + read/write split
  • apps/webapp/app/services/dataStores/organizationDataStoresRegistryInstance.server.ts — pass prisma alongside $replica
  • apps/webapp/test/organizationDataStoresRegistry.test.ts — 14 call sites bumped
  • apps/webapp/test/clickhouseFactory.test.ts — 5 call sites bumped

Test plan

  • Existing organizationDataStoresRegistry.test.ts + clickhouseFactory.test.ts still pass (constructor sites updated; behavior unchanged for tests).
  • After deploy to test cloud, retry /admin/data-stores "Add data store" form for the HIPAA org — should now succeed and the row should appear.
  • Verify the registry's polling reload picks up the new row within ORGANIZATION_DATA_STORES_RELOAD_INTERVAL_MS (60s default) and the factory starts routing to the org-scoped instance.

…writer prisma

The singleton was constructed with $replica, so addDataStore /
updateDataStore / deleteDataStore (and their backing SecretStore upserts)
ran against the read-only replica and Postgres rejected the INSERT with
code 25006:

    cannot execute INSERT in a read-only transaction

Symptom: admin /admin/data-stores form returns a 400 with the
"prisma.secretStore.upsert" Prisma error wrapping the 25006 message.
Read path (loadFromDatabase + its SecretStore.getSecret) is unaffected
because findMany + the secret read are read-only.

Fix: change the registry constructor to take a writer alongside the
replica. Read path keeps using the replica (it's cache-fill, not on a
user-latency-sensitive path); write methods use the writer. Singleton
in organizationDataStoresRegistryInstance.server.ts now passes both
(prisma, $replica). Test sites pass (prisma, prisma) — the testcontainer
exposes a single client so the two roles collapse.
@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented May 23, 2026

⚠️ No Changeset found

Latest commit: c16cfb5

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 23, 2026

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 32f66722-fdbb-4760-a214-3ce28621dfb8

📥 Commits

Reviewing files that changed from the base of the PR and between 61ca40b and c16cfb5.

📒 Files selected for processing (4)
  • apps/webapp/app/services/dataStores/organizationDataStoresRegistry.server.ts
  • apps/webapp/app/services/dataStores/organizationDataStoresRegistryInstance.server.ts
  • apps/webapp/test/clickhouseFactory.test.ts
  • apps/webapp/test/organizationDataStoresRegistry.test.ts
📜 Recent review details
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (11)
  • GitHub Check: webapp / 🧪 Unit Tests: Webapp (3, 8)
  • GitHub Check: webapp / 🧪 Unit Tests: Webapp (8, 8)
  • GitHub Check: webapp / 🧪 Unit Tests: Webapp (7, 8)
  • GitHub Check: webapp / 🧪 Unit Tests: Webapp (4, 8)
  • GitHub Check: webapp / 🧪 Unit Tests: Webapp (1, 8)
  • GitHub Check: webapp / 🧪 Unit Tests: Webapp (5, 8)
  • GitHub Check: webapp / 🧪 Unit Tests: Webapp (2, 8)
  • GitHub Check: webapp / 🧪 Unit Tests: Webapp (6, 8)
  • GitHub Check: e2e-webapp / 🧪 E2E Tests: Webapp
  • GitHub Check: typecheck / typecheck
  • GitHub Check: Analyze (javascript-typescript)
🧰 Additional context used
📓 Path-based instructions (10)
**/*.{ts,tsx}

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

**/*.{ts,tsx}: Use types over interfaces for TypeScript
Avoid using enums; prefer string unions or const objects instead

Files:

  • apps/webapp/test/clickhouseFactory.test.ts
  • apps/webapp/app/services/dataStores/organizationDataStoresRegistryInstance.server.ts
  • apps/webapp/app/services/dataStores/organizationDataStoresRegistry.server.ts
  • apps/webapp/test/organizationDataStoresRegistry.test.ts
{packages/core,apps/webapp}/**/*.{ts,tsx}

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

Use zod for validation in packages/core and apps/webapp

Files:

  • apps/webapp/test/clickhouseFactory.test.ts
  • apps/webapp/app/services/dataStores/organizationDataStoresRegistryInstance.server.ts
  • apps/webapp/app/services/dataStores/organizationDataStoresRegistry.server.ts
  • apps/webapp/test/organizationDataStoresRegistry.test.ts
**/*.{ts,tsx,js,jsx}

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

Use function declarations instead of default exports

**/*.{ts,tsx,js,jsx}: Prefer static imports over dynamic imports. Only use dynamic import() when circular dependencies cannot be resolved otherwise, code splitting is needed for performance, or the module must be loaded conditionally at runtime.
Import from @trigger.dev/core using subpaths only - never import from the root.
When writing Trigger.dev tasks, always import from @trigger.dev/sdk. Never use @trigger.dev/sdk/v3 or deprecated client.defineJob.
Add agentcrumbs markers (// @Crumbs or `#region `@crumbs) as you write code, not just when debugging. They stay on the branch throughout development and are stripped by agentcrumbs strip before merge.

Files:

  • apps/webapp/test/clickhouseFactory.test.ts
  • apps/webapp/app/services/dataStores/organizationDataStoresRegistryInstance.server.ts
  • apps/webapp/app/services/dataStores/organizationDataStoresRegistry.server.ts
  • apps/webapp/test/organizationDataStoresRegistry.test.ts
**/*.{test,spec}.{ts,tsx}

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

Use vitest for all tests in the Trigger.dev repository

Files:

  • apps/webapp/test/clickhouseFactory.test.ts
  • apps/webapp/test/organizationDataStoresRegistry.test.ts
**/*.ts

📄 CodeRabbit inference engine (.cursor/rules/otel-metrics.mdc)

**/*.ts: When creating or editing OTEL metrics (counters, histograms, gauges), ensure metric attributes have low cardinality by using only enums, booleans, bounded error codes, or bounded shard IDs
Do not use high-cardinality attributes in OTEL metrics such as UUIDs/IDs (envId, userId, runId, projectId, organizationId), unbounded integers (itemCount, batchSize, retryCount), timestamps (createdAt, startTime), or free-form strings (errorMessage, taskName, queueName)
When exporting OTEL metrics via OTLP to Prometheus, be aware that the exporter automatically adds unit suffixes to metric names (e.g., 'my_duration_ms' becomes 'my_duration_ms_milliseconds', 'my_counter' becomes 'my_counter_total'). Account for these transformations when writing Grafana dashboards or Prometheus queries

Files:

  • apps/webapp/test/clickhouseFactory.test.ts
  • apps/webapp/app/services/dataStores/organizationDataStoresRegistryInstance.server.ts
  • apps/webapp/app/services/dataStores/organizationDataStoresRegistry.server.ts
  • apps/webapp/test/organizationDataStoresRegistry.test.ts
apps/webapp/**/*.{ts,tsx}

📄 CodeRabbit inference engine (.cursor/rules/webapp.mdc)

apps/webapp/**/*.{ts,tsx}: Access environment variables through the env export of env.server.ts instead of directly accessing process.env
Use subpath exports from @trigger.dev/core package instead of importing from the root @trigger.dev/core path

Use named constants for sentinel/placeholder values (e.g. const UNSET_VALUE = '__unset__') instead of raw string literals scattered across comparisons

Files:

  • apps/webapp/test/clickhouseFactory.test.ts
  • apps/webapp/app/services/dataStores/organizationDataStoresRegistryInstance.server.ts
  • apps/webapp/app/services/dataStores/organizationDataStoresRegistry.server.ts
  • apps/webapp/test/organizationDataStoresRegistry.test.ts
apps/webapp/**/*.test.{ts,tsx}

📄 CodeRabbit inference engine (.cursor/rules/webapp.mdc)

Do not import env.server.ts directly or indirectly into test files; instead pass environment-dependent values through options/parameters to make code testable

For testable code, never import env.server.ts in test files. Pass configuration as options instead (e.g., realtimeClient.server.ts takes config as constructor arg, realtimeClientGlobal.server.ts creates singleton with env config)

Files:

  • apps/webapp/test/clickhouseFactory.test.ts
  • apps/webapp/test/organizationDataStoresRegistry.test.ts
**/*.{js,jsx,ts,tsx,json,md,yml,yaml}

📄 CodeRabbit inference engine (AGENTS.md)

Code formatting must be enforced using Prettier before committing

Files:

  • apps/webapp/test/clickhouseFactory.test.ts
  • apps/webapp/app/services/dataStores/organizationDataStoresRegistryInstance.server.ts
  • apps/webapp/app/services/dataStores/organizationDataStoresRegistry.server.ts
  • apps/webapp/test/organizationDataStoresRegistry.test.ts
**/*.test.{ts,tsx,js,jsx}

📄 CodeRabbit inference engine (AGENTS.md)

**/*.test.{ts,tsx,js,jsx}: Test files should live beside the files under test and use descriptive describe and it blocks
Unit tests should use vitest framework
Tests should avoid mocks or stubs and use helpers from @internal/testcontainers when Redis or Postgres are needed

**/*.test.{ts,tsx,js,jsx}: Never mock anything in tests - use testcontainers instead.
Test files should be placed next to source files (e.g., MyService.ts -> MyService.test.ts).

Files:

  • apps/webapp/test/clickhouseFactory.test.ts
  • apps/webapp/test/organizationDataStoresRegistry.test.ts
apps/webapp/**/*.server.ts

📄 CodeRabbit inference engine (apps/webapp/CLAUDE.md)

apps/webapp/**/*.server.ts: Never use request.signal for detecting client disconnects. Use getRequestAbortSignal() from app/services/httpAsyncStorage.server.ts instead, which is wired directly to Express res.on('close') and fires reliably
Access environment variables via env export from app/env.server.ts. Never use process.env directly
Always use findFirst instead of findUnique in Prisma queries. findUnique has an implicit DataLoader that batches concurrent calls and has active bugs even in Prisma 6.x (uppercase UUIDs returning null, composite key SQL correctness issues, 5-10x worse performance). findFirst is never batched and avoids this entire class of issues

Files:

  • apps/webapp/app/services/dataStores/organizationDataStoresRegistryInstance.server.ts
  • apps/webapp/app/services/dataStores/organizationDataStoresRegistry.server.ts
🧠 Learnings (9)
📚 Learning: 2026-03-22T13:26:12.060Z
Learnt from: ericallam
Repo: triggerdotdev/trigger.dev PR: 3244
File: apps/webapp/app/components/code/TextEditor.tsx:81-86
Timestamp: 2026-03-22T13:26:12.060Z
Learning: In the triggerdotdev/trigger.dev codebase, do not flag `navigator.clipboard.writeText(...)` calls for `missing-await`/`unhandled-promise` issues. These clipboard writes are intentionally invoked without `await` and without `catch` handlers across the project; keep that behavior consistent when reviewing TypeScript/TSX files (e.g., usages like in `apps/webapp/app/components/code/TextEditor.tsx`).

Applied to files:

  • apps/webapp/test/clickhouseFactory.test.ts
  • apps/webapp/app/services/dataStores/organizationDataStoresRegistryInstance.server.ts
  • apps/webapp/app/services/dataStores/organizationDataStoresRegistry.server.ts
  • apps/webapp/test/organizationDataStoresRegistry.test.ts
📚 Learning: 2026-03-22T19:24:14.403Z
Learnt from: matt-aitken
Repo: triggerdotdev/trigger.dev PR: 3187
File: apps/webapp/app/v3/services/alerts/deliverErrorGroupAlert.server.ts:200-204
Timestamp: 2026-03-22T19:24:14.403Z
Learning: In the triggerdotdev/trigger.dev codebase, webhook URLs are not expected to contain embedded credentials/secrets (e.g., fields like `ProjectAlertWebhookProperties` should only hold credential-free webhook endpoints). During code review, if you see logging or inclusion of raw webhook URLs in error messages, do not automatically treat it as a credential-leak/secrets-in-logs issue by default—first verify the URL does not contain embedded credentials (for example, no username/password in the URL, no obvious secret/token query params or fragments). If the URL is credential-free per this project’s conventions, allow the logging.

Applied to files:

  • apps/webapp/test/clickhouseFactory.test.ts
  • apps/webapp/app/services/dataStores/organizationDataStoresRegistryInstance.server.ts
  • apps/webapp/app/services/dataStores/organizationDataStoresRegistry.server.ts
  • apps/webapp/test/organizationDataStoresRegistry.test.ts
📚 Learning: 2026-05-18T08:21:27.694Z
Learnt from: d-cs
Repo: triggerdotdev/trigger.dev PR: 3632
File: apps/webapp/sentry.server.ts:4-21
Timestamp: 2026-05-18T08:21:27.694Z
Learning: When handling Prisma error P1001 ("Can't reach database server") in TypeScript, don’t assume a single error shape. Prisma can surface P1001 via two different error classes/fields: `PrismaClientKnownRequestError` exposes it as `err.code === "P1001"` (common during mid-query connection drops), while `PrismaClientInitializationError` exposes it as `err.errorCode === "P1001"` (common on client startup failure). Therefore, predicates should use `err.code === "P1001" || err.errorCode === "P1001"`. Do not flag `err.code === "P1001"` as “unreachable/never matches,” as it is expected in production.

Applied to files:

  • apps/webapp/test/clickhouseFactory.test.ts
  • apps/webapp/app/services/dataStores/organizationDataStoresRegistryInstance.server.ts
  • apps/webapp/app/services/dataStores/organizationDataStoresRegistry.server.ts
  • apps/webapp/test/organizationDataStoresRegistry.test.ts
📚 Learning: 2026-05-18T08:21:27.694Z
Learnt from: d-cs
Repo: triggerdotdev/trigger.dev PR: 3632
File: apps/webapp/sentry.server.ts:4-21
Timestamp: 2026-05-18T08:21:27.694Z
Learning: When handling Prisma errors for P1001 ("Can't reach database server"), do not assume it only appears under a single property name. Prisma may surface P1001 via either `PrismaClientKnownRequestError` (`err.code === "P1001"`, e.g., mid-query connection drops) or `PrismaClientInitializationError` (`err.errorCode === "P1001"`, e.g., client startup connection failure). To reliably detect the condition, check `err.code === "P1001" || err.errorCode === "P1001"`, and avoid review rules that would incorrectly flag `err.code === "P1001"` as unreachable/never-matching.

Applied to files:

  • apps/webapp/test/clickhouseFactory.test.ts
  • apps/webapp/app/services/dataStores/organizationDataStoresRegistryInstance.server.ts
  • apps/webapp/app/services/dataStores/organizationDataStoresRegistry.server.ts
  • apps/webapp/test/organizationDataStoresRegistry.test.ts
📚 Learning: 2026-05-07T12:25:18.271Z
Learnt from: d-cs
Repo: triggerdotdev/trigger.dev PR: 3531
File: apps/webapp/test/sentryTraceContext.server.test.ts:9-47
Timestamp: 2026-05-07T12:25:18.271Z
Learning: In the triggerdotdev/trigger.dev webapp test suite, it is acceptable to leave `createInMemoryTracing()` calls that register a global `NodeTracerProvider` without `afterEach`/`afterAll` teardown. Do not flag this as a test-ordering risk when the code follows the established pattern used across webapp tests (e.g., replication service/benchmark/backfiller tests). This is considered safe because `trace.getActiveSpan()` when called outside a `context.with(...)` block reads `AsyncLocalStorage.getStore()` (undefined when no `run()` scope exists), so it falls back to `ROOT_CONTEXT` with no attached span—regardless of which provider is registered.

Applied to files:

  • apps/webapp/test/clickhouseFactory.test.ts
  • apps/webapp/test/organizationDataStoresRegistry.test.ts
📚 Learning: 2026-05-12T21:04:05.815Z
Learnt from: ericallam
Repo: triggerdotdev/trigger.dev PR: 3542
File: apps/webapp/app/components/sessions/v1/SessionStatus.tsx:1-3
Timestamp: 2026-05-12T21:04:05.815Z
Learning: In this Remix + TypeScript codebase, do not flag a server/client boundary violation when a file imports only types from a module matching `*.server`.

Specifically, it’s safe to import types using `import type { Foo } from "*.server"` or `import { type Foo } from "*.server"` because TypeScript erases type-only imports at compile time and they emit no JavaScript, so they won’t cross the Remix server/client bundle boundary.

Only raise the boundary concern for value imports (e.g., `import { Foo }` without `type`, or `import Foo`), since those produce JavaScript output.

Applied to files:

  • apps/webapp/test/clickhouseFactory.test.ts
  • apps/webapp/app/services/dataStores/organizationDataStoresRegistryInstance.server.ts
  • apps/webapp/app/services/dataStores/organizationDataStoresRegistry.server.ts
  • apps/webapp/test/organizationDataStoresRegistry.test.ts
📚 Learning: 2026-05-18T14:40:02.173Z
Learnt from: ericallam
Repo: triggerdotdev/trigger.dev PR: 3658
File: packages/core/src/v3/realtimeStreams/manager.test.ts:1-147
Timestamp: 2026-05-18T14:40:02.173Z
Learning: In the triggerdotdev/trigger.dev repo, the policy “Never mock anything — use testcontainers instead” should only be enforced for integration tests that interact with real external services (e.g., Redis, Postgres) via actual infrastructure. For unit tests that exercise pure in-memory logic (e.g., cache semantics) it is OK to stub collaborators such as `ApiClient` using Vitest (`vi.fn()`) to assert call counts or control behavior. Do not flag `vi.fn()`-based `ApiClient` stubs in unit tests as violations of the testcontainers policy.

Applied to files:

  • apps/webapp/test/clickhouseFactory.test.ts
  • apps/webapp/test/organizationDataStoresRegistry.test.ts
📚 Learning: 2026-03-26T09:02:07.973Z
Learnt from: myftija
Repo: triggerdotdev/trigger.dev PR: 3274
File: apps/webapp/app/services/runsReplicationService.server.ts:922-924
Timestamp: 2026-03-26T09:02:07.973Z
Learning: When parsing Trigger.dev task run annotations in server-side services, keep `TaskRun.annotations` strictly conforming to the `RunAnnotations` schema from `trigger.dev/core/v3`. If the code already uses `RunAnnotations.safeParse` (e.g., in a `#parseAnnotations` helper), treat that as intentional/necessary for atomic, schema-accurate annotation handling. Do not recommend relaxing the annotation payload schema or using a permissive “passthrough” parse path, since the annotations are expected to be written atomically in one operation and should not contain partial/legacy payloads that would require a looser parser.

Applied to files:

  • apps/webapp/app/services/dataStores/organizationDataStoresRegistryInstance.server.ts
  • apps/webapp/app/services/dataStores/organizationDataStoresRegistry.server.ts
📚 Learning: 2026-05-05T09:38:02.512Z
Learnt from: d-cs
Repo: triggerdotdev/trigger.dev PR: 3523
File: apps/webapp/app/routes/api.v3.batches.ts:178-181
Timestamp: 2026-05-05T09:38:02.512Z
Learning: When reviewing code that catches `ServiceValidationError` in `*.server.ts` files, do not blindly forward `error.status` to HTTP responses, because SVEs may be thrown with non-default statuses (e.g., 400/500) and forwarding them can cause client-visible behavioral regressions (e.g., surfacing 500s to clients). Prefer a safe default response status of `error.status ?? 422`, but only after confirming via the reachable call graph that the caught `ServiceValidationError` instances are expected to carry those non-default statuses; otherwise, normalize to `422` to avoid unexpected client-visible 5xx behavior.

Applied to files:

  • apps/webapp/app/services/dataStores/organizationDataStoresRegistryInstance.server.ts
  • apps/webapp/app/services/dataStores/organizationDataStoresRegistry.server.ts
🔇 Additional comments (4)
apps/webapp/app/services/dataStores/organizationDataStoresRegistry.server.ts (1)

10-22: LGTM!

Also applies to: 36-38, 53-53, 56-56, 141-141, 144-144, 169-169, 173-173, 186-186, 191-191

apps/webapp/app/services/dataStores/organizationDataStoresRegistryInstance.server.ts (1)

2-2: LGTM!

Also applies to: 10-10

apps/webapp/test/clickhouseFactory.test.ts (1)

19-19: LGTM!

Also applies to: 31-31, 55-55, 78-78, 107-107

apps/webapp/test/organizationDataStoresRegistry.test.ts (1)

16-16: LGTM!

Also applies to: 22-22, 28-28, 39-39, 45-45, 66-66, 84-84, 100-100, 123-123, 154-154, 179-179, 197-197, 213-213


Walkthrough

This PR refactors OrganizationDataStoresRegistry to separate Prisma clients for read and write operations. The constructor now accepts two distinct clients: a writer client for mutations and a replica client for reads and polling. The loadFromDatabase() method queries via the replica client, while addDataStore(), updateDataStore(), and deleteDataStore() perform mutations via the writer client. The singleton initialization and all test instantiations are updated to pass both clients.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarizes the main change: routing writes through the writer Prisma client instead of the read-only replica.
Description check ✅ Passed The description is comprehensive and well-structured, covering the bug, fix, affected files, and test plan, though it lacks the repository's template structure with explicit checklist and changelog sections.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix-org-data-stores-registry-write-path

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown
Contributor

@devin-ai-integration devin-ai-integration Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Devin Review found 1 potential issue.

View 1 additional finding in Devin Review.

Open in Devin Review

@matt-aitken matt-aitken enabled auto-merge (squash) May 23, 2026 11:00
@matt-aitken matt-aitken merged commit 2fcc484 into main May 23, 2026
32 checks passed
@matt-aitken matt-aitken deleted the fix-org-data-stores-registry-write-path branch May 23, 2026 11:00
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.

3 participants