You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
well, i personally think its the latter. i don't consider 1.2.3.1 > 1.2.3 ambiguous (since "1.2.4 and above" is expressly>=1.2.4), but i agree it'll catch someone by surprise.
i suppose the other option would be to get fancy and support something like:
- if: next_patch(1.2.3)
- if: next_major(1.2.3)
that's what github would do.
edited to add: i was using > specifically because i wasn't in a >=2.426.4 situation trying to exclude a single version. perhaps a negation operation would have been simpler, but yuck.
Activity
mxcl commentedon Jan 24, 2024
we don’t support
>since it is ambiguous what the user means.eg.
> 1.2.3will allow1.2.3.1but you probably mean1.2.4and aboveProbably the error message should state that or we should just allow
1.2.3.1and it's your own fault. What you think?jhheider commentedon Jan 24, 2024
well, i personally think its the latter. i don't consider
1.2.3.1 > 1.2.3ambiguous (since "1.2.4 and above" is expressly>=1.2.4), but i agree it'll catch someone by surprise.i suppose the other option would be to get
fancyand support something like:that's what github would do.
edited to add: i was using
>specifically because i wasn't in a>=2.426.4situation trying to exclude a single version. perhaps a negation operation would have been simpler, but yuck.