Skip to content

Bump cli-compat skills to 0.2.0#5324

Queued
jamesbroadhead wants to merge 3 commits into
mainfrom
jb/bump-cli-compat-skills-0.2.0
Queued

Bump cli-compat skills to 0.2.0#5324
jamesbroadhead wants to merge 3 commits into
mainfrom
jb/bump-cli-compat-skills-0.2.0

Conversation

@jamesbroadhead
Copy link
Copy Markdown
Contributor

@jamesbroadhead jamesbroadhead commented May 24, 2026

Summary

  • Update cli-compat.json to point CLI version 1.0.0 at Agent Skills 0.2.0 (from 0.1.5).
  • The 0.300.0 entry stays at skills 0.1.5 so older CLI binaries keep resolving to a tag whose manifest format they understand (no repo_dir).

Why

databricks-agent-skills v0.2.0 (release) introduces the new manifest layout with repo_dir: "skills" vs repo_dir: "experimental" per skill (replacing the dropped experimental boolean) and ships 18 experimental skills under experimental/. Until this bump lands, databricks aitools install --experimental resolves to v0.1.5 and finds nothing experimental — users have to set DATABRICKS_SKILLS_REF=main as a workaround.

The CLI installer already understands repo_dir (SkillMeta.IsExperimental() in libs/aitools/installer/installer.go), so no code change is needed — only the version pin.

Test plan

  • go test ./libs/clicompat/... ./libs/aitools/... — all green locally.
  • Built the CLI from this branch and ran DATABRICKS_FORCE_EMBEDDED_COMPAT=true databricks aitools list:
    • Header: Available skills (v0.2.0).
    • 26 skills resolved (8 stable + 18 experimental), matching databricks-agent-skills@v0.2.0 manifest.json.
    • Experimental skills correctly tagged [experimental] — confirms SkillMeta.IsExperimental() returns true for entries with repo_dir == "experimental" in the v2 manifest.
  • CI: go test ./libs/clicompat/... and ./libs/aitools/... pass. Previous Integration Tests failure (run 26372918714) was unrelated flake — failing on TestAccept/bundle/resources/* and TestFsCp* on aws-prod-ucws-is/gcp-prod-is runners, none of which read cli-compat.json; same workflow has been flaking on main independently. Re-pushed an empty commit to retrigger.

Related

This pull request and its description were written by Isaac.

Pulls in the new experimental skills (18 skills under repo_dir=experimental)
released in databricks-agent-skills v0.2.0, so `databricks aitools install
--experimental` resolves them without DATABRICKS_SKILLS_REF=main.

The 0.300.0 entry stays at skills 0.1.5 for older CLI binaries.

Co-authored-by: Isaac
@eng-dev-ecosystem-bot
Copy link
Copy Markdown
Collaborator

eng-dev-ecosystem-bot commented May 24, 2026

Commit: f092b72

Run: 26457894880

Previous Integration Tests run failed on TestAccept/bundle/resources/*
and TestFsCp* on aws-prod-ucws-is/dbr and gcp-prod-is runners. The
diff only changes the skills version in cli-compat.json, which is
read by `aitools install` and unrelated to those tests. The same
cli-isolated-pr workflow has been flaking on main independently.

Co-authored-by: Isaac
Copy link
Copy Markdown
Member

@pkosiec pkosiec left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

{
"1.0.0": { "appkit": "0.38.0", "skills": "0.1.5" },
"1.0.0": { "appkit": "0.38.0", "skills": "0.2.0" },
"0.300.0": { "appkit": "0.24.0", "skills": "0.1.5" }
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There was never a 0.300.0 version?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you're right, I'll clean this up in an upcoming PR (that will also do another skills bump - can't trigger the skills release right now as I'm encountering "Failed to queue workflow run. Please try again." - https://www.githubstatus.com/

Copy link
Copy Markdown

@dustinvannoy-db dustinvannoy-db left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, assuming older CLI will also work.

@jamesbroadhead jamesbroadhead enabled auto-merge May 26, 2026 15:25
@jamesbroadhead
Copy link
Copy Markdown
Contributor Author

LGTM, assuming older CLI will also work.

@dustinvannoy-db this will require the 1.0 version of the CLI - but their upgrade lifecycle is pretty good

@jamesbroadhead jamesbroadhead added this pull request to the merge queue May 26, 2026
Any commits made after this event will not be merged.
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.

5 participants