-
Notifications
You must be signed in to change notification settings - Fork 57
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
Test on top of Erlang/OTP 25+ (not RC) #118
Test on top of Erlang/OTP 25+ (not RC) #118
Conversation
This was done because of a test to an issue, a few minutes ago. In any case, it's an extra confidence boost 😄 |
And a strict version
We weren't taking our own considerations into account for version strictness We want to be able to test cases where we use -otp- (if the consumer is doing it, at least they have to use _strict_ to assert their decision)
@@ -6193,7 +6193,7 @@ async function getOTPVersion(otpSpec0, osVersion) { | |||
const otpVersions = await getOTPVersions(osVersion) | |||
const otpSpec = otpSpec0.match(/^(OTP-)?([^ ]+)/) | |||
let otpVersion | |||
if (otpSpec[1]) { | |||
if (otpSpec[1] && !isStrictVersion()) { |
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.
This was just us being super strict with input, but for the edge case being tested we do want to allow "Using -otp- or OTP-", even though it is to be made explicit via the version-type option.
@paulo-ferraz-oliveira Approved, but left it open so you can squash as you like. |
No description provided.