feat(webapp,cli,core): list production project runtime updates - #4659
Draft
carderne wants to merge 1 commit into
Draft
feat(webapp,cli,core): list production project runtime updates#4659carderne wants to merge 1 commit into
carderne wants to merge 1 commit into
Conversation
🦋 Changeset detectedLatest commit: 1adfb2c The changes in this PR will be included in the next version bump. This PR includes changesets to release 27 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Contributor
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
Included review availability: Your plan provides up to 10 included reviews per hour; 5 remain after this review. 📜 Recent review details⏰ Context from checks skipped due to timeout. (4)
WalkthroughAdds Node.js runtime detection and typed project-runtime response data. Adds server and PAT API loading for current production runtimes. Adds an organization runtime-updates settings page, navigation item, path builder, and organization deeplink handling. Adds the Merge Risk: 🔵 Low · up to The new runtime-updates settings page may render deployment times differently on the server and browser, causing hydration mismatches or inconsistent page rendering. This is a bounded risk that is mergeable with explicit owner awareness. 🚥 Pre-merge checks | ✅ 3 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (3 passed)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
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 |
Contributor
Observability mapAs of 19/100 over 445 measured of 461 entry points (base 19, no change) What this PR changed
FIX FIRST
AUDIT 3 of 50 sensitive mutations record an actor. 47 without one. What the score is made ofThe score and findings here are report-only and never gate the merge. Separately, a required test suite keeps this tool's symbol and route lists in sync with the code they name, and can fail a pull request that renames or removes a symbol they reference, or that adds the first route with a segment they anticipate. Each failure names the list to edit. The rules and their reasons: internal-packages/observability-map/README.md. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 77c5c915-e15f-4fb4-9f2f-6ce0237ac6c5
📒 Files selected for processing (15)
.changeset/list-project-runtime-updates.mdapps/webapp/app/components/navigation/OrganizationSettingsSideMenu.tsxapps/webapp/app/routes/[_].$.tsapps/webapp/app/routes/_app.orgs.$organizationSlug.settings.runtime-updates/route.tsxapps/webapp/app/routes/api.v1.projects.runtimes.tsapps/webapp/app/services/projectRuntimeUpdates.server.tsapps/webapp/app/utils/deeplinkPages.test.tsapps/webapp/app/utils/deeplinkPages.tsapps/webapp/app/utils/pathBuilder.tspackages/cli-v3/src/apiClient.tspackages/cli-v3/src/cli/index.tspackages/cli-v3/src/commands/projects/index.tspackages/cli-v3/src/commands/projects/list.tspackages/core/src/v3/schemas/api-type.test.tspackages/core/src/v3/schemas/api.ts
Included review availability: Your plan includes up to 10 reviews per rolling hour; 5 remain after this review.
📜 Review details
⏰ Context from checks skipped due to timeout. (37)
- GitHub Check: webapp / 🧪 Unit Tests: Webapp (10, 12)
- GitHub Check: webapp / 🧪 Unit Tests: Webapp (5, 12)
- GitHub Check: webapp / 🧪 Unit Tests: Webapp (11, 12)
- GitHub Check: webapp / 🧪 Unit Tests: Webapp (6, 12)
- GitHub Check: webapp / 🧪 Unit Tests: Webapp (2, 12)
- GitHub Check: webapp / 🧪 Unit Tests: Webapp (8, 12)
- GitHub Check: webapp / 🧪 Unit Tests: Webapp (12, 12)
- GitHub Check: webapp / 🧪 Unit Tests: Webapp (7, 12)
- GitHub Check: webapp / 🧪 Unit Tests: Webapp (3, 12)
- GitHub Check: webapp / 🧪 Unit Tests: Webapp (1, 12)
- GitHub Check: webapp / 🧪 Unit Tests: Webapp (9, 12)
- GitHub Check: sdk-compat / Node.js 20.20 (warp-ubuntu-latest-x64-4x)
- GitHub Check: sdk-compat / Node.js 22.23 (warp-ubuntu-latest-x64-4x)
- GitHub Check: sdk-compat / Node.js 26.4 (warp-ubuntu-latest-x64-4x)
- GitHub Check: webapp / 🧪 Unit Tests: Webapp (4, 12)
- GitHub Check: obsmap / 🧪 Unit Tests: Observability Map
- GitHub Check: sdk-compat / Cloudflare Workers
- GitHub Check: sdk-compat / Node.js 24.18 (warp-ubuntu-latest-x64-4x)
- GitHub Check: typecheck / typecheck
- GitHub Check: e2e / 🧪 CLI v3 tests (warp-ubuntu-latest-x64-4x - npm)
- GitHub Check: packages / 🧪 Unit Tests: Packages (2, 3)
- GitHub Check: e2e / 🧪 CLI v3 tests (warp-windows-latest-x64-8x - npm)
- GitHub Check: e2e / 🧪 CLI v3 tests (warp-ubuntu-latest-x64-4x - pnpm)
- GitHub Check: sdk-compat / Bun Runtime
- GitHub Check: e2e / 🧪 CLI v3 tests (warp-windows-latest-x64-8x - pnpm)
- GitHub Check: packages / 🧪 Unit Tests: Packages (1, 3)
- GitHub Check: fk-cascade-guard / fk-cascade-guard
- GitHub Check: internal / 🧪 Unit Tests: Internal
- GitHub Check: packages / 🧪 Unit Tests: Packages (3, 3)
- GitHub Check: runops-guard / runops-guard
- GitHub Check: sdk-compat / Deno Runtime
- GitHub Check: e2e-webapp / 🧪 E2E Tests: Webapp
- GitHub Check: report
- GitHub Check: code-quality / code-quality
- GitHub Check: 🛡️ E2E Auth Tests (full)
- GitHub Check: Analyze (javascript-typescript)
- GitHub Check: Build and publish previews
🧰 Additional context used
📓 Path-based instructions (17)
**/*.{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
**/*.{ts,tsx}: Prefer static imports over dynamic imports. Only use dynamicimport()when:
- Circular dependencies cannot be resolved otherwise
- Code splitting is genuinely needed for performance
- The module must be loaded conditionally at runtime
Zod is pinned to a single version across the entire monorepo (currently3.25.76). When adding zod to a new or existing package, use the exact same version as the rest of the repo - never a different version or a range. Mismatched zod versions cause runtime type incompatibilities (e.g., schemas from one package can't be used as body validators in another).
Do not reintroduce V1.
Add crumbs as you write code — not just when debugging.
Do not invent new namespaces — pick from this table or ask first.
Files:
packages/cli-v3/src/cli/index.tsapps/webapp/app/utils/pathBuilder.tsapps/webapp/app/components/navigation/OrganizationSettingsSideMenu.tsxapps/webapp/app/utils/deeplinkPages.test.tspackages/cli-v3/src/apiClient.tspackages/cli-v3/src/commands/projects/list.tspackages/cli-v3/src/commands/projects/index.tsapps/webapp/app/routes/api.v1.projects.runtimes.tsapps/webapp/app/services/projectRuntimeUpdates.server.tspackages/core/src/v3/schemas/api-type.test.tsapps/webapp/app/routes/_app.orgs.$organizationSlug.settings.runtime-updates/route.tsxapps/webapp/app/routes/[_].$.tspackages/core/src/v3/schemas/api.tsapps/webapp/app/utils/deeplinkPages.ts
**/*.{ts,tsx,js,jsx}
📄 CodeRabbit inference engine (.github/copilot-instructions.md)
Use function declarations instead of default exports
Files:
packages/cli-v3/src/cli/index.tsapps/webapp/app/utils/pathBuilder.tsapps/webapp/app/components/navigation/OrganizationSettingsSideMenu.tsxapps/webapp/app/utils/deeplinkPages.test.tspackages/cli-v3/src/apiClient.tspackages/cli-v3/src/commands/projects/list.tspackages/cli-v3/src/commands/projects/index.tsapps/webapp/app/routes/api.v1.projects.runtimes.tsapps/webapp/app/services/projectRuntimeUpdates.server.tspackages/core/src/v3/schemas/api-type.test.tsapps/webapp/app/routes/_app.orgs.$organizationSlug.settings.runtime-updates/route.tsxapps/webapp/app/routes/[_].$.tspackages/core/src/v3/schemas/api.tsapps/webapp/app/utils/deeplinkPages.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:
packages/cli-v3/src/cli/index.tsapps/webapp/app/utils/pathBuilder.tsapps/webapp/app/utils/deeplinkPages.test.tspackages/cli-v3/src/apiClient.tspackages/cli-v3/src/commands/projects/list.tspackages/cli-v3/src/commands/projects/index.tsapps/webapp/app/routes/api.v1.projects.runtimes.tsapps/webapp/app/services/projectRuntimeUpdates.server.tspackages/core/src/v3/schemas/api-type.test.tsapps/webapp/app/routes/[_].$.tspackages/core/src/v3/schemas/api.tsapps/webapp/app/utils/deeplinkPages.ts
packages/**/*.{ts,tsx}
📄 CodeRabbit inference engine (AGENTS.md)
packages/**/*.{ts,tsx}: - Public packages (packages/*): Usebuild.
Always import from@trigger.dev/sdk. Never use@trigger.dev/sdk/v3or deprecatedclient.defineJob.
Files:
packages/cli-v3/src/cli/index.tspackages/cli-v3/src/apiClient.tspackages/cli-v3/src/commands/projects/list.tspackages/cli-v3/src/commands/projects/index.tspackages/core/src/v3/schemas/api-type.test.tspackages/core/src/v3/schemas/api.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/app/utils/pathBuilder.tsapps/webapp/app/components/navigation/OrganizationSettingsSideMenu.tsxapps/webapp/app/utils/deeplinkPages.test.tsapps/webapp/app/routes/api.v1.projects.runtimes.tsapps/webapp/app/services/projectRuntimeUpdates.server.tspackages/core/src/v3/schemas/api-type.test.tsapps/webapp/app/routes/_app.orgs.$organizationSlug.settings.runtime-updates/route.tsxapps/webapp/app/routes/[_].$.tspackages/core/src/v3/schemas/api.tsapps/webapp/app/utils/deeplinkPages.ts
apps/webapp/**/*.{ts,tsx}
📄 CodeRabbit inference engine (.cursor/rules/webapp.mdc)
apps/webapp/**/*.{ts,tsx}: Access environment variables through theenvexport ofenv.server.tsinstead of directly accessingprocess.env
Use subpath exports from@trigger.dev/corepackage instead of importing from the root@trigger.dev/corepath
Files:
apps/webapp/app/utils/pathBuilder.tsapps/webapp/app/components/navigation/OrganizationSettingsSideMenu.tsxapps/webapp/app/utils/deeplinkPages.test.tsapps/webapp/app/routes/api.v1.projects.runtimes.tsapps/webapp/app/services/projectRuntimeUpdates.server.tsapps/webapp/app/routes/_app.orgs.$organizationSlug.settings.runtime-updates/route.tsxapps/webapp/app/routes/[_].$.tsapps/webapp/app/utils/deeplinkPages.ts
apps/webapp/app/**/*.{ts,tsx}
📄 CodeRabbit inference engine (apps/webapp/CLAUDE.md)
apps/webapp/app/**/*.{ts,tsx}: For dashboard changes, visually verify the running Remix app with Chrome DevTools MCP, using snapshots, screenshots, interaction, and console-message checks as appropriate.
UseuseCallbackanduseMemoonly for context provider values, expensive derived data used as a dependency, or stable references required by dependency arrays; do not wrap ordinary event handlers or trivial computations.
Use named constants for sentinel or placeholder values instead of scattering raw string literals across comparisons.
Files:
apps/webapp/app/utils/pathBuilder.tsapps/webapp/app/components/navigation/OrganizationSettingsSideMenu.tsxapps/webapp/app/utils/deeplinkPages.test.tsapps/webapp/app/routes/api.v1.projects.runtimes.tsapps/webapp/app/services/projectRuntimeUpdates.server.tsapps/webapp/app/routes/_app.orgs.$organizationSlug.settings.runtime-updates/route.tsxapps/webapp/app/routes/[_].$.tsapps/webapp/app/utils/deeplinkPages.ts
apps/webapp/app/**/*.ts
📄 CodeRabbit inference engine (apps/webapp/CLAUDE.md)
apps/webapp/app/**/*.ts: Never userequest.signalto detect client disconnects. UsegetRequestAbortSignal()fromapp/services/httpAsyncStorage.server.ts, which is wired to Express response close events.
Access environment variables through theenvexport fromapp/env.server.ts; never useprocess.envdirectly.
Always use PrismafindFirstinstead offindUnique.
Always use the$transactionhelper from~/db.server, never callprisma.$transactionor$replica.$transactiondirectly. Pass isolation levels as strings, useSerializablefor correctness-critical read-then-write invariants, and guard possibly undefined helper results when a definite value is required.
Files:
apps/webapp/app/utils/pathBuilder.tsapps/webapp/app/utils/deeplinkPages.test.tsapps/webapp/app/routes/api.v1.projects.runtimes.tsapps/webapp/app/services/projectRuntimeUpdates.server.tsapps/webapp/app/routes/[_].$.tsapps/webapp/app/utils/deeplinkPages.ts
apps/**/*.{ts,tsx}
📄 CodeRabbit inference engine (AGENTS.md)
apps/**/*.{ts,tsx}: - Apps and internal packages (apps/*,internal-packages/*): Usetypecheck. Never usebuildfor these — building proves almost nothing about correctness.
Always import from@trigger.dev/sdk. Never use@trigger.dev/sdk/v3or deprecatedclient.defineJob.
Files:
apps/webapp/app/utils/pathBuilder.tsapps/webapp/app/components/navigation/OrganizationSettingsSideMenu.tsxapps/webapp/app/utils/deeplinkPages.test.tsapps/webapp/app/routes/api.v1.projects.runtimes.tsapps/webapp/app/services/projectRuntimeUpdates.server.tsapps/webapp/app/routes/_app.orgs.$organizationSlug.settings.runtime-updates/route.tsxapps/webapp/app/routes/[_].$.tsapps/webapp/app/utils/deeplinkPages.ts
**/*.{test,spec}.{ts,tsx}
📄 CodeRabbit inference engine (.github/copilot-instructions.md)
Use vitest for all tests in the Trigger.dev repository
We use vitest exclusively. Never mock anything - use testcontainers instead.
Files:
apps/webapp/app/utils/deeplinkPages.test.tspackages/core/src/v3/schemas/api-type.test.ts
apps/webapp/**/*.test.{ts,tsx}
📄 CodeRabbit inference engine (.cursor/rules/webapp.mdc)
Do not import
env.server.tsdirectly or indirectly into test files; instead pass environment-dependent values through options/parameters to make code testable
Files:
apps/webapp/app/utils/deeplinkPages.test.ts
apps/webapp/**/*.{test,spec}.{ts,tsx}
📄 CodeRabbit inference engine (apps/webapp/CLAUDE.md)
Test files must not import
app/env.server.ts; pass configuration as options instead.
Files:
apps/webapp/app/utils/deeplinkPages.test.ts
**/*.test.{ts,tsx}
📄 CodeRabbit inference engine (AGENTS.md)
Test files go next to source files (e.g.,
MyService.ts->MyService.test.ts).
Files:
apps/webapp/app/utils/deeplinkPages.test.tspackages/core/src/v3/schemas/api-type.test.ts
packages/cli-v3/src/commands/**/*
📄 CodeRabbit inference engine (packages/cli-v3/CLAUDE.md)
CLI command definitions should be located in
src/commands/
Files:
packages/cli-v3/src/commands/projects/list.tspackages/cli-v3/src/commands/projects/index.ts
apps/webapp/app/routes/**/*.ts
📄 CodeRabbit inference engine (apps/webapp/CLAUDE.md)
apps/webapp/app/routes/**/*.ts: Use Remix flat-file route conventions with dot-separated segments; for example,api.v1.tasks.$taskId.trigger.tsmaps to/api/v1/tasks/:taskId/trigger.
PAT-authenticated API routes must resolve their target organization or project within the caller's membership scope, using a membership filter or a helper such asfindProjectByReforresolveOrganizationForApiUser; RBAC authorization alone is insufficient.
Files:
apps/webapp/app/routes/api.v1.projects.runtimes.tsapps/webapp/app/routes/[_].$.ts
packages/core/**/*.{ts,tsx,js,jsx}
📄 CodeRabbit inference engine (packages/core/CLAUDE.md)
Never import the root package (
@trigger.dev/core). Always use subpath imports such as@trigger.dev/core/v3,@trigger.dev/core/v3/utils,@trigger.dev/core/logger, or@trigger.dev/core/schemas
Files:
packages/core/src/v3/schemas/api-type.test.tspackages/core/src/v3/schemas/api.ts
packages/core/**/*.{ts,tsx}
📄 CodeRabbit inference engine (AGENTS.md)
- packages/core (
@trigger.dev/core): Shared types. Import subpaths only (never root).
Files:
packages/core/src/v3/schemas/api-type.test.tspackages/core/src/v3/schemas/api.ts
🧠 Learnings (29)
📚 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:
packages/cli-v3/src/cli/index.tsapps/webapp/app/utils/pathBuilder.tsapps/webapp/app/components/navigation/OrganizationSettingsSideMenu.tsxapps/webapp/app/utils/deeplinkPages.test.tspackages/cli-v3/src/apiClient.tspackages/cli-v3/src/commands/projects/list.tspackages/cli-v3/src/commands/projects/index.tsapps/webapp/app/routes/api.v1.projects.runtimes.tsapps/webapp/app/services/projectRuntimeUpdates.server.tspackages/core/src/v3/schemas/api-type.test.tsapps/webapp/app/routes/_app.orgs.$organizationSlug.settings.runtime-updates/route.tsxapps/webapp/app/routes/[_].$.tspackages/core/src/v3/schemas/api.tsapps/webapp/app/utils/deeplinkPages.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:
packages/cli-v3/src/cli/index.tsapps/webapp/app/utils/pathBuilder.tsapps/webapp/app/components/navigation/OrganizationSettingsSideMenu.tsxapps/webapp/app/utils/deeplinkPages.test.tspackages/cli-v3/src/apiClient.tspackages/cli-v3/src/commands/projects/list.tspackages/cli-v3/src/commands/projects/index.tsapps/webapp/app/routes/api.v1.projects.runtimes.tsapps/webapp/app/services/projectRuntimeUpdates.server.tspackages/core/src/v3/schemas/api-type.test.tsapps/webapp/app/routes/_app.orgs.$organizationSlug.settings.runtime-updates/route.tsxapps/webapp/app/routes/[_].$.tspackages/core/src/v3/schemas/api.tsapps/webapp/app/utils/deeplinkPages.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:
packages/cli-v3/src/cli/index.tsapps/webapp/app/utils/pathBuilder.tsapps/webapp/app/components/navigation/OrganizationSettingsSideMenu.tsxapps/webapp/app/utils/deeplinkPages.test.tspackages/cli-v3/src/apiClient.tspackages/cli-v3/src/commands/projects/list.tspackages/cli-v3/src/commands/projects/index.tsapps/webapp/app/routes/api.v1.projects.runtimes.tsapps/webapp/app/services/projectRuntimeUpdates.server.tspackages/core/src/v3/schemas/api-type.test.tsapps/webapp/app/routes/_app.orgs.$organizationSlug.settings.runtime-updates/route.tsxapps/webapp/app/routes/[_].$.tspackages/core/src/v3/schemas/api.tsapps/webapp/app/utils/deeplinkPages.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:
packages/cli-v3/src/cli/index.tsapps/webapp/app/utils/pathBuilder.tsapps/webapp/app/components/navigation/OrganizationSettingsSideMenu.tsxapps/webapp/app/utils/deeplinkPages.test.tspackages/cli-v3/src/apiClient.tspackages/cli-v3/src/commands/projects/list.tspackages/cli-v3/src/commands/projects/index.tsapps/webapp/app/routes/api.v1.projects.runtimes.tsapps/webapp/app/services/projectRuntimeUpdates.server.tspackages/core/src/v3/schemas/api-type.test.tsapps/webapp/app/routes/_app.orgs.$organizationSlug.settings.runtime-updates/route.tsxapps/webapp/app/routes/[_].$.tspackages/core/src/v3/schemas/api.tsapps/webapp/app/utils/deeplinkPages.ts
📚 Learning: 2026-06-13T19:53:13.759Z
Learnt from: ericallam
Repo: triggerdotdev/trigger.dev PR: 3937
File: packages/trigger-sdk/skills/realtime-and-frontend/SKILL.md:258-260
Timestamp: 2026-06-13T19:53:13.759Z
Learning: When reviewing code that uses `trigger.dev/react-hooks`’s `useRealtimeRun`, preserve the call signature where the first argument is the full realtime handle object (not `handle.id`). This is intentional to maintain type-safety and is consistent with the official docs; do not suggest changing the first argument from the handle object to `handle.id`.
Applied to files:
packages/cli-v3/src/cli/index.tsapps/webapp/app/utils/pathBuilder.tsapps/webapp/app/components/navigation/OrganizationSettingsSideMenu.tsxapps/webapp/app/utils/deeplinkPages.test.tspackages/cli-v3/src/apiClient.tspackages/cli-v3/src/commands/projects/list.tspackages/cli-v3/src/commands/projects/index.tsapps/webapp/app/routes/api.v1.projects.runtimes.tsapps/webapp/app/services/projectRuntimeUpdates.server.tspackages/core/src/v3/schemas/api-type.test.tsapps/webapp/app/routes/_app.orgs.$organizationSlug.settings.runtime-updates/route.tsxapps/webapp/app/routes/[_].$.tspackages/core/src/v3/schemas/api.tsapps/webapp/app/utils/deeplinkPages.ts
📚 Learning: 2026-06-17T17:13:49.929Z
Learnt from: matt-aitken
Repo: triggerdotdev/trigger.dev PR: 3948
File: apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.bulk-actions.$bulkActionParam/route.tsx:48-62
Timestamp: 2026-06-17T17:13:49.929Z
Learning: In triggerdotdev/trigger.dev, within `dashboardLoader`/`dashboardAction` (or similar context resolver code) whenever you resolve an organization ID from an organization slug for RBAC/enterprise authorization scope, always read from the primary Prisma client (`prisma`), not `$replica`. Using `$replica` can hit replica-lag and cause the RBAC lookup/authorization to run without the correct org scope (bypassing intended role enforcement). Implement the slug→org lookup with `prisma.organization.findFirst(...)` (or equivalent primary-client query) and add an inline comment documenting why the primary client is required (replica lag could lead to unscoped RBAC checks).
Applied to files:
packages/cli-v3/src/cli/index.tsapps/webapp/app/utils/pathBuilder.tsapps/webapp/app/components/navigation/OrganizationSettingsSideMenu.tsxapps/webapp/app/utils/deeplinkPages.test.tspackages/cli-v3/src/apiClient.tspackages/cli-v3/src/commands/projects/list.tspackages/cli-v3/src/commands/projects/index.tsapps/webapp/app/routes/api.v1.projects.runtimes.tsapps/webapp/app/services/projectRuntimeUpdates.server.tspackages/core/src/v3/schemas/api-type.test.tsapps/webapp/app/routes/_app.orgs.$organizationSlug.settings.runtime-updates/route.tsxapps/webapp/app/routes/[_].$.tspackages/core/src/v3/schemas/api.tsapps/webapp/app/utils/deeplinkPages.ts
📚 Learning: 2026-06-23T13:04:21.413Z
Learnt from: carderne
Repo: triggerdotdev/trigger.dev PR: 4023
File: apps/webapp/app/services/upsertBranch.server.ts:14-18
Timestamp: 2026-06-23T13:04:21.413Z
Learning: In TypeScript, it’s valid to `import { type X }` and then use `typeof X` in a type-only position, e.g. `type Alias = z.infer<typeof X>`. The `type` modifier suppresses the runtime import, but the type checker still has the full exported type so `z.infer<typeof X>` can resolve correctly. In code reviews, don’t flag this as a TypeScript compile error as long as `typeof X` is used in a type context (e.g., with `z.infer`, `type` aliases, generics), not as a runtime value.
Applied to files:
packages/cli-v3/src/cli/index.tsapps/webapp/app/utils/pathBuilder.tsapps/webapp/app/components/navigation/OrganizationSettingsSideMenu.tsxapps/webapp/app/utils/deeplinkPages.test.tspackages/cli-v3/src/apiClient.tspackages/cli-v3/src/commands/projects/list.tspackages/cli-v3/src/commands/projects/index.tsapps/webapp/app/routes/api.v1.projects.runtimes.tsapps/webapp/app/services/projectRuntimeUpdates.server.tspackages/core/src/v3/schemas/api-type.test.tsapps/webapp/app/routes/_app.orgs.$organizationSlug.settings.runtime-updates/route.tsxapps/webapp/app/routes/[_].$.tspackages/core/src/v3/schemas/api.tsapps/webapp/app/utils/deeplinkPages.ts
📚 Learning: 2026-06-04T18:16:35.386Z
Learnt from: nicktrn
Repo: triggerdotdev/trigger.dev PR: 3836
File: apps/supervisor/src/backpressure/backpressureMonitor.ts:3-5
Timestamp: 2026-06-04T18:16:35.386Z
Learning: When reviewing TypeScript in this repo, apply the rule “prefer type aliases over interfaces” only to data/object shapes and union/intersection type modeling. If an interface is being used as a behavioral contract for collaborators to implement (e.g., method-shape interfaces that define required behavior, such as `BackpressureLogger` / `BackpressureSignalSource` in `apps/supervisor/src/backpressure/backpressureMonitor.ts`), keep it as an `interface` and do not flag it as a type-alias-vs-interface violation.
Applied to files:
packages/cli-v3/src/cli/index.tsapps/webapp/app/utils/pathBuilder.tsapps/webapp/app/utils/deeplinkPages.test.tspackages/cli-v3/src/apiClient.tspackages/cli-v3/src/commands/projects/list.tspackages/cli-v3/src/commands/projects/index.tsapps/webapp/app/routes/api.v1.projects.runtimes.tsapps/webapp/app/services/projectRuntimeUpdates.server.tspackages/core/src/v3/schemas/api-type.test.tsapps/webapp/app/routes/[_].$.tspackages/core/src/v3/schemas/api.tsapps/webapp/app/utils/deeplinkPages.ts
📚 Learning: 2026-06-09T17:58:04.699Z
Learnt from: 0ski
Repo: triggerdotdev/trigger.dev PR: 3879
File: apps/webapp/app/models/vercelIntegration.server.ts:619-630
Timestamp: 2026-06-09T17:58:04.699Z
Learning: In this codebase, outbound raw `fetch` calls should typically rely on Node/undici’s default request timeout (about ~300s) rather than adding a per-call `AbortController` + `setTimeout` wrapper inside individual functions (e.g. in files like `apps/webapp/app/models/vercelIntegration.server.ts`). During code review, do not flag the absence of a per-call timeout on a single `fetch` as an issue; if per-call timeouts are needed, they should be implemented via a codebase-wide convention (e.g., a shared fetch wrapper or documented pattern) rather than ad-hoc per-function changes.
Applied to files:
packages/cli-v3/src/cli/index.tsapps/webapp/app/utils/pathBuilder.tsapps/webapp/app/utils/deeplinkPages.test.tspackages/cli-v3/src/apiClient.tspackages/cli-v3/src/commands/projects/list.tspackages/cli-v3/src/commands/projects/index.tsapps/webapp/app/routes/api.v1.projects.runtimes.tsapps/webapp/app/services/projectRuntimeUpdates.server.tspackages/core/src/v3/schemas/api-type.test.tsapps/webapp/app/routes/[_].$.tspackages/core/src/v3/schemas/api.tsapps/webapp/app/utils/deeplinkPages.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/app/utils/pathBuilder.tsapps/webapp/app/components/navigation/OrganizationSettingsSideMenu.tsxapps/webapp/app/utils/deeplinkPages.test.tsapps/webapp/app/routes/api.v1.projects.runtimes.tsapps/webapp/app/services/projectRuntimeUpdates.server.tsapps/webapp/app/routes/_app.orgs.$organizationSlug.settings.runtime-updates/route.tsxapps/webapp/app/routes/[_].$.tsapps/webapp/app/utils/deeplinkPages.ts
📚 Learning: 2026-06-25T18:21:51.905Z
Learnt from: carderne
Repo: triggerdotdev/trigger.dev PR: 4039
File: apps/webapp/app/routes/invite-revoke.tsx:0-0
Timestamp: 2026-06-25T18:21:51.905Z
Learning: During the Zod v4 migration in the triggerdotdev/trigger.dev webapp, ensure any imports from `conform-to/zod` use the Zod-4 subpath: `conform-to/zod/v4` (e.g., `import { parseWithZod } from "conform-to/zod/v4"`). Do not import from the package root `conform-to/zod`, because it is the Zod 3 implementation and may load Zod-3-only symbols (e.g., `ZodBranded`, `ZodEffects`), which can throw at module load (notably with `zod4.4.3`). This should be enforced across `apps/webapp/**/*` where helpers like `parseWithZod` and `conformZodMessage` are used.
Applied to files:
apps/webapp/app/utils/pathBuilder.tsapps/webapp/app/components/navigation/OrganizationSettingsSideMenu.tsxapps/webapp/app/utils/deeplinkPages.test.tsapps/webapp/app/routes/api.v1.projects.runtimes.tsapps/webapp/app/services/projectRuntimeUpdates.server.tsapps/webapp/app/routes/_app.orgs.$organizationSlug.settings.runtime-updates/route.tsxapps/webapp/app/routes/[_].$.tsapps/webapp/app/utils/deeplinkPages.ts
📚 Learning: 2026-07-03T17:10:21.498Z
Learnt from: 0ski
Repo: triggerdotdev/trigger.dev PR: 4148
File: apps/webapp/app/models/orgMember.server.ts:149-168
Timestamp: 2026-07-03T17:10:21.498Z
Learning: In triggerdotdev/trigger.dev, `User.email` (Prisma schema: `internal-packages/database/prisma/schema.prisma`) currently does NOT use `citext` and does NOT have a `lower(email)` functional unique index. Therefore, do not introduce Prisma queries like `where: { email: { equals: <value>, mode: "insensitive" } }` (or any case-insensitive lookup) against `User.email`, because it can force sequential scans of the `users` table under load. During review, ensure email is normalized (e.g., lowercased/trimmed) before both writes and subsequent lookups, and if true case-insensitive behavior/uniqueness is required, implement it via a separate app-wide migration (e.g., switch to `citext` and/or add a functional unique index with backfill) rather than bolting it onto individual feature PRs.
Applied to files:
apps/webapp/app/utils/pathBuilder.tsapps/webapp/app/components/navigation/OrganizationSettingsSideMenu.tsxapps/webapp/app/utils/deeplinkPages.test.tsapps/webapp/app/routes/api.v1.projects.runtimes.tsapps/webapp/app/services/projectRuntimeUpdates.server.tsapps/webapp/app/routes/_app.orgs.$organizationSlug.settings.runtime-updates/route.tsxapps/webapp/app/routes/[_].$.tsapps/webapp/app/utils/deeplinkPages.ts
📚 Learning: 2026-02-11T16:37:32.429Z
Learnt from: matt-aitken
Repo: triggerdotdev/trigger.dev PR: 3019
File: apps/webapp/app/components/primitives/charts/Card.tsx:26-30
Timestamp: 2026-02-11T16:37:32.429Z
Learning: In projects using react-grid-layout, avoid relying on drag-handle class to imply draggability. Ensure drag-handle elements only affect dragging when the parent grid item is configured draggable in the layout; conditionally apply cursor styles based on the draggable prop. This improves correctness and accessibility.
Applied to files:
apps/webapp/app/components/navigation/OrganizationSettingsSideMenu.tsxapps/webapp/app/routes/_app.orgs.$organizationSlug.settings.runtime-updates/route.tsx
📚 Learning: 2026-07-28T21:57:20.061Z
Learnt from: samejr
Repo: triggerdotdev/trigger.dev PR: 4411
File: apps/webapp/app/routes/_app.orgs.$organizationSlug.settings.team/route.tsx:818-843
Timestamp: 2026-07-28T21:57:20.061Z
Learning: When using Radix UI `DialogClose` with `asChild` (e.g., Trigger.dev dashboard components), note that it injects `type="button"` into its child via `Slot`. If the child is a local `Button` that forwards its `type` prop to the native `<button>`, then placing it inside a `<form>` will *not* submit unless you explicitly set `type="submit"` (or otherwise override the injected type / wire up submission behavior). Review form actions to ensure the intended submit vs non-submit behavior is preserved.
Applied to files:
apps/webapp/app/components/navigation/OrganizationSettingsSideMenu.tsxapps/webapp/app/routes/_app.orgs.$organizationSlug.settings.runtime-updates/route.tsx
📚 Learning: 2026-04-16T14:21:15.229Z
Learnt from: ericallam
Repo: triggerdotdev/trigger.dev PR: 3368
File: apps/webapp/app/components/logs/LogsTaskFilter.tsx:135-163
Timestamp: 2026-04-16T14:21:15.229Z
Learning: When rendering lists of task registry items in apps/webapp (e.g., <SelectItem /> rows) and using `key={item.slug}`, do not flag it as potentially non-unique. In trigger.dev’s `TaskIdentifier` table, the DB constraint `@unique([runtimeEnvironmentId, slug])` guarantees `slug` is unique within a given runtime environment, so `item.slug` is safe as the React key as long as the list is derived from that registry/constraint (and not from a legacy query that could produce duplicate slugs).
Applied to files:
apps/webapp/app/components/navigation/OrganizationSettingsSideMenu.tsx
📚 Learning: 2026-05-08T21:00:20.973Z
Learnt from: samejr
Repo: triggerdotdev/trigger.dev PR: 3538
File: apps/webapp/app/components/primitives/Resizable.tsx:60-78
Timestamp: 2026-05-08T21:00:20.973Z
Learning: In the triggerdotdev/trigger.dev codebase, treat Zod as a boundary validation tool (API handlers, request/response validation, and storage/DB read/write validation), not as inline render-time validation inside React components/primitive UI code. For render-time guards, prefer small manual type-narrowing checks (e.g., a short predicate like ~10–20 lines) over importing Zod into UI primitives, to avoid per-render schema-parse overhead and unnecessary abstraction. Use the manual guard approach unless you truly need schema validation at a boundary; only then introduce Zod.
Applied to files:
apps/webapp/app/components/navigation/OrganizationSettingsSideMenu.tsxapps/webapp/app/routes/_app.orgs.$organizationSlug.settings.runtime-updates/route.tsx
📚 Learning: 2026-06-25T18:21:55.847Z
Learnt from: carderne
Repo: triggerdotdev/trigger.dev PR: 4039
File: apps/webapp/app/routes/invite-resend.tsx:0-0
Timestamp: 2026-06-25T18:21:55.847Z
Learning: In the triggerdotdev/trigger.dev Zod 4 migration, avoid importing from the root package `conform-to/zod` in webapp code. It can resolve to the Zod 3 build and may crash at module load under Zod 4. When reviewing TypeScript/TSX files in `apps/webapp`, prefer importing from the Zod 4 subpath `conform-to/zod/v4` for Zod 4-compatible schemas/types.
Applied to files:
apps/webapp/app/components/navigation/OrganizationSettingsSideMenu.tsxapps/webapp/app/routes/_app.orgs.$organizationSlug.settings.runtime-updates/route.tsx
📚 Learning: 2026-06-25T18:21:54.729Z
Learnt from: carderne
Repo: triggerdotdev/trigger.dev PR: 4039
File: apps/webapp/app/routes/confirm-basic-details.tsx:0-0
Timestamp: 2026-06-25T18:21:54.729Z
Learning: For Remix + TypeScript files that use Conform v1 (conform-to/react) and its getInputProps helper, when you intend to suppress the helper-provided default value for non-checkbox/non-radio inputs (e.g., hidden inputs managed via an explicit value prop), use the Conform v1 option key `value: false`. Do not recommend `defaultValue: false` here, because `defaultValue` is not a valid option key for these input types in Conform v1 typings.
Applied to files:
apps/webapp/app/components/navigation/OrganizationSettingsSideMenu.tsxapps/webapp/app/routes/_app.orgs.$organizationSlug.settings.runtime-updates/route.tsx
📚 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/app/utils/deeplinkPages.test.tspackages/core/src/v3/schemas/api-type.test.ts
📚 Learning: 2026-06-16T09:19:47.637Z
Learnt from: d-cs
Repo: triggerdotdev/trigger.dev PR: 3960
File: apps/webapp/test/prismaInfrastructureErrorCapture.test.ts:0-0
Timestamp: 2026-06-16T09:19:47.637Z
Learning: In this repo’s Vitest setup, `vitest.config.ts` uses `globals: true`, so identifiers like `vi`, `describe`, `it`, and `expect` are available as globals in Vitest test files. During code review, do not flag missing `vi`/`describe`/`it`/`expect` imports as a runtime error or correctness issue when they’re used in `*.test.ts/tsx` or `*.spec.ts/tsx` files. Explicit imports are still preferred for consistency, but they’re not required for runtime behavior.
Applied to files:
apps/webapp/app/utils/deeplinkPages.test.tspackages/core/src/v3/schemas/api-type.test.ts
📚 Learning: 2026-07-15T18:37:08.044Z
Learnt from: CR
Repo: triggerdotdev/trigger.dev PR: 0
File: apps/webapp/CLAUDE.md:0-0
Timestamp: 2026-07-15T18:37:08.044Z
Learning: Applies to apps/webapp/app/routes/**/*.ts : PAT-authenticated API routes must resolve their target organization or project within the caller's membership scope, using a membership filter or a helper such as `findProjectByRef` or `resolveOrganizationForApiUser`; RBAC authorization alone is insufficient.
Applied to files:
apps/webapp/app/routes/api.v1.projects.runtimes.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/projectRuntimeUpdates.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/projectRuntimeUpdates.server.ts
📚 Learning: 2025-11-27T16:26:37.432Z
Learnt from: CR
Repo: triggerdotdev/trigger.dev PR: 0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-11-27T16:26:37.432Z
Learning: Applies to **/*.{test,spec}.{ts,tsx} : Use vitest for all tests in the Trigger.dev repository
Applied to files:
packages/core/src/v3/schemas/api-type.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 this repo’s trigger.dev codebase, the “never mock — use testcontainers” guideline should only be applied to integration tests that talk to real external services (e.g., Redis, Postgres, S2). For unit tests that validate in-memory logic (e.g., deduplication/cache behavior in StandardRealtimeStreamsManager and similar module-boundary call counting), it is allowed to use Vitest mocks like `vi.fn()` and to stub/mock `ApiClient` objects to count calls or simulate in-process collaborators. Do not flag `vi.fn()`-based mocks as policy violations in these unit-test scenarios; reserve the rule for true external-service integration tests.
Applied to files:
packages/core/src/v3/schemas/api-type.test.ts
📚 Learning: 2026-02-03T18:27:40.429Z
Learnt from: 0ski
Repo: triggerdotdev/trigger.dev PR: 2994
File: apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.environment-variables/route.tsx:553-555
Timestamp: 2026-02-03T18:27:40.429Z
Learning: In apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.environment-variables/route.tsx, the menu buttons (e.g., Edit with PencilSquareIcon) in the TableCellMenu are intentionally icon-only with no text labels as a compact UI pattern. This is a deliberate design choice for this route; preserve the icon-only behavior for consistency in this file.
Applied to files:
apps/webapp/app/routes/_app.orgs.$organizationSlug.settings.runtime-updates/route.tsx
📚 Learning: 2026-07-22T11:16:06.546Z
Learnt from: samejr
Repo: triggerdotdev/trigger.dev PR: 4332
File: apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.regions/route.tsx:166-168
Timestamp: 2026-07-22T11:16:06.546Z
Learning: In the Trigger.dev web app, copy-interaction accessibility (keyboard and touch behavior for the copy affordance) is owned by the shared `CopyableText` `icon-right` primitive. When reviewing route-level code (e.g., admin debug panels and runs tables) that intentionally reuses this pattern, avoid suggesting divergent call-site-only accessibility fixes; instead, route any accessibility changes back to a holistic update of the `CopyableText` `icon-right` implementation so all reuse sites benefit consistently.
Applied to files:
apps/webapp/app/routes/_app.orgs.$organizationSlug.settings.runtime-updates/route.tsx
📚 Learning: 2026-04-02T19:18:26.255Z
Learnt from: samejr
Repo: triggerdotdev/trigger.dev PR: 3319
File: apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.bulk-actions/route.tsx:179-189
Timestamp: 2026-04-02T19:18:26.255Z
Learning: In this repo’s route components that render the Inspector `ResizablePanelGroup` panels, it’s acceptable to pass `collapsed={!isShowingInspector}` together with a no-op `onCollapseChange={() => {}}` when panel visibility is intentionally controlled only by route parameters (e.g., `*Param` search/route params) rather than user drag/collapse interactions. Do not flag an empty/no-op `onCollapseChange` as “missing wiring” in these cases; only flag it when collapse state is expected to change based on user interaction.
Applied to files:
apps/webapp/app/routes/_app.orgs.$organizationSlug.settings.runtime-updates/route.tsx
📚 Learning: 2026-05-12T21:04:00.184Z
Learnt from: ericallam
Repo: triggerdotdev/trigger.dev PR: 3542
File: apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.sessions._index/route.tsx:40-42
Timestamp: 2026-05-12T21:04:00.184Z
Learning: In triggerdotdev/trigger.dev route loader implementations (Remix `route.tsx` files under `apps/webapp/app/routes/**`), follow the existing convention for missing/unauthorized environment lookups: when `findEnvironmentBySlug` (or the equivalent env resolver) returns a falsy value, handle it by throwing `new Error("Environment not found")` rather than returning a `404` `Response` (i.e., do not flag this as “missing 404 response”). Changing the error-to-404 convention is a cross-cutting refactor and should be left out of individual PRs unless the PR explicitly addresses that broader migration.
Applied to files:
apps/webapp/app/routes/_app.orgs.$organizationSlug.settings.runtime-updates/route.tsx
🔇 Additional comments (15)
packages/core/src/v3/schemas/api.ts (1)
62-79: LGTM!Also applies to: 81-108
packages/core/src/v3/schemas/api-type.test.ts (1)
2-23: LGTM!apps/webapp/app/services/projectRuntimeUpdates.server.ts (1)
1-84: LGTM!apps/webapp/app/routes/api.v1.projects.runtimes.ts (1)
6-17: LGTM!packages/cli-v3/src/apiClient.ts (1)
32-32: LGTM!Also applies to: 219-230
packages/cli-v3/src/commands/projects/index.ts (1)
1-10: LGTM!packages/cli-v3/src/commands/projects/list.ts (1)
1-38: LGTM!Also applies to: 40-47, 49-95
packages/cli-v3/src/cli/index.ts (1)
11-11: LGTM!Also applies to: 45-45
.changeset/list-project-runtime-updates.md (1)
1-6: LGTM!apps/webapp/app/utils/pathBuilder.ts (1)
173-175: LGTM!apps/webapp/app/utils/deeplinkPages.ts (1)
41-43: LGTM!Also applies to: 68-93
apps/webapp/app/utils/deeplinkPages.test.ts (1)
11-13: LGTM!Also applies to: 166-173
apps/webapp/app/routes/_app.orgs.$organizationSlug.settings.runtime-updates/route.tsx (1)
58-123: 🎯 Functional CorrectnessVisually verify the new dashboard page.
Verify side-menu navigation, empty state, populated table, deployment links, screenshots, interactions, and browser console messages in the running Remix app. As per coding guidelines: “For dashboard changes, visually verify the running Remix app with Chrome DevTools MCP, using snapshots, screenshots, interaction, and console-message checks as appropriate.”
Source: Coding guidelines
apps/webapp/app/components/navigation/OrganizationSettingsSideMenu.tsx (1)
1-1: LGTM!Also applies to: 19-19, 131-138
apps/webapp/app/routes/[_].$.ts (1)
6-16: LGTM!Also applies to: 24-43, 60-63
| withLabel | ||
| /> | ||
| </TableCell> | ||
| <TableCell>{deployment.deployedAt?.toLocaleString() ?? "-"}</TableCell> |
Contributor
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🌐 Web query:
Does JavaScript Date.prototype.toLocaleString use the host environment's default locale and time zone when no locale or timeZone option is provided?
💡 Result:
Yes, JavaScript Date.prototype.toLocaleString uses the host environment's default locale and time zone when no locale or time zone options are provided [1][2][3]. In modern JavaScript environments that support the ECMAScript Internationalization API (ECMA-402), calling Date.prototype.toLocaleString without arguments delegates to the Intl.DateTimeFormat API [1][3]. In this default state, it formats the date string based on the runtime's default locale (which is typically determined by the operating system or browser settings) and the runtime's default time zone [1][4]. For implementations that lack support for the internationalization API (which is rare in contemporary environments), the behavior of Date.prototype.toLocaleString is implementation-dependent, though it generally still defaults to the system's local settings [1][3][5].
Citations:
- 1: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toLocaleString
- 2: https://devdoc.net/web/developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toLocaleString.html
- 3: https://github.com/mdn/content/blob/main/files/en-us/web/javascript/reference/global_objects/date/tolocalestring/index.md
- 4: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/DateTimeFormat
- 5: https://www.typeerror.org/docs/javascript/global_objects/date/tolocalestring
🏁 Script executed:
#!/bin/bash
set -eu
file="$(git ls-files | rg '^apps/webapp/app/routes/_app\.orgs\..*settings\.runtime-updates/route\.tsx$' | head -n 1)"
printf '%s\n' "FILE=$file"
[ -n "$file" ]
sed -n '1,180p' "$file"
printf '%s\n' '--- date-formatting usages ---'
rg -n -C 3 'deployedAt|toLocaleString|runtime-updates' apps/webapp/app packages internal-packages 2>/dev/null | head -n 240
printf '%s\n' '--- route/runtime configuration references ---'
rg -n -C 3 'dashboardLoader|deployedAt|NODE_RUNTIME_UPDATE_MAJOR' apps/webapp/app packages internal-packages 2>/dev/null | head -n 320Repository: triggerdotdev/trigger.dev
Length of output: 50381
🏁 Script executed:
#!/bin/bash
set -eu
node - <<'JS'
const instant = new Date("2026-01-15T12:34:56.000Z");
console.log("default:", instant.toLocaleString());
console.log("resolved:", new Intl.DateTimeFormat().resolvedOptions());
JS
TZ=UTC LANG=en-US node - <<'JS'
console.log("server-like:", new Date("2026-01-15T12:34:56.000Z").toLocaleString());
JS
TZ=America/Los_Angeles LANG=en-US node - <<'JS'
console.log("browser-like:", new Date("2026-01-15T12:34:56.000Z").toLocaleString());
JS
printf '%s\n' '--- typed loader/date handling ---'
rg -n -C 4 'useTypedLoaderData|typedjson|Date\.|deployedAt' \
apps/webapp/app/routes/_app.orgs.\$organizationSlug.settings.runtime-updates/route.tsx \
apps/webapp/app/services/routeBuilders \
package.json apps/webapp/package.json 2>/dev/null | head -n 220Repository: triggerdotdev/trigger.dev
Length of output: 5144
Use a hydration-stable deployed-time formatter.
toLocaleString() uses each runtime’s default locale and time zone. Different server and browser defaults can produce different text during hydration. Pass an explicit locale and time zone, or defer user-local formatting until after hydration.
carderne
force-pushed
the
feat/node-runtime-updates
branch
3 times, most recently
from
August 18, 2026 19:38
0d0522e to
c6b9c43
Compare
carderne
force-pushed
the
feat/node-runtime-updates
branch
from
August 18, 2026 19:39
c6b9c43 to
1adfb2c
Compare
@trigger.dev/build
trigger.dev
@trigger.dev/core
@trigger.dev/python
@trigger.dev/react-hooks
@trigger.dev/redis-worker
@trigger.dev/rsc
@trigger.dev/schema-to-json
@trigger.dev/sdk
commit: |
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
Users can now inspect every current Production project runtime with
trigger projects list, or limit the result to Node.js 21 deployments with--needs-update.The organization settings page identifies Production projects that need an update and is available through
/_/runtime-updates.