Skip to content

Conversation

@volodymyrZotov
Copy link
Contributor

This PR renames version input to cli-version to make it more obvious about which version we are talking about.

It defaults to latest if not provided.

In the future releases when we will migrate from CLI to SDK, the cli-version will be deprecated. And we will introduce a warning about future depreciation, close to that moment.

required: true
type: boolean
version:
cli-version:

Choose a reason for hiding this comment

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

hmm if we are already recgonizing that the SDK is going to be supported here soon enough, is this change even necessary? Seems like more work as when the SDKs get introduced this has to be fixed again

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Great question!

I thought introducing version would be a nice to have feature, especially as we give it for free as of using op-cli-installer package.

Having version input in the action would be useful in case latest CLI release has a regression, so users can start using older version of the CLI without the issue.

On another hand, as you fairly mentioned, as we move toward using SDK instead of CLI, that seems as additional work. Considering the fact that current load-secrets-action@v2 uses latest cli version as default, maybe we do not need to introduce this additional input at all and should remove it?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Though, considering the fact that we do not know exact timeline when we switch to SDK, I feel that cli-version input this is something nice to have until that.

Copy link

@MOmarMiraj MOmarMiraj Aug 14, 2025

Choose a reason for hiding this comment

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

my point is why can't users just treat version as the cli_version and we can put a comment above it instead and treat it as such until the SDK comes out. Changing it everywhere seems like a lot of work when we know we are going to migrate to the SDKs soon and then change this again.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I see your point.

Especially as we already have a description in the action.yml

  version:
    description: Specify which 1Password CLI version to install. Defaults to "latest".
    default: "latest"

Ok, let's close this PR and stick with version

@volodymyrZotov
Copy link
Contributor Author

After discussion decided to not merge it to not bring more changes as we already have a description for the version tag which clearly says what this version for.

  version:
    description: Specify which 1Password CLI version to install. Defaults to "latest".
    default: "latest"

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.

3 participants