chore(asm): update libddwaf to 1.19.0 #9906
Merged
Conversation
This file contains 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
christophe-papazian
added
changelog/no-changelog
|
|
Datadog ReportBranch report: ✅ 0 Failed, 175755 Passed, 1175 Skipped, 9h 53m 21.5s Total duration (18m 36.42s time saved) New Flaky Tests (1)
|
juanjux
approved these changes
Jul 23, 2024
christophe-papazian
deleted the
christophe-papazian/upgrade-libddwaf-v1.19
branch
github-actions bot
pushed a commit
that referenced
this pull request
Jul 23, 2024
update libddwaf to [1.19.0](https://github.com/DataDog/libddwaf/releases/tag/1.19.0) _no further changes in the tracer are required as this update does not contain any breaking changes._ Backporting to 2.10 to able the backend to test the new waf features while deploying 2.10rc on staging ## Checklist - [x] PR author has checked that all the criteria below are met - The PR description includes an overview of the change - The PR description articulates the motivation for the change - The change includes tests OR the PR description describes a testing strategy - The PR description notes risks associated with the change, if any - Newly-added code is easy to change - The change follows the [library release note guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html) - The change includes or references documentation updates if necessary - Backport labels are set (if [applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)) ## Reviewer Checklist - [x] Reviewer has checked that all the criteria below are met - Title is accurate - All changes are related to the pull request's stated goal - Avoids breaking [API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces) changes - Testing strategy adequately addresses listed risks - Newly-added code is easy to change - Release note makes sense to a user of the library - If necessary, author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment - Backport labels are set in a manner that is consistent with the [release branch maintenance policy](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting) (cherry picked from commit cac5e29)
2 tasks
christophe-papazian
added a commit
that referenced
this pull request
Jul 23, 2024
Backport cac5e29 from #9906 to 2.10. update libddwaf to [1.19.0](https://github.com/DataDog/libddwaf/releases/tag/1.19.0) _no further changes in the tracer are required as this update does not contain any breaking changes._ Backporting to 2.10 to able the backend to test the new waf features while deploying 2.10rc on staging ## Checklist - [x] PR author has checked that all the criteria below are met - The PR description includes an overview of the change - The PR description articulates the motivation for the change - The change includes tests OR the PR description describes a testing strategy - The PR description notes risks associated with the change, if any - Newly-added code is easy to change - The change follows the [library release note guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html) - The change includes or references documentation updates if necessary - Backport labels are set (if [applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)) ## Reviewer Checklist - [x] Reviewer has checked that all the criteria below are met - Title is accurate - All changes are related to the pull request's stated goal - Avoids breaking [API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces) changes - Testing strategy adequately addresses listed risks - Newly-added code is easy to change - Release note makes sense to a user of the library - If necessary, author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment - Backport labels are set in a manner that is consistent with the [release branch maintenance policy](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting) Co-authored-by: Christophe Papazian <[email protected]>
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.
update libddwaf to 1.19.0
no further changes in the tracer are required as this update does not contain any breaking changes.
Backporting to 2.10 to able the backend to test the new waf features while deploying 2.10rc on staging
APPSEC-54212
Checklist
Reviewer Checklist