Our current GitHub Actions setup is not testing the optional dependencies we have. The current plan is to create a separate workflow that downloads and installs the dependencies. This workflow will then build and test the library as in the current workflows. Since these dependencies are not 100% in our control (their repositories may go down or change), my suggestion is to make this workflow generate warnings (like the current lint job of the Testing workflow) and not block the merge.
Our current GitHub Actions setup is not testing the optional dependencies we have. The current plan is to create a separate workflow that downloads and installs the dependencies. This workflow will then build and test the library as in the current workflows. Since these dependencies are not 100% in our control (their repositories may go down or change), my suggestion is to make this workflow generate warnings (like the current
lintjob of theTestingworkflow) and not block the merge.