feat(deployments): show local build hint during depot outages

[myftija]

Changes in this PR:

• added a API endpoint to query the depot's status page for ongoing incidents
• added a hint about the --force-local-build flag to the deployment command
  that is only shown during depot outages.

[changeset-bot]

🦋 Changeset detected

Latest commit: d69838e

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 23 packages

Name	Type
trigger.dev	Patch
@trigger.dev/core	Patch
d3-chat	Patch
references-d3-openai-agents	Patch
references-nextjs-realtime	Patch
@trigger.dev/build	Patch
@trigger.dev/python	Patch
@trigger.dev/redis-worker	Patch
@trigger.dev/schema-to-json	Patch
@trigger.dev/sdk	Patch
@internal/cache	Patch
@internal/clickhouse	Patch
@internal/redis	Patch
@internal/replication	Patch
@internal/run-engine	Patch
@internal/schedule-engine	Patch
@internal/testcontainers	Patch
@internal/tracing	Patch
@internal/zod-worker	Patch
@trigger.dev/react-hooks	Patch
@trigger.dev/rsc	Patch
@trigger.dev/database	Patch
@trigger.dev/otlp-importer	Patch

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

[coderabbitai]

Walkthrough

Adds a remote build provider status endpoint and wiring for CLI hints: a new Remix route reports Depot status (operational, degraded, unknown) with timeout and validation; a Zod schema and TypeScript type for the response were added; the CLI API client gains getRemoteBuildProviderStatus() and sends the CLI version header; deploy/build commands surface a visible --force-local-build option and show a post-build hint (prettyWarning) when remote provider is degraded; a changeset documents the version bumps and the new hint.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25–30 minutes

• Review the new Remix route (api.v1.remote-build-provider-status.ts) for timeout, error handling, neverthrow usage, and schema validation.
• Verify the new Zod schema and exported type in packages/core/src/v3/schemas/api.ts.
• Check packages/cli-v3/src/apiClient.ts for correct header usage and response typing.
• Inspect deploy/build flow changes in packages/cli-v3/src/commands/deploy.ts, especially the conditions that surface the prettyWarning hint and the visibility change for --force-local-build.

Pre-merge checks and finishing touches

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The pull request description is largely incomplete and does not follow the required template structure. The provided description consists of only a brief informal bullet list of changes, but it is missing several required sections: the "Closes #" reference, the entire ✅ Checklist section, the Testing section describing how the changes were validated, the Changelog section with proper formatting, and the Screenshots section. While the description does touch on what was changed (relevant to the changeset objectives), it lacks the structure and completeness required by the repository's template.	The PR description should be updated to follow the repository's template. This includes adding a "Closes #" reference at the top, completing the checklist to confirm adherence to the contributing guide and testing, adding a Testing section with specific steps taken to validate the changes, and properly formatting the changelog entry. These additions will provide reviewers with the necessary context and verification that the contributing guidelines were followed.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The pull request title "feat(deployments): show local build hint during depot outages" accurately captures the main user-facing change introduced by this PR. The title follows the conventional commit format (feat(deployments):) and is concise and specific. It clearly communicates that the feature is about displaying a local build hint during depot outages, which aligns with the core objective of the changeset. While the title doesn't mention the supporting API endpoint added to query Depot status, that's an implementation detail rather than the primary user-facing change.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch local-build-hint

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4264bdf and 28ab123.

📒 Files selected for processing (5)

• .changeset/nice-pillows-hide.md (1 hunks)
• apps/webapp/app/routes/api.v1.remote-build-provider-status.ts (1 hunks)
• packages/cli-v3/src/apiClient.ts (3 hunks)
• packages/cli-v3/src/commands/deploy.ts (3 hunks)
• packages/core/src/v3/schemas/api.ts (1 hunks)

🧰 Additional context used

📓 Path-based instructions (5)

**/*.{ts,tsx}

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

**/*.{ts,tsx}: Always prefer using isomorphic code like fetch, ReadableStream, etc. instead of Node.js specific code
For TypeScript, we usually use types over interfaces
Avoid enums
No default exports, use function declarations

Files:

• packages/core/src/v3/schemas/api.ts
• packages/cli-v3/src/apiClient.ts
• apps/webapp/app/routes/api.v1.remote-build-provider-status.ts
• packages/cli-v3/src/commands/deploy.ts

{packages/core,apps/webapp}/**/*.{ts,tsx}

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

We use zod a lot in packages/core and in the webapp

Files:

• packages/core/src/v3/schemas/api.ts
• apps/webapp/app/routes/api.v1.remote-build-provider-status.ts

apps/webapp/**/*.{ts,tsx}

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

When importing from @trigger.dev/core in the webapp, never import the root package path; always use one of the documented subpath exports from @trigger.dev/core’s package.json

Files:

• apps/webapp/app/routes/api.v1.remote-build-provider-status.ts

{apps/webapp/app/**/*.server.{ts,tsx},apps/webapp/app/routes/**/*.ts}

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

Access environment variables only via the env export from app/env.server.ts; do not reference process.env directly

Files:

• apps/webapp/app/routes/api.v1.remote-build-provider-status.ts

apps/webapp/app/**/*.ts

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

Modules intended for test consumption under apps/webapp/app/**/*.ts must not read environment variables; accept configuration via options instead

Files:

• apps/webapp/app/routes/api.v1.remote-build-provider-status.ts

🧠 Learnings (3)

📚 Learning: 2025-08-18T10:07:17.368Z

Learnt from: CR
PR: triggerdotdev/trigger.dev#0
File: .cursor/rules/writing-tasks.mdc:0-0
Timestamp: 2025-08-18T10:07:17.368Z
Learning: Applies to **/trigger/**/*.{ts,tsx,js,jsx} : Import Trigger.dev APIs from "trigger.dev/sdk/v3" when writing tasks or related utilities

Applied to files:

• packages/cli-v3/src/apiClient.ts

📚 Learning: 2025-06-06T23:55:01.933Z

Learnt from: nicktrn
PR: triggerdotdev/trigger.dev#2155
File: hosting/docker/.env.example:4-7
Timestamp: 2025-06-06T23:55:01.933Z
Learning: In the trigger.dev project, .env.example files should contain actual example secret values rather than placeholders, as these help users understand the expected format. The files include clear warnings about not using these defaults in production and instructions for generating proper secrets.

Applied to files:

• .changeset/nice-pillows-hide.md

📚 Learning: 2025-08-18T10:07:17.368Z

Learnt from: CR
PR: triggerdotdev/trigger.dev#0
File: .cursor/rules/writing-tasks.mdc:0-0
Timestamp: 2025-08-18T10:07:17.368Z
Learning: Applies to trigger.config.ts : Declare build options and extensions (external, jsx, conditions, extensions) via the build block in trigger.config.ts rather than custom scripts

Applied to files:

• .changeset/nice-pillows-hide.md

🧬 Code graph analysis (3)

packages/cli-v3/src/apiClient.ts (2)

packages/core/src/v3/apiClient/core.ts (1)

• wrapZodFetch (727-767)

packages/core/src/v3/schemas/api.ts (2)

• RemoteBuildProviderStatusResponseBody (442-445)
• RemoteBuildProviderStatusResponseBody (447-449)

apps/webapp/app/routes/api.v1.remote-build-provider-status.ts (1)

packages/core/src/v3/schemas/api.ts (2)

• RemoteBuildProviderStatusResponseBody (442-445)
• RemoteBuildProviderStatusResponseBody (447-449)

packages/cli-v3/src/commands/deploy.ts (1)

packages/cli-v3/src/utilities/cliOutput.ts (1)

• prettyWarning (96-117)

⏰ 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). (23)

• GitHub Check: units / internal / 🧪 Unit Tests: Internal (3, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (7, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (4, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (8, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (6, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (5, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (2, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (1, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (1, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (5, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (6, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (4, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (8, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (7, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (3, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (2, 8)
• GitHub Check: units / packages / 🧪 Unit Tests: Packages (1, 1)
• GitHub Check: e2e / 🧪 CLI v3 tests (ubuntu-latest - pnpm)
• GitHub Check: e2e / 🧪 CLI v3 tests (windows-latest - npm)
• GitHub Check: e2e / 🧪 CLI v3 tests (windows-latest - pnpm)
• GitHub Check: e2e / 🧪 CLI v3 tests (ubuntu-latest - npm)
• GitHub Check: typecheck / typecheck
• GitHub Check: Analyze (javascript-typescript)

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 28ab123 and d69838e.

📒 Files selected for processing (1)

• apps/webapp/app/routes/api.v1.remote-build-provider-status.ts (1 hunks)

🧰 Additional context used

📓 Path-based instructions (5)

**/*.{ts,tsx}

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

**/*.{ts,tsx}: Always prefer using isomorphic code like fetch, ReadableStream, etc. instead of Node.js specific code
For TypeScript, we usually use types over interfaces
Avoid enums
No default exports, use function declarations

Files:

• apps/webapp/app/routes/api.v1.remote-build-provider-status.ts

{packages/core,apps/webapp}/**/*.{ts,tsx}

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

We use zod a lot in packages/core and in the webapp

Files:

• apps/webapp/app/routes/api.v1.remote-build-provider-status.ts

apps/webapp/**/*.{ts,tsx}

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

When importing from @trigger.dev/core in the webapp, never import the root package path; always use one of the documented subpath exports from @trigger.dev/core’s package.json

Files:

• apps/webapp/app/routes/api.v1.remote-build-provider-status.ts

{apps/webapp/app/**/*.server.{ts,tsx},apps/webapp/app/routes/**/*.ts}

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

Access environment variables only via the env export from app/env.server.ts; do not reference process.env directly

Files:

• apps/webapp/app/routes/api.v1.remote-build-provider-status.ts

apps/webapp/app/**/*.ts

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

Modules intended for test consumption under apps/webapp/app/**/*.ts must not read environment variables; accept configuration via options instead

Files:

• apps/webapp/app/routes/api.v1.remote-build-provider-status.ts

🧠 Learnings (5)

📚 Learning: 2025-08-29T10:06:49.293Z

Learnt from: CR
PR: triggerdotdev/trigger.dev#0
File: .cursor/rules/webapp.mdc:0-0
Timestamp: 2025-08-29T10:06:49.293Z
Learning: Applies to apps/webapp/**/*.{ts,tsx} : When importing from trigger.dev/core in the webapp, never import the root package path; always use one of the documented subpath exports from trigger.dev/core’s package.json

Applied to files:

• apps/webapp/app/routes/api.v1.remote-build-provider-status.ts

📚 Learning: 2025-08-18T10:07:17.368Z

Learnt from: CR
PR: triggerdotdev/trigger.dev#0
File: .cursor/rules/writing-tasks.mdc:0-0
Timestamp: 2025-08-18T10:07:17.368Z
Learning: Applies to **/trigger/**/*.{ts,tsx,js,jsx} : Import Trigger.dev APIs from "trigger.dev/sdk/v3" when writing tasks or related utilities

Applied to files:

• apps/webapp/app/routes/api.v1.remote-build-provider-status.ts

📚 Learning: 2025-07-18T17:49:24.468Z

Learnt from: CR
PR: triggerdotdev/trigger.dev#0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-07-18T17:49:24.468Z
Learning: Applies to {packages/core,apps/webapp}/**/*.{ts,tsx} : We use zod a lot in packages/core and in the webapp

Applied to files:

• apps/webapp/app/routes/api.v1.remote-build-provider-status.ts

📚 Learning: 2025-08-29T10:06:49.293Z

Learnt from: CR
PR: triggerdotdev/trigger.dev#0
File: .cursor/rules/webapp.mdc:0-0
Timestamp: 2025-08-29T10:06:49.293Z
Learning: Applies to {apps/webapp/**/__tests__/**/*.{ts,tsx},apps/webapp/**/*.{test,spec}.{ts,tsx}} : Tests should only import classes/functions from files under apps/webapp/app/**/*.ts

Applied to files:

• apps/webapp/app/routes/api.v1.remote-build-provider-status.ts

📚 Learning: 2025-08-29T10:06:49.293Z

Learnt from: CR
PR: triggerdotdev/trigger.dev#0
File: .cursor/rules/webapp.mdc:0-0
Timestamp: 2025-08-29T10:06:49.293Z
Learning: Applies to {apps/webapp/app/**/*.server.{ts,tsx},apps/webapp/app/routes/**/*.ts} : Access environment variables only via the env export from app/env.server.ts; do not reference process.env directly

Applied to files:

• apps/webapp/app/routes/api.v1.remote-build-provider-status.ts

🧬 Code graph analysis (1)

apps/webapp/app/routes/api.v1.remote-build-provider-status.ts (1)

packages/core/src/v3/schemas/api.ts (2)

• RemoteBuildProviderStatusResponseBody (442-445)
• RemoteBuildProviderStatusResponseBody (447-449)

⏰ 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). (19)

• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (8, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (6, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (4, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (2, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (5, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (3, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (7, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (1, 8)
• GitHub Check: typecheck / typecheck
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (6, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (4, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (3, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (2, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (1, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (5, 8)
• GitHub Check: e2e / 🧪 CLI v3 tests (ubuntu-latest - npm)
• GitHub Check: e2e / 🧪 CLI v3 tests (windows-latest - pnpm)
• GitHub Check: e2e / 🧪 CLI v3 tests (windows-latest - npm)
• GitHub Check: units / packages / 🧪 Unit Tests: Packages (1, 1)