Skip to content

Conversation

@sebastiw
Copy link

@sebastiw sebastiw commented Oct 2, 2025

Description

Re-opened #313 with review fixes

Example on how one can maintain a compatibility matrix.
Note I've not tested keeping the os-version in the strategy itself, but according to the github documentation it works for the runs-on argument as well.

I'm currently running otp-rebar pinning for another project for OTP22-OTP27 versions below.
And I ran a similar thing (though not with erlef/setup-beam) previously for the same project for OTP17-21.

I'll add the os-version to my project for testing, but I wanted early feedback on your thoughts.

sebastiw and others added 6 commits December 20, 2024 08:47
Example on how one can maintain a compatibility matrix
Co-authored-by: Kian-Meng Ang <kianmeng.ang@gmail.com>
Apparently rebar3 has started to maintain a version compatability table themselves. Missing older versions though

| 3.10.0 | 17         |
| 3.11.1 | 18         |
@sebastiw sebastiw changed the title Patch 1 Compatibility matrix strategy Oct 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants