Issue #251: add github action to test for dependency errors#253
Merged
geourjoa merged 17 commits intoTETRAS-IIIF:mainfrom Apr 15, 2026
Merged
Issue #251: add github action to test for dependency errors#253geourjoa merged 17 commits intoTETRAS-IIIF:mainfrom
geourjoa merged 17 commits intoTETRAS-IIIF:mainfrom
Conversation
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Collaborator
Author
|
NOTE: testing but, when i run |
Contributor
There is perhaps something we can do with I will try something |
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
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.
hi @geourjoa
this is my solution for: #251 (comment)
i added a github action that tests that the
package.jsoncan be installed successfully.i can't test the actual NPM package installation because that would need a new version of MAE to be published through NPM before merging the PR, which would be a big/weird change to your current workflow.
thanks !