Uh oh!
There was an error while loading. Please reload this page.
[ci] Backport only stability fixes to stable, default to claude-opus-5 - #3092
Conversation
`stable` is a maintenance line: its users stayed behind for stability, so it should take fixes and nothing else. The previous prompt told the AI to lean toward backporting and explicitly listed "self-contained minor feature additions" as backport-worthy, which pulled feature work onto the branch whenever it cherry-picked cleanly. The decision prompt now recommends a backport only for defect, security, regression, test, build/release, and doc-correction changes, declines everything else (including small additive features and non-defect perf work), and breaks ties toward declining — `workflow_dispatch` remains the escape hatch for anything wrongly declined. Also bumps the default opencode model to `anthropic/claude-opus-5`. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
🦋 Changeset detectedLatest commit: 0d5185e The changes in this PR will be included in the next version bump. This PR includes changesets to release 0 packagesWhen changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types 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 |
🧪 E2E Test Results✅ All tests passed E2E Test SummarySummary
Details by Category✅ ▲ Vercel Production
✅ 💻 Local Development
✅ 📦 Local Production
✅ 🐘 Local Postgres
✅ 🪟 Windows
✅ 📋 Other
✅ vercel-multi-region
|
📊 Workflow Benchmarkscommit Backend:
ℹ️ Metric definitions & methodologyBest/P75/P90/P99 deltas compare against the most recent benchmark run on Metrics — TTFS: time to first step body (in-deployment start() → first step body, deployment clocks) · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (whole-run time outside step bodies, in-deployment anchored) · SL: stream latency (in-deployment write → read propagation, readAt - writtenAt) · SO: stream overhead (end-to-end write+consume time beyond the modelled generation window) Scenarios — step: one trivial no-op step, no stream; no hooks, so the run stays in turbo mode (in-process fast path) · stream: one streaming step; no hooks, so the run stays in turbo mode (in-process fast path) · hook + stream: registers a hook before one step, which exits turbo mode (dispatch path) · 1020 steps: 1020 trivial sequential steps; STSO is measured between consecutive steps in the given step ranges, and WO is the whole-run overhead outside step bodies · stream latency: parallel reader/writer steps on a dedicated stream; SL is the in-deployment write->read propagation (readAt - writtenAt) · stream overhead (text): writer streams 300 variable-length text token deltas paced at 100/s for 3s (a haiku-size LLM's token throughput) while a parallel reader drains the whole stream; SO is the end-to-end write+consume time beyond the 3s generation window (overhead/backpressure) · stream overhead (structured): same workload as stream overhead (text), but each delta is an AI-SDK-style structured object ({ type: 'text-delta', id, text }) instead of a raw string, so the SO gap vs the text scenario is the added serialization cost 🔴 marks a percentile over its target (within target is left unmarked). Targets (p75/p90/p99, ms) — TTFS 200/300/600 · SL 50/60/125 · SO 250/500/1000 · STSO (1-20) 20/30/60 · STSO (101-120) 30/45/90 · STSO (1001-1020) 40/60/120 All metrics are measured from deployment-side timestamps only. Runs are triggered by an in-deployment route that stamps the anchor ( Cold starts are kept in the numbers on purpose — they are part of real bursty-workload latency. The workbench deployment cold-starts the |
Uh oh!
There was an error while loading. Please reload this page.
No backport to This commit only changes the backport automation's decision policy and default AI model in To override, re-run the Backport to stable workflow manually via |
…ry-2 * origin/main: (292 commits) feat(core): seal forwarded stream writes to the owner's public key (#3098) feat(core): seal hook payloads to the target run's public key (#3096) [e2e] Rebuild the event-log corruption repro around step-count divergence (#3147) feat: decrypt sealed payloads in the dashboard and CLI (#3146) Prewarm only appended replay payloads (#3131) feat: publish each run's X25519 public key on the run entity (#3095) feat(core): route sealed envelopes through the serialization layer (#3094) docs: redirect retired migration-guides URLs to comparisons (#3127) feat(core): add `encp` sealed-box encryption primitive (#3093) chore(core): clarify runtime comments (#3111) Remove obsolete world factory aliases (#3112) feat(core): deterministic sandbox hardening (#3045) Remove retired v1 step route plumbing (#3061) [core] Don't count racing invocations' duplicate step_started events toward the maxRetries ceiling (#3069) [world-testing] Isolate each spawned test server's data directory (#3055) fix: upgrade postcss to >=8.5.18 to address GHSA-r28c-9q8g-f849 (#3102) [next] Respect .gitignore in dev watcher to avoid EMFILE on large monorepos (#3085) [ci] Backport only stability fixes to `stable`, default to claude-opus-5 (#3092) perf(core): immediate leading-edge dispatch for idle streams (flush window default 0) (#3088) Optimize `processImportSpecifier` by computing `shouldFollowImportsFromFile` once per file (#3052) ... # Conflicts: # docs/components/geistdocs/desktop-menu.tsx # docs/components/geistdocs/mobile-menu.tsx # docs/content/docs/v5/cookbook/advanced/child-workflows.mdx # docs/content/docs/v5/cookbook/advanced/upgrading-workflows.mdx # docs/content/docs/v5/cookbook/agent-patterns/agent-cancellation.mdx # docs/content/docs/v5/cookbook/agent-patterns/durable-agent.mdx # docs/content/docs/v5/cookbook/agent-patterns/human-in-the-loop.mdx # docs/content/docs/v5/cookbook/common-patterns/batching.mdx # docs/content/docs/v5/cookbook/common-patterns/idempotency.mdx # docs/content/docs/v5/cookbook/common-patterns/rate-limiting.mdx # docs/content/docs/v5/cookbook/common-patterns/saga.mdx # docs/content/docs/v5/cookbook/common-patterns/scheduling.mdx # docs/content/docs/v5/cookbook/common-patterns/sequential-and-parallel.mdx # docs/content/docs/v5/cookbook/common-patterns/timeouts.mdx # docs/content/docs/v5/cookbook/common-patterns/webhooks.mdx # docs/content/docs/v5/cookbook/common-patterns/workflow-composition.mdx # docs/content/docs/v5/cookbook/index.mdx # docs/content/docs/v5/cookbook/integrations/ai-sdk.mdx # docs/content/docs/v5/cookbook/integrations/chat-sdk.mdx # docs/content/docs/v5/cookbook/integrations/sandbox.mdx # docs/next.config.ts # docs/proxy.ts # docs/scripts/lint.ts # pnpm-lock.yaml # pnpm-workspace.yaml
Two changes to
.github/workflows/backport.yml.1.
stabletakes stability fixes onlyThe decision prompt used to tell the AI to lean toward backporting, and listed "minor feature additions that are self-contained and not dependent on
main-only changes" as backport-worthy. The result is that feature work lands onstablewhenever it happens to cherry-pick cleanly — which is exactly backwards for a maintenance line whose users stayed behind for stability.The prompt now recommends a backport only for:
stablestable, and flaky-test fixesstablebuildable and releasablestableand declines everything else, calling out the cases that used to slip through: small additive features, performance work and refactors that aren't fixing a user-visible defect, non-defect behavior changes to existing APIs, and routine non-security dependency bumps. Mixed fix-plus-feature commits are declined with the fix named in the reasoning so a human can split it out.
The tiebreak also flips: when in doubt, decline. A missed fix can be forced through with
workflow_dispatch; unwanted change onstablecan't be un-shipped. The prompt explicitly says a clean cherry-pick is not evidence that a change belongs onstable.Nothing about the mechanism changes — the action still only ever opens a PR for human review, still comments the reasoning on the source PR when it declines, and
workflow_dispatchstill forces a backport.2. Default model →
anthropic/claude-opus-5Was
anthropic/claude-fable-5. Confirmed the slug is exposed by the AI Gateway (https://ai-gateway.vercel.sh/v1/models), so opencode won't hitProviderModelNotFoundError. Themodelinput still overrides it per dispatch.AGENTS.mdis updated to match.Verification
.github/workflows/backport.ymlparses as YAML (js-yaml),env.AI_MODELresolves as expected.**bold**survive shell escaping, no stray command substitution.Expect the immediate effect to be a lower backport rate; the no-backport comment on each source PR states which criterion applied.
🤖 Generated with Claude Code