feat: add 'make test' to v2's workflow#3379
feat: add 'make test' to v2's workflow#3379airween merged 2 commits intoowasp-modsecurity:v2/masterfrom
Conversation
…d packages Co-authored-by: Felipe Zipitría <[email protected]>
|
Sorry to ask, what is the advantage of using this form? Why isn't good to use the current |
Supply chain attacks? See: |
Thanks. If I'm right, if we use hash's then we should have to care with new releases. I think this PR is outside of this, so can we skip this change now? Later I try to align these as you suggested with other necessary configuration. |
|
Sounds good. Renovatebot can take care of that, let's do it in a different pr then. |



what
This PR adds mod_security2 module's own test cases to the GH workflow.
The new job uses the same matrix as the existing one, but we can't use
--enable-assertionsconfigure option (which is important with the valid configuration, where we do not use invalid values), because then the test cases which check invalid values would throw an assert error.why
The module's
make testscommand hasn't been working for some time, because the PCRE2 modifications weren't applied that code. With some recent PR's those part of code were aligned, somake testworks again.