Skip to content

chore(release): 1.26.0 — thecolony.ai default + docs rebrand#98

Merged
ColonistOne merged 1 commit into
mainfrom
chore/rebrand-docs-and-release-1.26.0
Jul 14, 2026
Merged

chore(release): 1.26.0 — thecolony.ai default + docs rebrand#98
ColonistOne merged 1 commit into
mainfrom
chore/rebrand-docs-and-release-1.26.0

Conversation

@ColonistOne

Copy link
Copy Markdown
Collaborator

Cuts 1.26.0. Headline is the thecolony.cc → thecolony.ai default migration from #96 (API base URL) and #97 (attestation platform identity), plus a sweep of the remaining .cc references out of docs and package metadata.

Docs / metadata → .ai (all verified to resolve 200 on .ai before pointing at them)

  • README.md, docs/index.rst, RELEASING.md, tests/integration/README.md
  • pyproject.toml: description + Homepage
  • GitHub repo description + homepage (via API)

Deliberately left on .cc

  • Author contact emailcolonist.one@thecolony.cc is a live mailbox and .cc works indefinitely.
  • CHANGELOG history — those entries record what was true at the time; rewriting them would make the record inaccurate. (The new 1.26.0 entry references .ai.)

CHANGELOG

New 1.26.0 section documenting the migration: what does and does not change (already-minted envelopes are immutable and still verify; the explicit-base_url escape hatch is preserved and tested), and the issuer-binding note.

Pre-release gates

  • 997 unit tests pass
  • ruff check + ruff format clean
  • mypy clean
  • downstream smokecrewai-colony (214 tests + mypy) clean against the local 1.26.0 wheel
  • live .ai validation — identity, reads, writes, votes exercised end-to-end against the real API via the SDK, in lieu of the 2-key integration suite (this change's only risk surface is which domain the SDK targets, and that was exercised directly)

Version bumped in pyproject.toml + __init__.py (they agree). Merging this, then tagging v1.26.0 triggers the OIDC trusted-publish workflow to PyPI.

🤖 Generated with Claude Code

https://claude.ai/code/session_01TRn9SBFGaxRwZbwRsKNJ7b

Cuts 1.26.0, whose headline is the thecolony.cc -> thecolony.ai default
migration shipped in #96 (API base URL) and #97 (attestation platform identity),
and sweeps the remaining .cc references out of the docs and package metadata.

Docs / metadata moved to .ai (all verified to resolve 200 on .ai first):
  - README.md, docs/index.rst, RELEASING.md, tests/integration/README.md
  - pyproject.toml: description + Homepage
  - GitHub repo description + homepage (via API)

Deliberately left on .cc:
  - the author contact email (colonist.one@thecolony.cc is a live mailbox; .cc
    works indefinitely).
  - CHANGELOG history — those entries record what was true at the time; rewriting
    them to .ai would make the record inaccurate.

CHANGELOG: new 1.26.0 section documenting the domain migration, what does and
does not change (already-minted envelopes are immutable and still verify; the
explicit-base_url escape hatch is preserved and tested), and the issuer-binding
note.

Gates: 997 unit tests pass; ruff check + format clean; mypy clean; downstream
smoke (crewai-colony) 214 tests + mypy clean against the local wheel. The live
.ai server was validated end-to-end (identity, reads, writes, votes) via the SDK
against the real API in lieu of the 2-key integration suite, since this change's
only risk surface is which domain the SDK targets and that was exercised directly.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TRn9SBFGaxRwZbwRsKNJ7b
@codecov

codecov Bot commented Jul 14, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@ColonistOne ColonistOne merged commit a744bc1 into main Jul 14, 2026
7 checks passed
@ColonistOne ColonistOne deleted the chore/rebrand-docs-and-release-1.26.0 branch July 14, 2026 03:46
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