release: v3.1.0 — Legible to machines - #10481
Merged
Merged
Conversation
Moves the [Unreleased] section to [3.1.0], bumps pyproject.toml and the project's own pin in uv.lock. Minor rather than major by the repo's own rule: agentic/commands/release.md reserves major for language/library waves, rebrands and breaking URL or schema changes, and this window contains none of those. It is a large feature batch — 84 entries over two months — not a milestone in that sense. Two aggregate lines added as the procedure requires: the Dependencies bullet now covers all 32 Dependabot bumps of the window rather than the nine it listed, and a Catalog line records 1,607 implementation merges, 10 new plot types and the catalogue's current size. uv.lock carries only the version line. Running `uv lock` also normalised platform markers on secretstorage and statsmodels — drift from a newer uv than the one that wrote the committed lock. That is unrelated to the release and would have made the diff harder to audit, so it is left for a separate change; `uv lock --check` passes with the lock as committed here. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Prepares the v3.1.0 (“Legible to machines”) release by finalizing the changelog for the release window and bumping the project version so packaging and lock metadata reflect the new release.
Changes:
- Promote
[Unreleased]content to a new## [3.1.0] — 2026-08-18 — Legible to machinessection, refresh[Unreleased], and update compare links. - Bump the project version from 3.0.0 → 3.1.0 in
pyproject.toml. - Update the
anyplotpackage version pin inuv.lockto 3.1.0.
Reviewed changes
Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
CHANGELOG.md |
Adds the v3.1.0 release section, keeps an empty [Unreleased], updates aggregate bullets and compare links. |
pyproject.toml |
Bumps [project].version to 3.1.0. |
uv.lock |
Updates the editable anyplot package’s version to 3.1.0 to match the release. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cuts v3.1.0, the first release since v3.0.0 on 2026-06-10 — 84 changelog entries over two months.
Version choice
Minor, by the repo's own rule.
agentic/commands/release.mdreserves major for "new language/library waves, rebrands, breaking URL/schema changes". This window has none: no new language, no new library, no rebrand. It is a large feature batch, not a milestone in that sense — the owner confirmed the reading.Codename: Legible to machines
The theme is that an assistant asked about a plot can now find it, open one library's page, read the runnable source, fetch the rendered image and cite the URL. That path was broken at four separate points, every one of them invisible to anyone browsing the site by hand:
/{spec}/{language}robots.txtforbids crawlingPlus the crawler policy opening to every operator that follows the rules — the only way Gemini can ever cite the catalogue — and two Plausible sites separating what people read from what machines do.
The three files
CHANGELOG.md[Unreleased]→[3.1.0] — 2026-08-18 — Legible to machines, fresh empty[Unreleased], both compare links, intro paragraph, two aggregate linespyproject.toml3.0.0→3.1.0uv.lockAggregates
On the lock file
uv lockalso normalised platform markers onsecretstorageandstatsmodels— drift between the committed lock and a neweruv. Unrelated to the release and it would have made this diff harder to audit, souv.lockcarries only the version line here.uv lock --checkpasses as committed. Worth a separate housekeeping change.Completeness check
Every non-exempt commit since
v3.0.0was matched against the changelog. Eleven appeared unreferenced; ten arespec: add …(spec-create output, exempt) and the eleventh — the white-screen outage fix — is documented, under the Dependabot PR number that caused it rather than the fix PR's. No gaps.pytest tests/unit1648 passed;ruff checkclean.After merge
Tag and publish per
agentic/commands/release.md:The site masthead picks the tag up on its own — nothing to deploy.
🤖 Generated with Claude Code