docs: refresh compute private beta page with may 1 updates#3502
docs: refresh compute private beta page with may 1 updates#3502matt-aitken merged 1 commit intomainfrom
Conversation
|
WalkthroughThis change updates the Compute private beta documentation to reflect current state as of May 1, 2026. It adds an announcement describing performance improvements including faster cold starts across all machine sizes and faster first runs after deploys. A new warning was added regarding the Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 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 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
docs/compute-private-beta.mdx (1)
37-51:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winSwitch these fences to
ts.These TypeScript examples use
typescriptas the fence language, but this repo’s docs convention ists/tsx. Updating both snippets keeps the MDX consistent and avoids renderer quirks. As per coding guidelines, usetsandtsx(nottypescript) as the code-fence language tags for TypeScript/TSX snippets.Suggested fix
-```typescript +```ts ... -```typescript +```ts🤖 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 37 - 51, Replace the code-fence language tag "typescript" with the repo-standard "ts" for both TypeScript snippets shown (the block starting with import { yourTask } from "./trigger/your-task"; and the block containing const defaultRegion = process.env.USE_COMPUTE_BETA === "1" ? "us-east-1-next" : undefined; followed by await yourTask.trigger(...)). Update both opening fences from ```typescript to ```ts so the MDX uses the correct ts/tsx convention and avoids renderer quirks.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Outside diff comments:
In `@docs/compute-private-beta.mdx`:
- Around line 37-51: Replace the code-fence language tag "typescript" with the
repo-standard "ts" for both TypeScript snippets shown (the block starting with
import { yourTask } from "./trigger/your-task"; and the block containing const
defaultRegion = process.env.USE_COMPUTE_BETA === "1" ? "us-east-1-next" :
undefined; followed by await yourTask.trigger(...)). Update both opening fences
from ```typescript to ```ts so the MDX uses the correct ts/tsx convention and
avoids renderer quirks.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: ca6ba3d6-e1ed-4669-80cd-f93b68fbc77b
📒 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 (javascript-typescript)
- GitHub Check: Analyze (python)
- GitHub Check: Analyze (actions)
🧰 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 (2)
📚 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
📚 Learning: 2026-04-30T20:30:29.458Z
Learnt from: ericallam
Repo: triggerdotdev/trigger.dev PR: 3226
File: docs/ai-chat/quick-start.mdx:13-13
Timestamp: 2026-04-30T20:30:29.458Z
Learning: In this repo’s documentation MDX files (`docs/**/*.mdx`), use `ts` and `tsx` (not `typescript`) as the code-fence language tags for TypeScript/TSX snippets. Do not flag `ts`/`tsx` code-fence language tags as incorrect in any docs MDX file, since this is the site-wide Mintlify-compatible convention.
Applied to files:
docs/compute-private-beta.mdx
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
2 participants
Updates the compute private beta page with the May 1 release entry, plus a deploy-time warning when
us-east-1-nextis the project default.The new What's new entry, verbatim:
May 1, 2026
microandsmall-1x- there's no longer a cold-start penalty for picking a smaller machine.large-1xandlarge-2xno longer hard-fail. They're still not recommended - cold-start performance trails the smaller presets and we're ironing out reliability issues.Follow-up to #3472 and #3479.