* Do a bit of YAMLlint'ing
* Ease consumer cache invalidation
By providing an output with the action version we ease
cache invalidation on consumer, due to the fact we can
now stop worrying about changes to the action's cache itself
Might also be interesting for self-hosted runners...
* Remove duplicates
* Do further validations for robustness
* Make iterating over mirrors more flexible (and reusable)
At the same time we fix an error, where we aren't using the
mirrors for the OTP build :)
* Make installation of cache-based tool callback -based
This hopefully eases introduction of new languages at the cost
of a bit of abstraction (there's an extensive comment on how to
fill in the install options' object)
We'll soon test this abstraction by making Gleam and rebar3
cached too
* Increase our visibility when debugging
* Improve on lessons learned to ease incorporation of further caches
(starting with Gleam on Linux)
* Cache Gleam on Windows
* Cache Rebar3 on Linux
Also, gets rid of all .sh
* Cache Rebar3 on Windows
Also, gets rid of all .ps1
* Act on CI results
And also be consistent when it comes to using
fs....Sync vs fs.promise....
* Move tests to a single file
* Move main executable to a single file
* Decrease number of changes to ease review
* Expose function required for tests
* Don't async/await when not required
* Resolve post- merge-conflict resolution issues
* Update some dependencies' versions (also, get rid of husky)
* Introduce branch dependency execution
We want the most important things to fail first and prevent the
other ones from executing
e.g. if your dist/ is not updated, there's no point seeing the tests fail
* Rid ourselves of bloat
* Introduce expectations for upcoming version
* Tweak whitespace
* Tweak our calls to getVersionFromSpec (increase code consistency)
* Remove non-used variable
* Start coercing on input, stop sorting/maybe prepending 'v' on input
We'll deal with all this in a centralized place to make
it easier to reason on the code
* Revamp our getVersionFromSpec
1. stop accepting maybePrependWithV0, since this is only used in specialized
cases
2. sort versions internally (don't expect it to come sorted)
3. compare rc/strict and .includes in a single go (don't separate these)
4. don't expect already coerced version arrays, coerce them when required
(the maybeCoerced version had changed already, which means we're smarter
at putting stuff inside the version array)
5. raise an exception if a semver-invalid version is not flagged as strict
* Reduce our expectations, but still be appropriate to our mission
* Update our tests for our new expectations (start the TDD bit)
* Execute npm run build-dist and keep results
* Increase inter-job dependency
* Don't expect markdownlint to be installed remotely
* Revert "Increase inter-job dependency"
This reverts commit 500b0fe7e9eec1c4f258b4d16b40719ee1d0a1ad.
* Revert "Introduce branch dependency execution"
This reverts commit fbe1317a800d7722f4e8b668c073218263d0ab17.
* Have all the CI workflows run under the same conditions
* Fix as per CI results
* Re-establish the possibility to match versions like 22.3.4.2.1.0
We cheat on the semver matching:
1. we keep an ordered list of versions that respect e.g. 22.3.4
2. if we match 22.3.4 when fetching a version, we get the last value
from the list of versions that respect it, e.g. 22.3.4.2.1.0
(since this is ordered, it should work as previously expected)
This increases code complexity for getVersionFromSpec,
but hopefully not by much...
We also remove throw-based test cases (non-versions will fail later,
with null), and add some tests to prove our need code.
* Trim out linting practices
But still keep them useful
* Add more stuff to test on
* Tweak our debugging (more verbose when the runner is in debug mode)
* Hopefully make it easier to debug
* Have the distribution work :-)
* Adapt to a better reality
* Fix OTP version null check
* Revert "Fix OTP version null check"
This reverts commit 2c433c16ac.
* Check that the resolved versions contain the spec.
* Only perform semver version resolution when spec is not an rc and version-type is not strict
* Move version inclusion check to the end of the function, when we may have prepended a 'v'
* Refactor function return
* Add test case for strict version resolving a spec that is no available version
* Link to the elixir/erlang compatibility page
Currently when a user encounters an incompatibility between the
requested elixir and erlang versions it isn't clear how to figure out
what the compatible versions are. This is the current error as shown to users:
> Error: Requested Elixir / Erlang/OTP version (1.11.3 / 24.2) not found in version list (did you check Compatibility between Elixir and Erlang/OTP?)
Example failure: https://github.com/ScenicFramework/scenic/pull/318/checks
This PR adds a link to
https://hexdocs.pm/elixir/compatibility-and-deprecations.html so user's
can easily see what versions are compatible.
* Update dist/index.js
* Act on review comment: on > at
---------
Co-authored-by: Paulo F. Oliveira <paulo.ferraz.oliveira@gmail.com>
* Enable debug for OTP versions' listings
* Make it easier to detect
* Prevent error annotation on expected error
The fact that one mirror fails in the above test and others follow
working is test enough for me
A single failing mirror should fail, but it's confusing to have
an error annotation for a success (via continue-on-error) while
not being able to suppress it via GitHub Actions
* Trying to figure out why we have a rebar_core exception
Might simply be that the bug is already fixed and we need to bump rebar3
* Try to debug into non-JSON input
* Prevent error in rebar_core
We're getting Access Denied for
Fetching registry from "https://repo.hex.pm:443/registry.ets.gz?"
* Try to figure out what's breaking tests
* Make jsonParse(...).map failure more understandable
* Ease test maintenance
* Tweak folder structure while moving console._ to core._
* New option to work with one or more hex.pm mirrors
Add a new option called `hexpm-mirrors` for one or more hex.pm mirrors.
Default list is `builds.hex.pm`, so behavior is unaffected unless option is
used.
Signed-off-by: Paul Guyot <pguyot@kallisys.net>
* Implement suggested rewording changes from @paulo-ferraz-oliveira
Co-authored-by: Paulo F. Oliveira <paulo.ferraz.oliveira@gmail.com>
Signed-off-by: Paul Guyot <pguyot@kallisys.net>
---------
Signed-off-by: Paul Guyot <pguyot@kallisys.net>
Co-authored-by: Paulo F. Oliveira <paulo.ferraz.oliveira@gmail.com>
In my Windows 11 test environment, using Powershell Core 7.3.4, I get
the following message while running similar code to what this github
action uses:
```
Installed Elixir version follows
InvalidOperation: C:\Users\vagrant\setup-beam\src\test.ps1:4
Line |
4 | & "${DIR_FOR_BIN}/bin/elixir" "-v" | Write-Output
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| Cannot run a document in the middle of a pipeline: C:\elixir\bin\elixir.
```
Adding `.bat` fixes the issue. This is probably not the root cause of
erlef/setup-beam#189, however.
* Provide an input for github tokens
- By providing an input for github tokens with a default users no longer have to pass
the github token via their environment across workflows.
- Remove GITHUB_TOKEN from our environment in all workflows
* Don't run workflows on main on pull requests
Co-authored-by: Paulo F. Oliveira <paulo.ferraz.oliveira@gmail.com>
* Repeat request on error (while logging it)
* Test one change at a time
* Conditionally authorize requests
This seems to affect Windows builds, so might not be the best solution,
but we're trying to isolate the issue to move forward
* Act on CI results
* Ease consumption via a JSON.parse wrapper
We still throw the error, but in a more controlled manner
* Act on CI results
* Check behaviour on Windows pre- Gleam 0.23
* Increase consistency with .sh counterpart
* Support older versions (pre 0.22.1) on Windows
* Increase inter-script consistency
* Run `npm run build-dist`
* React to CI results
* Provide a working rebar.cmd for system that need it
(Windows on non-PowerShell)
* Add tests for recent changes
If the "run" were to fail the job would too
* Check if Rust can find it
* feat: add escripts to path
* Update src/install-elixir.ps1
Co-authored-by: Paulo F. Oliveira <paulo.ferraz.oliveira@gmail.com>
* add github action combo to test escript
* force install
* use os homedir for escript install path
Co-authored-by: Paulo F. Oliveira <paulo.ferraz.oliveira@gmail.com>
* Ease consumption by means of .tool-versions
* Update as per self-review
* Update as per self-review
* Act on CI results
* Act on CI results
* Act on CI results
This value is check by code, in any case
* Act on CI results
* Act on CI results
* Act on CI results
It appears we can't install Elixir twice on Windows, but can
on Ubuntu; this is outside the scope of this branch's context
so I won't fix it now
* Tweak visual consumption elements
* Ease potential future maintenance and/or update
* Update all our deps
Get rid of warnings such as:
* `save-state` will be deprecated
* `set-output` will be deprecated
* nodejs 12 is being deprecated
...
Rely on tests to make sure the actions still works
* Fix as per CI results
* Get rid of deprecated containers
* Have a warningless run
We're not testing rebar3 here, in any case
* Check tests failing for something that should pass
* Test with version-type: strict
* Add more tests
GitHub actions is refusing to run a given workflow :shrug
* Try to fix new test that shouldn't be failing
Which is exactly what we intended to originate by starting a new
pull request.
* Fix tests as per CI
* Fix tests as per CI
* Adapt to "latest"
* Fix as per CI results
Actions' window shows everything as Ok but then internals not
Error when evaluating 'runs-on' for job 'integration_test'. .github/workflows/ubuntu.yml (Line: 19, Col: 14): Unexpected type of value '', expected type: OneOf.
Strange one, this one!
* Try to "help" for non-OTP declared input
We do this for OTP-, but not for maint-
as the former is hopefully more common
than the latter
* Introduce `latest` to signify `master`
Semantically they're similar, but with `latest` we know:
1. to fetch Elixir's no-otp-... version
2. to fetch Erlang's master
whereas with 25 (latest at this moment) we'd
try to fetch elixirvsn-otp-25 which could fail with
Elixir master and version-type strict
* Fix as per CI
Still not 100% convinced that `latest` should be separate from `master`
but I want to know how tests run, in this case in particular
* Fix as per CI
* Fix as per CI
* Revert potential wrong decision
* Fix as per understand recent Elixir changes (namely master v. main)
* Try to simplify it
We introduce the concept of version v. branch (as per @ericmj)
and we use that to find the most appropriate Erlang/Elixir combo.
* Prevent "future" errors when choosing incompatible Elixir v. OTP versions
* Fix tests as per GitHub Actions' output
* Make test elixir `master` strict
It has no -otp- in the name
* Update for latest Gleam
- Gleam releases now use LLVM triplets for platforms so the download
URLs have been updated accordingly.
- Gleam's rebar3 support has been removed.
This change means that future versions of this action cannot download
older versions of Gleam. I can make it backwards compatible, but I will
need help from someone who can convert the shell script into PowerShell
for Windows.
* Support older Gleam versions
* Remove rebar from Gleam
Don't take `maint-` -prefixed versions into account unless they're asked for it
specifically
At the same time, while fetching versions, make sure we identify them better so that
25 does not end up pulling maint-25 instead of OTP-25.0, as it should
* Add Erlang/OTP 25+ (not RC) to tests
* Test a specific combo
And a strict version
* Allow testing "edge" cases
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)
GitHub Actions