Document conservative DB Connect / serverless env upgrade rule - #6407
Open
rugpanov wants to merge 1 commit into
Open
Document conservative DB Connect / serverless env upgrade rule#6407rugpanov wants to merge 1 commit into
rugpanov wants to merge 1 commit into
Conversation
rugpanov
force-pushed
the
serverless-upgrade-guidance
branch
from
August 27, 2026 20:40
7b018ef to
baf5cb3
Compare
Follow-up to #6378. Tightens the comment above conservative_db_connect_version_spec into crisp upgrade guidance, and adds an .agents/rules doc capturing the conservative DB Connect upgrade rule and the env-version / Python / DB Connect consistency invariant so the next serverless environment bump is smoother. Co-authored-by: Isaac <no-reply@databricks.com>
rugpanov
force-pushed
the
serverless-upgrade-guidance
branch
from
August 27, 2026 20:42
baf5cb3 to
507d261
Compare
Collaborator
Integration test reportCommit: 507d261
Top 3 slowest tests (at least 2 minutes):
|
rugpanov
marked this pull request as ready for review
August 27, 2026 21:03
Contributor
Author
|
@yiweidai-db @Hangzhi — follow-up to #6378 addressing your review requests: this documents the conservative DB Connect upgrade rule and the env-version / Python / DB Connect consistency invariant. Couldn't add you as formal reviewers (GitHub requires repo collaborator access), so flagging here — would appreciate your eyes. cc @lennartkats-db |
yiweidai-db
reviewed
Aug 28, 2026
| `default_python_version`; the SQL templates (`dbt-sql`, `default-sql`) define | ||
| only a subset. | ||
|
|
||
| **RULE: Keep `conservative_db_connect_version_spec` (in `default/`) at the lowest version that still works. Bump it only when the pinned DBR release falls out of support — never just to match the newest serverless environment version.** The DB Connect client is only forward-compatible: it reaches compute of its own version and higher. The lowest working pin therefore maximizes the range of DBR versions a customer can connect to, whereas a high pin rules out customers on older DBR. Customers can upgrade themselves after initializing the template. This is why the pin typically lags the newest release. See PR #3897 and PR #6378 for prior history. |
There was a problem hiding this comment.
[suggestion]
Let's link the DBR support matrix docs for agents to search https://docs.databricks.com/aws/en/release-notes/runtime/
yiweidai-db
approved these changes
Aug 28, 2026
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.
Changes
Follow-up to #6378 — documents the conservative DB Connect upgrade rule reviewers asked for, so the next serverless env bump goes smoothly.
conservative_db_connect_version_specinto a crisp upgrade rule.agents/rules/template-versions.md: keep the DB Connect pin conservative (bump only when the pinned DBR falls out of support, not to match the newest serverless env), keep env-version / Python / DB Connect mutually compatible, and only keepserverless_environment_versionin sync across templatesWhy
Tests
{{/* */}}block, so rendered output and acceptance goldens are unchangedFollow-ups in separate PRs: a
bump-serverless-env-versionskill, and dead-macro cleanup indbt-sql.This pull request and its description were written by Isaac.