chore: remove obsolete v3/v4 version copy from the dashboard - #4589
Merged
Conversation
Engine V1 (v3) execution has been removed, so every "you need V4 for this" notice in the dashboard decorated a feature that is already available to everyone, and the side menu's v3 deprecation panel advertised shutdown dates that have now passed. Removes the V4Badge/V4Title component and its call sites, the "branches require V4" copy in the environment selector and both blank-state panels, the V3 deprecation panel in the side menu, and the queues-page engine-version upgrade callout along with the presenter code paths that produced it. Co-Authored-By: Claude <noreply@anthropic.com>
|
The dashboard-side cleanup dropped the engine-version failure arm from the queue presenters, which also removed the 400 that GET /api/v1/queues and GET /api/v1/queues/:queueParam returned for engine V1 projects. Restore that rejection in the two API route handlers so v3 clients still get a clean 4xx, while the dashboard keeps the simplified presenter result and page. Co-Authored-By: Claude <noreply@anthropic.com>
carderne
marked this pull request as ready for review
August 12, 2026 13:43
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
Restore the BookOpenIcon and docsPath imports in the queues route. This branch removed them along with the obsolete v3 upgrade callout, while main's #4592 added new WhenAgentUnavailable docs buttons that use both. The textual merge was clean but left the file referencing two unimported symbols. Co-Authored-By: Claude <noreply@anthropic.com>
Restore the allowArbitraryQueues flag on the test-task and replay paths. The queue dropdown is fed by a query that hard-filters version "V2", so a V1 environment sees an empty list; the free-text input is the only way those users can set a queue. Removing it was a functional regression and out of scope for a copy cleanup. Also drop QueuesHasNoTasks, which lost its only renderer along with the V1 queues failure UI, and the now-unreferenced queues-dashboard.png asset. Co-Authored-By: Claude <noreply@anthropic.com>
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
Restore the V3DeprecationPanel in the side menu for old v3 projects and reword it: "v3 is now deprecated" plus a note that no runs are executing and a link to the v4 upgrade guide. Co-Authored-By: Claude <noreply@anthropic.com>
samejr
approved these changes
Aug 13, 2026
Merged
ericallam
pushed a commit
that referenced
this pull request
Aug 13, 2026
## Summary 4 new features, 24 improvements, 10 bug fixes. ## Highlights - Allow `trigger deploy` to authenticate with an environment API key from `TRIGGER_ACCESS_TOKEN`. ([#4561](#4561)) ## Improvements - Chat in the browser now reconnects when the connection drops mid-turn, instead of leaving the reply stuck as if it were still generating. Reports can be fetched as structured data with the `json` format, and the shortest report period is now one minute (`1m`, `30m`, `1h`, `7d`). The `mint-token` command's help is clearer too: a token minted without `--cap` is read-only, and `--ttl` shows the correct maximum lifetime of 7 days. ([#4418](#4418)) - The dev environment onboarding now tracks real progress. After you run `init`, the setup checklist marks your project as initialized, and it updates live as your dev server connects and your tasks register. The blank state also adds a "Copy AI agent prompt" button that copies a ready-to-paste setup prompt (pre-filled with your project reference) for Claude Code, Cursor, or any coding agent. ([#4563](#4563)) The `init` scaffold now imports from `@trigger.dev/sdk` instead of the deprecated `@trigger.dev/sdk/v3` subpath. - Deployed images now ship dependencies and bundled task code as separate layers. Repeat deploys with unchanged dependencies typically push and pull far less data, making deploys and worker image pulls faster. ([#4551](#4551)) - The current-worker API now reports each task's queue, so you can see which tasks write to a given queue. ([#4525](#4525)) - Watch-mode chat streams now survive quiet windows and page reloads, and a reply cut off by a lost connection shows an error instead of appearing finished. Aborting a resumed subscription only closes your local stream — call `stopGeneration(chatId)` or pass `stopOnAbort: true` to stop the run. Also fixed a race where quickly restarting a stream could break stop and reconnect, and stopping a chat now hands it back to your other tabs instead of leaving them read-only. ([#4516](#4516)) ## Server changes These changes affect the self-hosted Docker image and Trigger.dev Cloud: - The dashboard agent now has a monthly message allowance and plan-based limits on watches. Queries stay read-only with clearer errors when busy, and messages with unusual characters no longer fail to send. ([#4516](#4516)) - Meet the dashboard agent: a chat in every environment that answers questions about your runs, queues, errors and health with real data and links, replacing Ask AI everywhere it used to appear. Investigate a failed run, an error, a backed-up queue or a run that hasn't started to get a worked-through answer — what happened, why, and how to fix it, with every claim linked to the runs, errors and deploys behind it. It reads your data read-only, works on preview and dev branches with that branch's own data, and reads the same everywhere — dashboard, terminal, editor. A very long chat keeps working: the agent summarises the earlier part and carries on. **Watch…** on a run, queue, error or the health report tells you when things change: a run finishes, a queue clears or grows past a number you pick, an error comes back, an environment recovers. The answer arrives in the chat and, if you want, by email, Slack or webhook — and the agent can look into bad news on its own. A watch reaches you on any browser you sign in from, without opening the chat first. A sample of conversations is scored automatically so the agent keeps getting better; only the score and a one-line summary are kept, never your messages, data or code, and we can switch it off for your organization on request. Ask the agent instead of the Docs buttons in page headers — they stay there when the agent isn't available to you. Separately, a queue's wait times, peak depth, throughput and throttling can now be read from the API. ([#4418](#4418)) - Add backend support for delaying cron schedules within a specified window with a minimum of 60 seconds. ([#4566](#4566)) - Reduced recurring background database load from the billing-limit recovery check, so paused environments are reconciled with less overhead. ([#4590](#4590)) - Validating a schedule when deploying or updating a schedule now does less work on projects with many preview branches, so those operations stay fast as branches accumulate. ([#4598](#4598)) - Project pages now load faster for projects with a large number of preview branches, by no longer loading archived branch environments that aren't shown. ([#4595](#4595)) - Database queries that filter on a list of values now reuse cached query plans more consistently, instead of forcing the database to re-plan whenever the list length changes. ([#4480](#4480)) - Routine cleanup of old dashboard agent data now runs on its own schedule. ([#4599](#4599)) - Database connection metrics are now reported for every configured database connection instead of only the primary one, and stay accurate regardless of connection type. ([#4541](#4541)) - Deployment-related API endpoints now draw from their own generous rate limit budget, configurable via the `DEPLOYMENT_RATE_LIMIT_*` environment variables, so runtime API traffic no longer competes with deployments for the same per-environment budget. ([#4565](#4565)) - Deleting or editing a secret environment variable is now fast and no longer slows down as a project accumulates variables. ([#4555](#4555)) - Speed up personal access token lookups by indexing them on their owner ([#4588](#4588)) - Switching project or organization in the sidebar now keeps you on the same page instead of sending you back to Tasks. Pages for a specific run, deploy or other single item open the matching list instead. ([#4585](#4585)) - Reduced database load when loading the dashboard by removing an unused organization member count that was being calculated on every page navigation. ([#4587](#4587)) - The environment variables page now loads a page at a time, keeping it fast for projects with a large number of variables. Search matches variable names across every page. ([#4597](#4597)) - Groundwork for an alternative database connection driver, gated behind configuration and disabled by default, so there is no change to default behavior. ([#4539](#4539)) - Deleting an alert channel is now fast and no longer slows down as a project builds up alert history. ([#4554](#4554)) - Reduced internal overhead on the API under high load. ([#4532](#4532)) - Out-of-date upgrade prompts no longer appear in the dashboard: the "V4" badges and the notices saying preview branches and the queues table need V4 have been removed. The side menu still warns you when a project is on v3, with updated wording and a link to the v4 upgrade guide. ([#4589](#4589)) - Make background worker registration cheaper for projects with many scheduled tasks by scoping declarative schedule reconciliation to the current environment and dropping redundant schedule lookups. ([#4577](#4577)) - Speed up setting and importing environment variables for projects with many variables. ([#4579](#4579)) - Loading the deployments list is now faster, especially when filtering by deployment status on projects with many deployments. ([#4591](#4591)) - Fixed the billing limits page timing out for organizations with many preview branches, especially while a spend limit was being enforced. The page now loads quickly, so you can raise or resolve your limit without delay. ([#4594](#4594)) - Fix the Concurrency page showing the plan's default concurrency for the dev environment instead of the environment's actual limit. ([#4596](#4596)) - Creating an organization sometimes left you back on the creation form even though the organization had already been created, so clicking Create again made a duplicate. Creating an organization now completes and takes you to your new organization. ([#4530](#4530)) - Ensure creating a project completes instead of returning to its creation form after a navigation error. ([#4584](#4584)) - Renaming a project now keeps you on the project settings page and tells you what happened, instead of silently moving you to the tasks page or clearing the form with no explanation. ([#4601](#4601)) - Fixed support threads showing no account details for some customers, so the team can see your plan, organizations and projects when you get in touch. ([#4575](#4575)) - In the light theme, the Format, Clear and Copy buttons on the query editor no longer blend into the query text behind them. ([#4592](#4592)) - The health report now says start latency is "unknown" when there is no data for it, instead of showing a healthy-looking 0ms ([#4544](#4544)) - Realtime streams written inside a chat session run now use the same backend as the session itself, and runs are no longer created against a backend that cannot serve them. ([#4564](#4564)) - The grouped "watch updates" notification now shows the total number of results waiting, instead of only the most recent batch's count. ([#4525](#4525)) <details> <summary>Raw changeset output</summary> # Releases ## @trigger.dev/build@4.5.11 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.5.11` ## trigger.dev@4.5.11 ### Patch Changes - Chat in the browser now reconnects when the connection drops mid-turn, instead of leaving the reply stuck as if it were still generating. Reports can be fetched as structured data with the `json` format, and the shortest report period is now one minute (`1m`, `30m`, `1h`, `7d`). The `mint-token` command's help is clearer too: a token minted without `--cap` is read-only, and `--ttl` shows the correct maximum lifetime of 7 days. ([#4418](#4418)) - Allow `trigger deploy` to authenticate with an environment API key from `TRIGGER_ACCESS_TOKEN`. ([#4561](#4561)) - The dev environment onboarding now tracks real progress. After you run `init`, the setup checklist marks your project as initialized, and it updates live as your dev server connects and your tasks register. The blank state also adds a "Copy AI agent prompt" button that copies a ready-to-paste setup prompt (pre-filled with your project reference) for Claude Code, Cursor, or any coding agent. ([#4563](#4563)) The `init` scaffold now imports from `@trigger.dev/sdk` instead of the deprecated `@trigger.dev/sdk/v3` subpath. - Deployed images now ship dependencies and bundled task code as separate layers. Repeat deploys with unchanged dependencies typically push and pull far less data, making deploys and worker image pulls faster. ([#4551](#4551)) - Updated dependencies: - `@trigger.dev/core@4.5.11` - `@trigger.dev/build@4.5.11` - `@trigger.dev/schema-to-json@4.5.11` ## @trigger.dev/core@4.5.11 ### Patch Changes - Chat in the browser now reconnects when the connection drops mid-turn, instead of leaving the reply stuck as if it were still generating. Reports can be fetched as structured data with the `json` format, and the shortest report period is now one minute (`1m`, `30m`, `1h`, `7d`). The `mint-token` command's help is clearer too: a token minted without `--cap` is read-only, and `--ttl` shows the correct maximum lifetime of 7 days. ([#4418](#4418)) - The current-worker API now reports each task's queue, so you can see which tasks write to a given queue. ([#4525](#4525)) ## @trigger.dev/python@4.5.11 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.5.11` - `@trigger.dev/sdk@4.5.11` - `@trigger.dev/build@4.5.11` ## @trigger.dev/react-hooks@4.5.11 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.5.11` ## @trigger.dev/redis-worker@4.5.11 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.5.11` ## @trigger.dev/rsc@4.5.11 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.5.11` ## @trigger.dev/schema-to-json@4.5.11 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.5.11` ## @trigger.dev/sdk@4.5.11 ### Patch Changes - Chat in the browser now reconnects when the connection drops mid-turn, instead of leaving the reply stuck as if it were still generating. Reports can be fetched as structured data with the `json` format, and the shortest report period is now one minute (`1m`, `30m`, `1h`, `7d`). The `mint-token` command's help is clearer too: a token minted without `--cap` is read-only, and `--ttl` shows the correct maximum lifetime of 7 days. ([#4418](#4418)) - Watch-mode chat streams now survive quiet windows and page reloads, and a reply cut off by a lost connection shows an error instead of appearing finished. Aborting a resumed subscription only closes your local stream — call `stopGeneration(chatId)` or pass `stopOnAbort: true` to stop the run. Also fixed a race where quickly restarting a stream could break stop and reconnect, and stopping a chat now hands it back to your other tabs instead of leaving them read-only. ([#4516](#4516)) - Updated dependencies: - `@trigger.dev/core@4.5.11` </details> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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
3 participants
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.
Requested by Chris Arderne · Slack thread
✅ Checklist
Before / after
Engine V1 (v3) execution is gone, so every "you need V4 for this" notice in the dashboard was decorating a feature that everyone already has.
Before
After
The branch panels keep the sentence that explains what branches are and drop the version claim; the panel whose real gate is the plan lets its title and Upgrade button carry that on their own, rather than asserting a second, wrong reason. Page titles are plain text. The queues page always renders the queues table.
The side menu panel stays — an old v3 project still needs to be told why nothing is running — but now says what is true today: title "v3 is now deprecated", body "This is a v3 project which is now deprecated so no runs are executing. Upgrade to v4 to resume executing runs in this project.", and its button links to the v4 upgrade guide. Who sees it is unchanged: managed cloud only,
engine === "V1", project created before the v4 release date, and no active incident.Scope
This is copy removal plus the dead code that removal leaves behind. The test-task and replay forms are not touched. An earlier revision of this branch also deleted the
allowArbitraryQueuesflag those two paths use to swap the queueSelectfor a free-textInput. That was wrong: the dropdown is fed by a query that hard-filtersversion: "V2", so on an engine V1 environment the list comes back empty and the free-text input is the only way to set a queue at all. Both paths keep their existing behaviour, andTestTaskPresenter.server.ts,resources.taskruns.$runParam.replay.ts,ReplayRunDialog.tsxand the test-task route are back to zero diff againstmain.How
apps/webapp/app/components/V4Badge.tsx(V4Badge+V4Title) and unwrapped its call sites inwaitpoints.tokens,branches(two arms) anddev-branchesroutes so each is a plain<PageTitle title="…" />.components/navigation/EnvironmentSelector.tsxand both panels incomponents/BlankStatePanels.tsx, plus the imports that went with it.V3DeprecationPanel/V3DeprecationContentincomponents/navigation/SideMenu.tsx— structure, styling, collapsed-rail popover and gating (isV3Project,isLikelyV3,V4_RELEASE_DATE) all unchanged, along with theengine/createdAtfields onSideMenuProjectthe gating reads. Only the copy changed: new title and body, and the link now goes throughdocsPath("/upgrade-to-v4")to the v4 upgrade guide instead of the hardcoded migration-guide URL.EngineVersionUpgradeCalloutand bothcode === "engine-version"call sites from the queues route. That took the last reference toassets/images/queues-dashboard.pngwith it, so the screenshot is deleted too, along withQueuesHasNoTasksinBlankStatePanels.tsx— the removed failure UI was its only renderer, and it is unreachable without it.code: "engine-version"producers fromQueueListPresenter.server.tsandQueueRetrievePresenter.server.ts, and moved that check up into the two API route handlers.GET /api/v1/queuesandGET /api/v1/queues/:queueParamstill calldetermineEngineVersionand still answer an engine V1 project with400 {"error": "engine-version"}, unchanged — that is a reachable clean-4xx path for clients still on v3, and only the dashboard's rendering of it was removed. InQueueRetrievePresenterthequeue-not-foundfailure arm survives, soapi.v1.queues.$queueParam.tsreturns the 400 before the presenter runs and maps the presenter's one remaining failure to 404. InQueueListPresenterengine-versionwas the onlysuccess: falseproducer, so with the check hoisted the result type collapses to a single object shape;api.v1.queues.ts, the queues resource route, the runs AI-filter route and the queues page were updated to match.project.engine === "V2"guards that engine V1's removal made constant, in the runs index route and the side menu.None of these are part of the deprecation boundary described in
.claude/rules/legacy-v3-code.md— they are display affordances, not reject-cleanly paths. The V1 branches inengineDeprecation.server.ts,engineVersion.server.ts,triggerTask.server.ts,cancelTaskRun.server.ts,rescheduleTaskRun.server.ts,initializeDeployment.server.tsandhandleWebsockets.server.tsare untouched, as are the historical-data paths inSpanPresenter,ApiRetrieveRunPresenter,replayTaskRunand the admin debug views.Left for follow-up
Deliberately out of scope here:
docsPath("v3/…")link targets (tasks.scheduled.$taskParam,schedules.new,test.tasks.$taskParam,tasks.dashboard,components/runs/v3/TaskRunsTable.tsx,BlankStatePanels). They resolve, but via two redirect hops.batchVersion === "v1"tooltip on the batches page, "Upgrade to the latest SDK for batch statuses to appear." The gate is live legacy data, but the advice is stale — a v1 batch is a historical record that upgrading cannot fix. That is a rewording, not a removal.@trigger.dev/sdk/v3warning inSetupCommands.tsx, which is still useful guidance inside an agent-rules prompt."Beta upgrade guide"onOUTDATED_SDK_VERSIONinpackages/core— stale branding rather than a v3/v4 specifier, and it would turn this into a mixed PR.One thing noticed while working that was not in scope:
WaitpointListPresenter.server.tsstill returns"Upgrade to SDK version 4+ to use Waitpoint tokens."behind anengineVersion === "V1"check — the same shape as the queues callout removed here, worth the same treatment.pauseQueue.server.tskeeps itscode: "engine-version"rejection, and so do the two queues API endpoints — that is API behaviour on the clean-4xx boundary, not dashboard copy.Testing
pnpm run typecheck --filter webapppasses, andpnpm run lintis clean afterpnpm run format/pnpm run lint:fix. Not exercised in a running dashboard.Changelog
Out-of-date upgrade prompts no longer appear in the dashboard: the "V4" badges and the notices saying preview branches and the queues table need V4 have been removed. The side menu still warns you when a project is on v3, with updated wording and a link to the v4 upgrade guide.