* 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>
* Add some more error logging
* `npm run build`
* Make the message more concise
* Remove the trailing newline at the very end of the last line of the error message
* `npm ci && npm run build`
* 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>
* use windows tar, not git bash one
* correct manual patch
* rebuild
* Update src/installer.ts
Co-authored-by: Dilum Aluthge <dilum@aluthge.com>
* Update installer.js
* Include the direct URL of the issue (not just the issue number)
* npm run build
---------
Co-authored-by: Dilum Aluthge <dilum@aluthge.com>
Co-authored-by: Viral B. Shah <ViralBShah@users.noreply.github.com>
* fix aarch64 urls for nightly
* rebuild js for aarch64 nightly
* test nightly on apple m1 (aarch64)
* Run on more macOS versions, and add a few comments
---------
Co-authored-by: Dilum Aluthge <dilum@aluthge.com>
* On macOS, first try to find a tarball (`.tar.gz`) file, but fall back to `.dmg` if we can't find a tarball
* Add an "Example builds" job for Julia 1.2
Setting the `arch` input to `aarch64` will install `aarch64` binaries,
intended to be used on aarch64-based self-hosted runners.
Please note that we currently don't run test builds on that
architecture, so we cannot guarantee that the input won't break
randomly, although there is no reason why it would.
In a future update, we may choose a default architecture based on the
arch of the runner.
Thanks to @giordano for providing a self-hosted runner for testing.
Co-authored-by: Mosè Giordano <mose@gnu.org>
* Support release nightlies
See #62
* Replace == nightly with endsWith nightly
* Use majorMinorMatch, not full match
* Replace more (in-)equality checks
* Reduce number of duplicate CI builds
* Add example to docs
* Tidy up nightly conditions
