[szibis]

#597 merged after the v1.87.0 metadata sync (#601), from a head that predated it. The merge placed #597's entry inside the released ## [1.87.0] section and left ## [Unreleased] empty, so:

• the CHANGELOG says v1.87.0 contains a change it never shipped (v1.87.0 was cut from fix(ci): keep the dependency exemption when a branch is brought up to date #599 alone);
• the release bot sees an empty [Unreleased] and will not cut a release for fix(e2e): give VictoriaLogs the memory its queries need #597.

This restores [1.87.0] to exactly what the release commit (f722ff7f) published — verified byte-for-byte from ## [1.87.0] down — and lists the entry under [Unreleased] / ### Fixed, where the next release picks it up.

The same failure is what #600 turns into a CI error; this is the manual repair for the instance that landed before it. It uses a docs(changelog) commit, the escape hatch #600 provides for deliberate edits to released history.

[github-actions]

PR Quality Report

Compared against base branch main.

Coverage and tests

Signal	Base	PR	Delta
Test count	7387	7387	0
Coverage	90.1%	90.1%	0.0% (stable)

Compatibility

Track	Base	PR	Delta
Loki API	100.0%	11/11 (100.0%)	0.0% (stable)
Logs Drilldown	100.0%	17/17 (100.0%)	0.0% (stable)
VictoriaLogs	100.0%	11/11 (100.0%)	0.0% (stable)

Performance smoke

Performance smoke was skipped for this PR because no perf-sensitive paths changed.

State

• Coverage, compatibility, and sampled performance are reported here from the same PR workflow.
• This is a delta report, not a release gate by itself. Required checks still decide merge safety.
• Performance smoke was intentionally skipped because no perf-sensitive paths changed in this PR.
• Delta states use the same noise guards as the quality gate (percent + absolute + low-baseline checks), so report labels match merge-gate behavior.