Changelog
What we shipped, newest first. Small fixes ship every day; these are the changes worth knowing about.
October 2026
-
Dagster support is generally available
Asset materializations, asset checks and run logs now feed incidents, lineage and fix pull requests. Thanks to the 31 teams in the beta.
-
Freshness promises in local time
Write promises like “ready by 7:00 Riyadh time” for teams that work across GCC time zones. Daylight saving changes for teams abroad are handled for you.
-
Faster lineage for large projects
First-time mapping of a 2,000-model project is down from 9 minutes to under 4.
September 2026
-
Fix pattern: Snowflake permission errors
When a role loses a grant, Tessel names the missing privilege and proposes the change to your grants file.
-
PagerDuty auto-resolve
Pages now resolve on their own when the fix pull request is merged and the next run succeeds.
-
Incident links in dbt Cloud
Links from incidents to dbt Cloud runs now open the right account for teams with more than one.
August 2026
-
Volume checks for joins
Watch the match rate of joins you mark as important and get an incident when it drops.
-
Saudi region for all plans
Starter workspaces can now choose to store metadata in Dammam as well as in the UAE.
-
Quieter Slack threads
Follow-up runs update the original incident message instead of posting new ones.
How we ship
Tessel deploys several times a day. New features go to a beta group first, then to everyone once they have run on at least 20 production workspaces without a regression.
Changes that affect what Tessel reads or stores are announced by email to workspace admins at least 30 days ahead and listed here. Nothing that changes permissions ever ships silently.