Compatibility matrix strategy#389
Merged
paulo-ferraz-oliveira merged 8 commits intoerlef:mainfrom Mar 14, 2026
Merged
Conversation
Example on how one can maintain a compatibility matrix
Apparently rebar3 has started to maintain a version compatability table themselves. Missing older versions though | 3.10.0 | 17 | | 3.11.1 | 18 |
Schultzer
approved these changes
Oct 2, 2025
paulo-ferraz-oliveira
approved these changes
Feb 28, 2026
Collaborator
|
If CI passes I'm merging this to the main branch, but not tagging yet (also, not really relevant, since this is a generic consideration, not part of the actual executed code). |
paulo-ferraz-oliveira
requested changes
Feb 28, 2026
Collaborator
paulo-ferraz-oliveira
left a comment
paulo-ferraz-oliveira
left a comment
There was a problem hiding this comment.
Per CI output you should run npm run build-dist, fix until Ok, then push.
Apply changes to resolve linter warnings Co-authored-by: Paulo F. Oliveira <paulo.ferraz.oliveira@gmail.com>
paulo-ferraz-oliveira
approved these changes
Mar 14, 2026
Collaborator
|
Pushed a minor commit to resolve linter warnings. If the basic CI passes, I'm merging. |
Collaborator
|
Merging... thanks. |
Collaborator
|
This was published in v1.23.0. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.