-
Notifications
You must be signed in to change notification settings - Fork 1.7k
feat: add 'make test' to v2's workflow #3379
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll suggest you also to pin versions to well-known hashes and do not use master
for versions unless necessary.
There is a nice tool to do this.
…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-assertions
configure 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 tests
command 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 test
works again.