Add '--skip-interpro-version-check' parameter to control compatibility checks#294
Merged
matthiasblum merged 6 commits intomainfrom Jan 30, 2026
Merged
Add '--skip-interpro-version-check' parameter to control compatibility checks#294matthiasblum merged 6 commits intomainfrom
matthiasblum merged 6 commits intomainfrom
Conversation
matthiasblum
changed the title
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
2 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.
Add a new
skipInterproVersionCheckparam (and--skip-interpro-version-checkCLI flag) to bypass InterProScan-InterPro data version compatibility enforcement.Until versions.json is updated on release day, passing the new version of InterPro after
--interpro XXX.Ywould cause InterProScan 6 to fail. This new param allows to bypass this check.The GitHub action for linting was failing, possibly because linter-rules-for-nextflow requires a newer version of
gradle. I rewrote the GitHub actions to use the officially publishedlinter-rules-for-nextflowDocker image. Instead of disabling specific rules by editing the rule files at CI time, they are disabled directly in the code via comments.