Hi @cmantilla ,

If you’d like to stay up to date on Databricks releases and any potentially breaking changes, the best way is to follow the official release notes and subscribe to the documentation RSS feed for your cloud.

Subscribe to release notes via RSS

Choose the feed for the cloud you’re using:

• Databricks on AWS:
  RSS feed:  https://docs.databricks.com/aws/en/feed.xml
  Release Notes hub:  https://docs.databricks.com/aws/en/release-notes/

• Databricks on GCP:
  RSS feed:  https://docs.databricks.com/gcp/en/feed.xml
  Release Notes hub:  https://docs.databricks.com/gcp/en/release-notes/

• Azure Databricks:
  RSS feed:  https://learn.microsoft.com/en-us/azure/databricks/feed.xml
  Release Notes hub:  https://learn.microsoft.com/en-us/azure/databricks/release-notes/

You can add the RSS URL to any feed reader (for example, Feedly, Outlook, Thunderbird, or an RSS‑to‑email service) to get notified whenever new release notes are published.

Where breaking/behaviour changes are documented

Once you click-through from the feed or the hub pages:

• Databricks Runtime release notes (per version) include sections like “Breaking changes” or “Behavioural changes” where behaviour-affecting updates are called out.
• Platform release notes (web UI, SQL, APIs, etc.) often explicitly mark items as “Breaking change: …” when something may affect existing workloads or scripts.

If you care specifically about breaking changes, you can also filter or search within your RSS reader or browser for terms like “Breaking change” or “behavioural changes” in those notes.

If your org is interested, you may use the official docs RSS feeds as the single source of truth, but wire them into org‑level tools rather than have individual users subscribe to them. You can then integrate it with Teams/Slack, etc, so that users can follow.

Also note, for some intentional breaking changes in Databricks Runtime, customers are usually notified in advance by email to registered Databricks account admins.

If this answer resolves your question, could you mark it as “Accept as Solution”? That helps other users quickly find the right fix.

Regards,