Skip to content

chore: prepare the 2.6.1 releas - #175

Merged
bagowix merged 1 commit into
mainfrom
release/2.6.1
Aug 17, 2026
Merged

chore: prepare the 2.6.1 releas#175
bagowix merged 1 commit into
mainfrom
release/2.6.1

Conversation

@bagowix

@bagowix bagowix commented Aug 17, 2026

Copy link
Copy Markdown
Owner

Summary

Prepare the 2.6.1 patch release.

  • Bump the package version from 2.6.0 to 2.6.1.
  • Move the current [Unreleased] changelog entries into [2.6.1] - 2026-08-17.
  • Update changelog comparison links and the comparison-page release version.
  • Regenerate docs/llms-full.txt.

Patch, not minor: nothing under interlock/ changed since v2.6.0 — the release carries documentation and packaging metadata only (#166, #173, #174), and griffe reports the VERSION attribute as the sole public difference.

It exists because a package page keeps the description and the project urls of the version that was uploaded, so none of that work is visible where it was aimed. pypi.org currently serves the README whose 31 relative links answer 404 there, and a Homepage pointing at the repository rather than at the documentation. Checked on the built wheel: Homepage → the documentation site, 0 relative links in the long description, state-machine diagram embedded.

Checklist

  • Tests added or updated (suite stays at 100% coverage)
  • uv run ruff format --check and uv run ruff check pass
  • uv run mypy, uv run pyright and uv run pyrefly check pass
  • Docs updated (docs/) for user-facing changes
  • CHANGELOG.md [Unreleased] updated
  • Commits follow Conventional Commits

Additional release checks: the package build passes (interlock_cb-2.6.1), twine check PASSED on both artefacts, and griffe reports only the expected public VERSION change (2.6.02.6.1).

One timing note for tagging: GitHub is currently returning No server is currently available to service your request on parts of its API — CodeQL and Scorecard failed that way on #174 and on main, at the Initialize step rather than in analysis. Worth having those green before pushing the tag, so the publish job does not meet the same outage.

Related issues

#166
#173
#174

Patch, not minor: nothing under interlock/ changed since v2.6.0 — griffe
reports only the VERSION attribute. The release exists to refresh what PyPI
serves, since a package page keeps the description and the project urls of
the version that was uploaded: pypi.org still shows the README whose 31
relative links answer 404 there, and a Homepage pointing at the repository
instead of the documentation.

- Bump the package version from 2.6.0 to 2.6.1.
- Move the current [Unreleased] changelog entries into [2.6.1] - 2026-08-17.
- Update the changelog comparison links and the comparison-page release
  version.
- Regenerate docs/llms-full.txt.
@codspeed-hq

codspeed-hq Bot commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

Merging this PR will improve performance by 10.32%

⚡ 1 improved benchmark
✅ 27 untouched benchmarks

Performance Changes

Benchmark BASE HEAD Efficiency
test_baseline_direct_call 29.3 µs 26.6 µs +10.32%

Tip

Curious why this is faster? Comment @codspeedbot explain why this is faster on this PR, or directly use the CodSpeed MCP with your agent.


Comparing release/2.6.1 (cd209a3) with main (284d69d)

Open in CodSpeed

@codecov

codecov Bot commented Aug 17, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!

@bagowix
bagowix merged commit a12d792 into main Aug 17, 2026
21 of 22 checks passed
@bagowix
bagowix deleted the release/2.6.1 branch August 17, 2026 18:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant