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

Major semver tag #145

Open
jimmymcpeter opened this issue Apr 25, 2024 · 2 comments
Open

Major semver tag #145

jimmymcpeter opened this issue Apr 25, 2024 · 2 comments

Comments

@jimmymcpeter
Copy link

Would it be possible to add and maintain a major semver tag? For example, as of writing this, v2 would match the latest 2.25.0 release. If you release 2.26.0 next week, then v2 would then be updated to match that. I currently use the Phrase CLI from the phrase/setup-cli GitHub Action and am trying to reduce the manual update maintenance.

@theSoenke
Copy link
Collaborator

Hi @jimmymcpeter, maybe this could also be solved by introducing a latest version in the setup-cli GitHub action. And major CLI versions would then also be a major GitHub action version. But in your case do you actually always need the latest feature of the CLI? Most updates introduce for example new endpoints but if you don't always need the most recent API additions older v2 version might be sufficient as well

@jimmymcpeter
Copy link
Author

jimmymcpeter commented Apr 29, 2024

Hi, unfortunately I wouldn't use latest because it doesn't avoid major semver (breaking) changes. I'd prefer to pass version: 2.x to the phrase/setup-cli action if you didn't want to do a v2 tag on the phrase-cli repo. The actions/setup-node action supports semver like this along with aliases like latest if you want to take a look -- https://github.com/actions/setup-node/blob/main/src/distributions/installer-factory.ts#L15

But in your case do you actually always need the latest feature of the CLI?

To sum it up, I'd like to get minor and patches automatically. Dependabot can't automate this since you must pass an explicit version to phrase/setup-cli. Every time you release a new CLI, my logs are constantly printing "Please consider updating the Phrase Strings CLI client (xxxx < 2.26.0). You can get the latest version from https://phrase.com/cli." until I go update the version by hand.

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

2 participants