Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compatibility matrix strategy #313

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

sebastiw
Copy link

Description

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.

Example on how one can maintain a compatibility matrix
@sebastiw
Copy link
Author

ofc we can rename the erlang-variable (as in e.g. matrix.erlang.otp) to anything else, compat might be a better fit?

erlang:
- otp: "17"
rebar3: "3.10.0"
os: ubuntu-18.04
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ubuntu-18.04 is no longer available.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok, I'll remove OTP17-20 from Readme.

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