Enable wildcards for the version field

Open
#178 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions, shell
Domain
ci-cd, cli

Research direction

No files or tests are named in the issue. Start by locating the action entry point and the code that validates or resolves the CLI version field, then trace how a pinned version such as 1.9.0 is handled. Done means a wildcard such as 1.9.* is accepted and selects a compatible CLI version without requiring workflow edits for each revision.

Written by the indexing model from the issue text.

Description

This will help you choose the most compatible version of the CLI instead of pinning to a particular version. In general, the changes in Databricks CLI are not fully compatible with semantic versioning (We had some issues in the past that a change in minor version was a breaking change from the previous state, which is annoying).
I propose to enable wildcards for version so that the action can automatically pick the most compatible version for that. An example would be instead of 1.9.0, we can choose 1.9.* so we are still in the same version bracket, but we can skip the hotfixes and revisions without any need to constantly change the version number.

Dominant language
Shell
Stars
29
Forks
19
Avg merge
3m
Merged PRs (30d)
6

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from databricks/setup-cli

All issues in databricks/setup-cli

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.