add doc comment regarding how to pick nim versions #38
Comments
There is not that function. |
|
see nim-lang/fusion#70 (comment) alaviss/[email protected] allows using |
jiro4989
added a commit
that referenced
this issue
Jan 7, 2021
* add empty functions * fix * install compare-versions * install node-fetch * wip * wip * wip * add test code * wip * wip * wip * remove node-fetch * implements patch version * format * tsc * add typescript test job * add 'v' prefix * format * tsc * add test case * format * implements minor version * add test case * tsc * update validations * format * add test case * tsc * update test case * add export * add test case * tsc * update test description * update test code position * format * add match version functions * format * tsc * add test cases * implements glob * tsc * add test case * add info message * tsc * add request header * format * tscv * fix code * format * tsc * fix * tsc * fix * format * tsc
jiro4989
added a commit
that referenced
this issue
Jan 7, 2021
|
@timotheecour |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
as shown in nim-lang/fusion#67, we should pick latest of each branch, so 1.2.0 is probably not what users would want to test (instead, 1.2.8 currently)
is there a way to test for latest stable for 1.2.x branch? that would be the ideal to avoid having to change up a new release
The text was updated successfully, but these errors were encountered: