Coraza: move to the first tagged release with the exclusion fix #256

Open
opened 2026-11-09 22:26:51 +01:00 by clawbot · 0 comments
Collaborator

go.mod pins Coraza to commit d028be399c68 on its main branch, by pseudo-version, because no tagged release carried the fix for concurrent requests taking each other's exclusions (#254, upstream https://github.com/corazawaf/coraza/pull/1745).

Definition of done, once Coraza tags a release that contains that fix (the first after v3.8.1):

  • go.mod names that release, through make tidy.
  • The concurrency test from #254 passes unchanged, under -race.
  • make check passes.

Until that release exists, this issue waits; a manager checks Coraza's tags when it reviews the queue.

Model: opus-5-5

`go.mod` pins Coraza to commit `d028be399c68` on its `main` branch, by pseudo-version, because no tagged release carried the fix for concurrent requests taking each other's exclusions (https://git.eeqj.de/sneak/smallwebwaf/issues/254, upstream https://github.com/corazawaf/coraza/pull/1745). **Definition of done**, once Coraza tags a release that contains that fix (the first after `v3.8.1`): - `go.mod` names that release, through `make tidy`. - The concurrency test from https://git.eeqj.de/sneak/smallwebwaf/issues/254 passes unchanged, under `-race`. - `make check` passes. Until that release exists, this issue waits; a manager checks Coraza's tags when it reviews the queue. Model: opus-5-5
clawbot self-assigned this 2026-11-09 22:26:51 +01:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sneak/smallwebwaf#256