Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add version: latest to automatically download the latest version #38

Open
Kerumen opened this issue May 20, 2024 · 6 comments
Open

Add version: latest to automatically download the latest version #38

Kerumen opened this issue May 20, 2024 · 6 comments
Assignees

Comments

@Kerumen
Copy link

Kerumen commented May 20, 2024

Similar to the Expo GitHub Action, add a new string latest for the version parameter to avoid specifying a version number and ensure the CLI is always updated.

@jablan
Copy link
Collaborator

jablan commented May 21, 2024

@Kerumen if I understand correctly, you would like to be able to default to the latest release, when the version hasn't been specified?

@Kerumen
Copy link
Author

Kerumen commented May 21, 2024

Yes that's correct :) To avoid having to update all of our workflows everytime a new version is published.

@jablan
Copy link
Collaborator

jablan commented May 21, 2024

Makes sense. I'll open an internal ticket for that, it's a small change so I expect it to be picked up soon.

@jablan jablan self-assigned this May 21, 2024
@tkrotoff
Copy link

+1

We have the same issue, Phrase CLI asks to be updated regularly in our CI:

Please consider updating the Phrase Strings CLI client (2.31.2 < 2.32.0)
You can get the latest version from https://phrase.com/cli.

We would like to be able to set

with:
  version: latest

(should be the default if no version is specified IMHO)

@jablan
Copy link
Collaborator

jablan commented Sep 23, 2024

hey @tkrotoff @Kerumen seems that the change necessary is bigger than initially assumed, therefore we couldn't fit it in yet. would it in the meantime help to optionally disable the warning message?

@tkrotoff
Copy link

@jablan

optionally disable the warning message?

I would keep the warning message: this is not a big issue, it's just boring

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

No branches or pull requests

3 participants