Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
binenv only accepts semver formatted versions. hence, edge-X.Y.Z is not possible to solve this, we excluded "edge" versions, keeping only "stable" ones. relates to #231
- Loading branch information
Showing
2 changed files
with
3 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -1493,6 +1493,7 @@ | |
"1.11.1", | ||
"1.11.0", | ||
"1.10.2", | ||
"1.10.1", | ||
"1.10.0", | ||
"1.9.1", | ||
"1.9.0", | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
99386aa
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apologies if this is just my not understanding this, but the release versions are actually named "stable-x.x.x" or "edge-x.x.x", so unless binenv is parsing the release names and extracting the portion that does comply with SemVer format this will be returning
stable-stable-x.x.x
.99386aa
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, I've just seen c926ac8 😞
Does this mean it's a solid no for Linkerd in binenv?
99386aa
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am sorry to say that, unfortunately, it is not possible atm
We might have to implement some kind of version pre-parsing I guess to make it work, but that would be clumsy and might have big side effects
I am too busy right now to tackle this and there are many other issues that deserves my attention too
If you feel like taking a shot at it, we can talk about it.
99386aa
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not a problem, thanks for the time you've spent on it and apologies for [unintentionally] breaking things!
I'll see if I can get some time to put into it.