Release-cycle step 7, in its own dedicated commit as required by README:
a baseline move never rides along with a feature change.
`baselines/latest.json` is replaced with the `benchmark-linux-php8.4`
artifact from the CI run on the tagged commit `df9ca33` (run 37872132328)
-- PHP 8.4.26, Linux x86_64, size 500000, iterations 7, suite `all`,
reporting judy_version 2.8.0, matching the parameters of the baseline it
replaces. The `pie install orieg/judy:` pin in `.github/workflows/ci.yml`
moves 2.6.0 -> 2.8.0 now that 2.8.0 resolves on Packagist / PIE.
The interleaved comparison this baseline supersedes, 2.6.0 -> 2.8.0 on the
same runner (5 groups x 5 rounds x 2 arms | 250s):
Interleaved comparison: 2.6.0 -> 2.8.0 | 5 groups x 5 rounds x 2 arms | 250s
Run-wide median delta: +0.44% (PHP-array control +0.01%) -> clean
Summary: 0 faster, 0 regressions, 100 unchanged, 0 unstable, 0 new, 0 removed
The PHP-array control at +0.01% rules out runner contention, and 0
regressions confirms behavior tightening, strict validation, and memory-safety
fixes across 2.8.0 carry no measurable performance overhead.
Summary
Release-cycle step 7, in its own dedicated PR as required by README: a baseline move never rides along with a feature change.
1. What changed and where
.github/workflows/ci.yml: Bumppie install --skip-enable-extension orieg/judy:2.6.0to2.8.0.baselines/latest.json: Replaced withbenchmark-linux-php8.4artifact from CI run on tagged commitdf9ca33(run 37872132328).2. What was verified by running
orieg/judy:2.8.0is published and indexed on Packagist.3. Invariants preserved
4. Downstream impacts
allow-golden-update: baselines/latest.json 2.8.0 baseline update from CI run on tagged commit df9ca33
allow-regression: baselines/latest.json 2.8.0 baseline update from CI run on tagged commit df9ca33