- When a GitHub organization owner approves your install request, the Git Repository page shows a banner with Link it. An installation marked Not linked has a Link button.
- A workspace that clones with a deploy key shows a banner to connect the repository through the GitHub App instead.
- After you install the GitHub App, the Git Repository page updates without a reload.
- Switching a workspace between a deploy key and the GitHub App now redeploys its Bolt schedules.
- Branch pickers are no longer empty after you connect a repository through the GitHub App or GitLab.
- To install GitLab with your own bot, use a personal access token of the bot user. Group and project access tokens can’t create the per-run tokens. The OAuth application step shows the redirect URL for your Paradime region. See Choose how Paradime gets in.
- The DinoAI reviewer runs
paradime-pr-reviewer, the reviewer agent that Paradime builds in. If your workspace has its own agent namedpr-reviewer, the DinoAI reviewer runs that agent instead. See The DinoAI reviewer. - If the agent of a custom reviewer was deleted or renamed, the Paradime Code Review check shows
Not reviewed: no reviewer agent, with a link to the Code review settings. Before, no check was posted. - Code review is always in the Agent app sidebar. If the workspace isn’t ready for reviews, the page says what to connect first, with a button for it.
- Schedules in a workspace with no git repository, such as agent-only schedules, deploy again.
- Cron schedules that use
7for Sunday, for example0 6 * * 1-7, now deploy. - Bolt runs Lightdash CLI 3.253.1, so
lightdashcommands no longer warn that the CLI runs a different version than Lightdash. - In Slack alert templates, Paradime escapes the values of template variables, so text such as
<!channel>in dbt™ error output no longer notifies the channel. A template that goes over the new rendering limits sends the default notification. See Template limits. - The Slack, Microsoft Teams, and email destinations for Bolt run and parse errors now follow Bolt permissions. Anyone who can create schedules can change them, and anyone who can see Bolt can view them. Before, they needed Radar alert permissions.
- When a warehouse that the Warehouse AI Agent Optimizer runs on is dropped, renamed, or no longer reachable, Radar sends one notification a day that lists those warehouses and what to do. It goes to the default destinations of Radar alerts, or to the workspace admins if no defaults were ever saved. See When a cost agent stops working.
- Tableau syncs finish when the Tableau Metadata API times out on custom SQL. Paradime skips only the lineage of that custom SQL.
- A Power BI integration with expired or wrong credentials now shows the failure on the integration.
- A field that Looker rejects no longer drops the column lineage of the whole explore, and column lineage builds now finish on large Looker instances.
- Custom integrations can declare field-level lineage with the Paradime Python SDK 6.12.0. See Add field-level lineage.
- Cross-project
ref()calls from a dbt™ 2.0 project to a dbt Core™ Snowflake project that doesn’t quote its names now resolve. Paradime Mesh publications now carry the quoting settings of the producer project.
- Harvest mode for Thanksgiving: from November 20 to 30, a Harvest mode switch shows in the left sidebar, above Search. Switch it on for a Thanksgiving greeting on Home and a pumpkin pie cursor. Paradime saves your choice in your browser.