-
Notifications
You must be signed in to change notification settings - Fork 111
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
Cannot install package with prerelease identifier containing x
#1518
Labels
bug
This issue describes a defect or unexpected behavior
carvel-accepted
This issue should be considered for future work and that the triage process has been completed
Comments
I am now versioning that package with |
🤣 As always, thank you so much for being amazing and looking into this ❤️ |
mamachanko
added a commit
to mamachanko/kapp-controller
that referenced
this issue
Apr 17, 2024
fixes carvel-dev#1518 Signed-off-by: Max Brauer <[email protected]>
mamachanko
added a commit
to mamachanko/kapp-controller
that referenced
this issue
Apr 17, 2024
fixes carvel-dev#1518 Signed-off-by: Max Brauer <[email protected]>
This was referenced Apr 17, 2024
Merged
supposed to be fixed by #1534 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
This issue describes a defect or unexpected behavior
carvel-accepted
This issue should be considered for future work and that the triage process has been completed
What steps did you take:
Install a package with prerelease identifier containing
x
, saytest.example.com/0.1.0-experimental
.What happened:
The present
x
trips carvel-dev/semver into applying wildcard logic. But it's not a wildcard. There are no wildcards in prerelease identifiers.What did you expect:
It install the package.
Anything else you would like to add:
The issue originates in github.com/carvel-dev/semver and gets exposed to kapp-controller through github.com/carvel-dev/vendir. There is the existing carvel-dev/vendir#123 which is now ~3 years old. Therefore I am bringing it up here again.
The problem is that the issue goes down so deep and the error message
Parsing version constraint '0.1.0-experimental': Could not get version from string: "<"
is incomprehensible unless one knows what's going on.[Additional information that will assist in solving the issue.]
Environment:
v0.48.2
Vote on this request
This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.
👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"
We are also happy to receive and review Pull Requests if you want to help working on this issue.
The text was updated successfully, but these errors were encountered: