Conversation
|
WalkthroughA new MDX documentation page is added to document the private beta compute runtime feature based on microVMs. The page specifies that the feature is private beta for staging use only, details access enablement through the dashboard Regions page for us-east-1-next, and provides TypeScript examples for configuring the region per-trigger via TriggerOptions or as a project-wide default. The page also documents cold-start behavior and directs users to report issues via Slack with run IDs. Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 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. Review rate limit: 7/8 reviews remaining, refill in 7 minutes and 30 seconds.Comment |
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
docs/compute-private-beta.mdx (1)
17-20: Use<Steps>for the access flow to improve scanability.This section describes a sequence; rendering it as
<Steps>/<Step>will make onboarding instructions clearer.As per coding guidelines, “Use Mintlify components for structured content: ...
<Steps>/<Step>...”.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/compute-private-beta.mdx` around lines 17 - 20, Replace the plain paragraph under the "Getting access" heading with a Mintlify Steps flow: wrap the sequence in a <Steps> component and create individual <Step> entries for each step (e.g., "Request access", "Check Regions page", "Contact us"), moving the sentence about the region appearing on the Regions page into the appropriate <Step> and keep the Slack instruction as the final <Step>. Ensure you use <Steps> and <Step> tags (not plain text) and preserve the original wording/meaning while splitting it into discrete steps for scanability.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/compute-private-beta.mdx`:
- Around line 29-43: The examples reference undefined variables and a local
import; make them self-contained and use the SDK import: replace the local
import of yourTask with import { task } from "@trigger.dev/sdk", define export
const yourTask = task({ id: "your-task", run: async (payload: { message: string
}) => { console.log(payload.message); } }); then call yourTask.trigger with a
concrete payload object (e.g., { message: "hello" }) in both snippets and keep
the defaultRegion logic (const defaultRegion = process.env.USE_COMPUTE_BETA ===
"1" ? "us-east-1-next" : undefined) when passing the region option.
---
Nitpick comments:
In `@docs/compute-private-beta.mdx`:
- Around line 17-20: Replace the plain paragraph under the "Getting access"
heading with a Mintlify Steps flow: wrap the sequence in a <Steps> component and
create individual <Step> entries for each step (e.g., "Request access", "Check
Regions page", "Contact us"), moving the sentence about the region appearing on
the Regions page into the appropriate <Step> and keep the Slack instruction as
the final <Step>. Ensure you use <Steps> and <Step> tags (not plain text) and
preserve the original wording/meaning while splitting it into discrete steps for
scanability.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: 1d6e1cca-97e1-4d49-adc3-120324cc7631
📒 Files selected for processing (1)
docs/compute-private-beta.mdx
📜 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). (3)
- GitHub Check: Analyze (actions)
- GitHub Check: Analyze (python)
- GitHub Check: Analyze (javascript-typescript)
🧰 Additional context used
📓 Path-based instructions (1)
docs/**/*.mdx
📄 CodeRabbit inference engine (docs/CLAUDE.md)
docs/**/*.mdx: MDX documentation pages must include frontmatter with title (required), description (required), and sidebarTitle (optional) in YAML format
Use Mintlify components for structured content: , , , , , , /, /
Always import from@trigger.dev/sdkin code examples (never from@trigger.dev/sdk/v3)
Code examples must be complete and runnable where possible
Use language tags in code fences:typescript,bash,json
Files:
docs/compute-private-beta.mdx
🧠 Learnings (3)
📓 Common learnings
Learnt from: CR
Repo: triggerdotdev/trigger.dev PR: 0
File: .cursor/rules/writing-tasks.mdc:0-0
Timestamp: 2026-03-25T15:29:25.889Z
Learning: Applies to **/trigger/**/*.{ts,tsx,js,jsx} : Specify CPU/RAM requirements using the `machine` option with a `preset` value (e.g., 'large-1x')
📚 Learning: 2026-04-13T10:09:26.822Z
Learnt from: nicktrn
Repo: triggerdotdev/trigger.dev PR: 3366
File: apps/webapp/app/v3/services/worker/workerGroupService.server.ts:248-257
Timestamp: 2026-04-13T10:09:26.822Z
Learning: In `apps/webapp/app/v3/services/worker/workerGroupService.server.ts`, the MICROVM compute-access check in `getDefaultWorkerGroupForProject` intentionally applies only to the `regionOverride` path. When no `regionOverride` is given, `project.defaultWorkerGroup` and the global default worker group are always returned without compute-access gating — this is by design and should not be flagged as a bypass.
Applied to files:
docs/compute-private-beta.mdx
📚 Learning: 2026-03-10T12:44:14.176Z
Learnt from: nicktrn
Repo: triggerdotdev/trigger.dev PR: 3200
File: docs/config/config-file.mdx:353-368
Timestamp: 2026-03-10T12:44:14.176Z
Learning: In the trigger.dev repo, docs PRs are often companions to implementation PRs. When reviewing docs PRs (MDX files under docs/), check the PR description for any companion/related PR references and verify that the documented features exist in those companion PRs before flagging missing implementations. This ensures docs stay in sync with code changes across related PRs.
Applied to files:
docs/compute-private-beta.mdx
🔇 Additional comments (1)
docs/compute-private-beta.mdx (1)
1-11: Frontmatter and beta warning block look good.Required metadata is present, and the
<Warning>component is used appropriately for the private-beta safety callout.
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
2 participants
Compute page for private beta onboarding (not added to nav).