version bump v2.7.8#320
Conversation
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
LGTM — straightforward version bump and changelog roll-up.
Extended reasoning...
Overview
This PR prepares the 2.7.8 patch release. It bumps the version in pyproject.toml (2.7.7 → 2.7.8) and the matching entry in uv.lock, and moves the code-complete items from the Upcoming section of CHANGES.md into a dated Current 2.7.8 section (Node 24 CI bump from #318 and the all_editions de-duplication from #317). No source code changes.
Security risks
None. Changes are limited to release metadata and changelog text; no auth, crypto, permissions, or input-handling code is touched.
Level of scrutiny
Very low. This is a mechanical release-prep PR of the same shape as every prior version bump — the actual behavior changes were reviewed and merged as #317 and #318 separately.
Other factors
The version numbers are consistent across pyproject.toml and uv.lock, the changelog section header restructure looks correct (the ## Current marker moves up above the new 2.7.8 block, with a fresh empty Upcoming stub on top), and the described contents match the two included PRs.
The Eyecite Report 👁️Gains and LossesThere were 0 gains and 0 losses. Total citations found: base 15988, PR 15988 (net +0). Click here to see details.
Time ChartGenerated Files |

Patch release 2.7.8.
Rolls the code-complete items from Upcoming into a dated Current section and bumps the version in
pyproject.toml/uv.lock.Included since 2.7.7:
all_editions(all_editions contains duplicate (identical) editions for whitespace-spaced reporters since 2.7.7 #317)Once merged, tag
v2.7.8on the merge commit to trigger the PyPI publish workflow.🤖 Generated with Claude Code