-
Notifications
You must be signed in to change notification settings - Fork 2
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
Keep track of all projects using lutaml-model #105
Comments
@HassanAkbar this is so that we know what gems we can test against to know if the latest versions of lutaml-model are backwards compatible (i.e. will any user break). |
@CAMOBAP a recent update of lutaml-model broke some of the gems. We wish to add an automated workflow that runs the tests of some external gems that we manage, such as: simple ones:
complex ones:
Can we make those part of the build process (as separate jobs)? i.e. we checkout those repositories, run their specs against our local code of lutaml-model. |
This will eventually include metanorma and modspec-ruby. But not until the integration issues for them are debugged and confirmed. |
For now, we have two approaches for testing which are 'flavor'-based in
It makes sense to make a more general approach to list repo name instead flavor and reuse it in this repo + |
Done https://github.com/lutaml/lutaml-model/actions/runs/12109210193/job/33758076323 Some repos failed |
Thank you @CAMOBAP ! |
Using:
In migration:
Pending migration:
The text was updated successfully, but these errors were encountered: