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

Use SemVer versioning instead of MAJOR.MINOR #391

Open
clemlesne opened this issue Oct 16, 2023 · 2 comments
Open

Use SemVer versioning instead of MAJOR.MINOR #391

clemlesne opened this issue Oct 16, 2023 · 2 comments
Labels
t-platform Issues with this label are in the ownership of the platform team.

Comments

@clemlesne
Copy link

During my GitHub Actions builds, I'm using a shared version number (binaries, containers, serverless, doc, …). The version is formatted with the SemVer norm, x.y.x-a.b.

I cannot use my version number with the Apify CLI build because it returns the error Error: Version number must be MAJOR.MINOR, where MAJOR and MINOR is a number in range from 0 to 99..

Versions:

  • apify-cli/0.18.1
@mtrunkat
Copy link
Member

Hi @clemlesne, thank you for reporting this. Unfortunately, semantic versioning, as described, is not currently supported. However, we plan to fix this and introduce the new versioning system for Actors with the support of SemVer. I don't have an exact date yet.

CC @fnesveda

@mtrunkat mtrunkat added the t-platform Issues with this label are in the ownership of the platform team. label Oct 18, 2023
@clemlesne
Copy link
Author

I see. This constraint would be important for me to be resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
t-platform Issues with this label are in the ownership of the platform team.
Projects
None yet
Development

No branches or pull requests

2 participants