Repository navigation
Invite signed-in users to try the version 3 pre-release, once - #2331
Conversation
Co-authored-by: Isaac <no-reply@databricks.com>
anton-107
left a comment
There was a problem hiding this comment.
A few copy suggestions for the invitation, none blocking. I rendered the toast in VS Code 1.147 to check how it reads.
| this.record("shown"); | ||
|
|
||
| const choice = await window.showInformationMessage( | ||
| "Try the version 3 pre-release of the Databricks extension? It adds Unity Gateway models in VS Code Chat and a redesigned sidebar. You can switch back to version 2 anytime.", |
There was a problem hiding this comment.
"Try X?" asks a yes/no question, but the buttons don't answer it: "Release notes" isn't a yes or a no, and the only no is closing the toast. VS Code's own notifications state a fact and let the buttons carry the choice ("A new version of VS Code is available. [Update Now] [Release Notes]"). A statement also reads better when the toast ends up in the Notification Center. It also shortens the four-noun opening, and the toast already shows the extension as its source:
| "Try the version 3 pre-release of the Databricks extension? It adds Unity Gateway models in VS Code Chat and a redesigned sidebar. You can switch back to version 2 anytime.", | |
| "Version 3 of the Databricks extension is available as a pre-release, with Unity Gateway models in VS Code Chat and a redesigned sidebar. You can switch back to version 2 at any time.", |
| const SWITCH = "Switch to Pre-Release"; | ||
| const RELEASE_NOTES = "Release notes"; |
There was a problem hiding this comment.
Two small things on the buttons:
- VS Code's Extensions view calls these actions "Switch to Pre-Release Version" and "Switch to Release Version", and the 3.1.0 notes tell users to use "Switch to Release Version" to go back. Using the same words here makes the way back easy to find.
- VS Code buttons use title case, so "Release Notes" matches the button next to it.
| const SWITCH = "Switch to Pre-Release"; | |
| const RELEASE_NOTES = "Release notes"; | |
| const SWITCH = "Switch to Pre-Release Version"; | |
| const RELEASE_NOTES = "Release Notes"; |
The test file's SWITCH and RELEASE_NOTES constants (lines 20 and 22) would need the same change.
Co-authored-by: Isaac <no-reply@databricks.com>
Co-authored-by: Isaac <no-reply@databricks.com>
|
If integration tests don't run automatically, an authorized user can run them manually by following the instructions below: Trigger: Inputs:
Checks will be approved automatically on success. |
## packages/databricks-vscode ## (2026-11-20) * Handle GitHub Copilot detected only through VS Code's copilot shim (#2295) ([5e677a5](5e677a5)), closes [#2295](#2295) * Invite signed-in users to try the version 3 pre-release, once (#2331) ([5fc60f8](5fc60f8)), closes [#2331](#2331) * Update Databricks CLI to v1.27.0 (#2333) ([286b4e9](286b4e9)), closes [#2333](#2333) ## packages/databricks-vscode-types ## (2026-11-20) --------- Co-authored-by: releasebot <noreply@github.com> Co-authored-by: Abdurrahman Abdulaziz <abdelrahman_omar_1515@yahoo.com>
Changes
Shows a one-time invitation to try the version 3 pre-release of the extension. It uses the same extension ID (
databricks.databricks) and appears on the Marketplace pre-release channel.workbench.extensions.installExtensionwithinstallPreReleaseVersion: true. If it succeeds, the prompt "Reload the window to finish switching to version 3." is always offered, with "Reload Window". If the command throws, a generic error is shown and the real error is logged.release-v3.1.0tag.The reload prompt is not gated on a version check. In a VS Code test, the installed version still read 2.23.1 for at least 6 seconds after the install resolved, so comparing versions would hide the prompt.
Telemetry
The event
prereleaseInvitationrecordsshown,switch,switchFailed,releaseNotesanddismissed.Known limits
project.jsonare not excluded, and the notification does not mention that version 3 no longer migrates them. The release notes do.Tests
PreReleaseInvitationManager.test.ts, run in VS Code 1.138.0 (MOCHA_GREP=PreReleaseInvitation yarn run test:unit): 13 tests covering the host rules, the 5 s delay (not shown before it, cancelled when the connection drops, cancelled bydispose), the fork and remote-window gates throughshowIfDue, show-once, the end date, each answer and the failed switch (generic error, no raw error text).This pull request and its description were written by Isaac.