* Support the special version "MIN"
* Support JULIA_PROJECT
* Add tests
* Add forgotten test fixtures
* Get latest prerelease/release
* No special pre-release behaviour
* Add test for NPM semver difference
* Robust test suite
* Disallow less-than-equal
* Refactor validJuliaCompatRange to return a validRange
* Rename MIN to min
* Rename getProjectFile to getProjectFilePath
* Comment on "project" input
* Additional tests for getProjectFilePath
* Add comment on `juliaCompatRange`
Co-authored-by: Dilum Aluthge <dilum@aluthge.com>
* Update dependencies
---------
Co-authored-by: Dilum Aluthge <dilum@aluthge.com>
* improve example versions and note
* add info if user explicitly sets version to 1.6
* npm run build
* add 1.6 explicitly to CI
* convert to a github actions notice
* try core.notice
* npm run build
* Apply suggestions from code review
Co-authored-by: Dilum Aluthge <dilum@aluthge.com>
* Update action.yml
* update example
* update toc
* npm build
---------
Co-authored-by: Dilum Aluthge <dilum@aluthge.com>
* If the user provides `default` as the value of the `arch` input, use the runner machine's architecture
* `npm run build`
* Convert the key `processedArchInput` to lower case before indexing into the `archSynonyms` dict
* `npm run build`
---------
Co-authored-by: Ian Butterworth <i.r.butterworth@gmail.com>
* update tests to latest `versions.json`
* allow specifying the version as `lts` to install the latest LTS version
for now, this just hardcodes the LTS version in the source (similar to how juliaup does it) since the latest LTS is not available in `versions.json`. Since the LTS is updated so rarely this might be ok for now.
* add a 'pre' version
* Run `npm ci` followed by `npm run build`
* Add a CI job to test `pre`
---------
Co-authored-by: Viral B. Shah <ViralBShah@users.noreply.github.com>
Co-authored-by: Dilum Aluthge <dilum@aluthge.com>
