> ## Documentation Index > Fetch the complete documentation index at: https://docs.paradime.io/llms.txt > Use this file to discover all available pages before exploring further. # Other improvements > Fixes in v6.19: one Turbo CI result for shared repos, merges in merge order, clearer Bolt run pages, MCP reconnects, agent Python installs, dbt-trino 1.10.6. *October 16, 2026* **CI/CD chains** * **Repositories shared by several workspaces:** `Paradime Turbo CI` now combines the result of every workspace that runs CI on the pull request, and fails if any of them fails. Before, the last workspace to report decided it, so a failure could hide behind a pass. Each workspace also gets its own `Paradime Turbo CI / ` check, so require only `Paradime Turbo CI` in branch protection. See [Chains](/products/bolt/ci-cd/chains#several-workspaces-on-one-repository). * **Merge order:** a [merge queue](/products/bolt/ci-cd/chains#merge-queue) runs merges in the order they merged, not in the order GitHub's events arrive. An older merge that arrives after a newer one already had its turn is skipped, because the newer merge commit contains its changes. * **Merge retries:** retry a failed merge step while another step of the same merge still waits in the queue. * **Branch overrides:** a run on a branch other than its schedule's own, such as an API or CLI trigger with a branch, no longer starts the schedules that [run after](/products/bolt/creating-schedules/trigger-types#on-run-completion) it. The run page shows a **Branch override** pill. * A late or redelivered GitHub event no longer restarts the chain of a closed or draft pull request. **Bolt** * The **Retry from failure** dialog wraps long commands, so **Cancel** and **Retry** stay on screen. * On a run page, the pipeline graph shows this run's own parent and child runs, with links, instead of each schedule's latest run. * A retry shows **Retry of #N** and who started it, instead of "Triggered by" the run it retried. * The schedule's YAML view and downloaded YAML use `run_after` instead of `schedule_trigger`. * [`run_after`](/products/bolt/creating-schedules/schedules-as-code/configuration-reference#run-completion-trigger) accepts a bare `on:`, which used to break the whole schedules file. `paradime bolt verify` accepts it from Paradime CLI 6.9.0. **DinoAI** * **MCP servers:** add OAuth servers that use a client ID metadata document, such as Loops, without a client ID. A server that isn't connected opens its page from the card, with its status, the error, **Reconnect**, and **Remove**. A **Public (no auth)** server that fails to connect is no longer saved. See [External MCP servers](/products/dino-ai/programmable-agents/external-mcp-servers). * Agents can install a repository's Python dependencies, with `poetry install` or a virtual environment under `/tmp`, to test a Python change before opening a pull request. * Agents no longer fail to push their branch, or to run `dbt`, when they run the command through a shell wrapper such as `bash -c`. * A code block in a language DinoAI doesn't recognize shows as plain text, and no longer stops the code blocks after it from being highlighted. * The first time you open DinoAI in the Code IDE, a single welcome screen replaces the five-step tour. **Settings** * Adding, changing, renaming, or removing a **Default** environment variable now updates every developer's Code IDE straight away. New terminals see the change without anyone saving their own Code IDE variables first. See [Environment Variables](/products/settings/environment-variables/index#default). **dbt™** * Bolt runs and DinoAI agents use dbt-trino 1.10.6 on dbt™ 1.10, 1.11, and 1.12, up from 1.9.3, 1.10.2, and 1.10.3 respectively. ## Related topics - [Other improvements](/changelog/2026-09-03/other-improvements.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.