Skip to content

Read the Go SDK's _last_sha in the SDK consistency check - #7317

Merged
Divyansh-db merged 2 commits into
mainfrom
sdk-consistency-last-sha
Nov 4, 2026
Merged

Divyansh-db merged 2 commits into
mainfrom
sdk-consistency-last-sha

Conversation

@Divyansh-db

Copy link
Copy Markdown
Contributor

Changes

TestConsistentDatabricksSdkVersion and the bump-sdk skill now read the Go SDK's .codegen/_last_sha at the pinned version instead of .codegen/_openapi_sha. The CLI's own .codegen/_openapi_sha is unchanged.

Why

The Go SDK records the spec commit each release was generated from in _last_sha. Its _openapi_sha is now a copy of that value kept for older tooling and is being phased out. The two files hold the same value at every SDK release since v0.188.0, including the v0.193.0 pin on main, so the check's result doesn't change.

Tests

  • go test -run TestConsistentDatabricksSdkVersion ./internal/build passes on this branch: the CLI's .codegen/_openapi_sha matches the SDK's _last_sha at v0.193.0.
  • With the CLI's SHA replaced by a dummy value, the test fails with "please update the SDK version before generating the CLI".

This pull request and its description were written by Isaac.

The Go SDK records the spec commit each release was generated from in
.codegen/_last_sha. Its .codegen/_openapi_sha is now a copy of that value
kept for older tooling and is being phased out. TestConsistentDatabricksSdkVersion
and the bump-sdk skill now read _last_sha. Both files hold the same value
at every SDK release since v0.188.0, including the v0.193.0 pin on main.

Co-authored-by: Isaac <no-reply@databricks.com>
@eng-dev-ecosystem-bot

eng-dev-ecosystem-bot commented Nov 3, 2026 •

Copy link
Copy Markdown
Collaborator

Integration test report

Commit: e69be5b

Run: 41679391904

Env 🔄​flaky ✅​pass 🙈​skip Time
🔄​ aws linux-2core-8gb 1 270 15 13:24
🔄​ aws-windows-latest-4core-16gb 1 272 13 9:51
✅​ azure linux-2core-8gb 270 15 12:37
✅​ azure-windows-latest-4core-16gb 272 13 8:18
✅​ gcp linux-2core-8gb 271 15 10:38
✅​ gcp-windows-latest-4core-16gb 273 13 9:59
Test Name aws linux-2core-8gb aws-windows-latest-4core-16gb
🔄​ TestSyncIncrementalFileOverwritesFolder 🔄​f ✅​p
🔄​ TestSyncIncrementalSyncFileToPythonNotebook ✅​p 🔄​f
Top 22 slowest tests (at least 2 minutes):
duration env testname
3:37 azure linux-2core-8gb TestFilerWorkspaceNotebook/sqlNb.sql
3:35 aws-windows-latest-4core-16gb TestImportDirWithOverwriteFlag
3:34 gcp linux-2core-8gb TestFilerRecursiveDelete/workspace_files_extensions
3:27 aws-windows-latest-4core-16gb TestFilerWorkspaceFilesExtensionsRead
3:20 aws-windows-latest-4core-16gb TestAccept
3:20 aws-windows-latest-4core-16gb TestLock
3:20 azure-windows-latest-4core-16gb TestFilerWorkspaceFilesExtensionsStat
3:13 azure-windows-latest-4core-16gb TestAccept
3:12 gcp-windows-latest-4core-16gb TestAccept
3:01 gcp-windows-latest-4core-16gb TestFilerReadWrite/workspace_files
2:56 azure-windows-latest-4core-16gb TestFilerWorkspaceFilesExtensionsDelete
2:55 gcp linux-2core-8gb TestFilerRecursiveDelete/workspace_files
2:43 aws-windows-latest-4core-16gb TestFilerWorkspaceFilesExtensionsReadDir
2:35 aws linux-2core-8gb TestImportDirWithOverwriteFlag
2:34 azure linux-2core-8gb TestExportDir
2:26 gcp-windows-latest-4core-16gb TestFilerWorkspaceFilesExtensionsReadDir
2:14 aws-windows-latest-4core-16gb TestSyncFullFileSync
2:11 azure linux-2core-8gb TestFilerWorkspaceNotebook/scalaNb.scala
2:09 aws linux-2core-8gb TestFilerWorkspaceFilesExtensionsStat
2:04 aws linux-2core-8gb TestFilerRecursiveDelete/workspace_files
2:02 gcp linux-2core-8gb TestFilerReadDir/workspace_files_extensions
2:01 aws linux-2core-8gb TestFilerWorkspaceFilesExtensionsRead

@Divyansh-db
Divyansh-db marked this pull request as ready for review November 3, 2026 16:49
@Divyansh-db
Divyansh-db requested review from a team as code owners November 3, 2026 16:49
@Divyansh-db
Divyansh-db enabled auto-merge November 3, 2026 16:56
@Divyansh-db
Divyansh-db added this pull request to the merge queue Nov 4, 2026
Merged via the queue into main with commit a3fd25d Nov 4, 2026
27 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants