-
Notifications
You must be signed in to change notification settings - Fork 56
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 known branch exceptions to version matching #242
Conversation
@josevalim, @grzuy, this adds an exception (to loose version matching) for "known" branches |
@@ -10292,6 +10292,10 @@ function isRC(ver) { | |||
return ver.match(xyzAbcVersion('^', '(?:-rc\\.?\\d+)')) | |||
} | |||
|
|||
function isKnownBranch(ver) { | |||
return ['main', 'master', 'maint'].includes(ver) |
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.
If you want to be safer, you could match "maint" anywhere in the version, as OTP has maint-26, maint-25, and so on. :) Just saying, your call, we don't use it right now.
Looks great, thank you! |
67f7a17
to
980f47e
Compare
Maybe doing it this way is better, since we don't "break" existing consumption elements Forcing `version-type: strict`, while explicit, would probably force some installations to use a too-specific Elixir version
4d5fc33
to
7100c00
Compare
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.
LGTM!
Perfect stuff. Thanks @starbelly. I'll release a patch now. |
v1, v1.17 and v1.17.1 released, pointing to the latest commit. |
Description
Maybe doing it this way is better, since we don't "break" existing consumption elements, while just adding to already existing exception
-rc-
.Forcing
version-type: strict
, while explicit, would probably force some installations to use a too-specific Elixir version, so we "fix" what we had to prevent that.Closes #241.