Skip to content

docs: drop stale CHANGELOG.md + add maintainer contact#170

Merged
anilmurty merged 1 commit into
mainfrom
docs/drop-changelog-add-contact
Jun 20, 2026
Merged

docs: drop stale CHANGELOG.md + add maintainer contact#170
anilmurty merged 1 commit into
mainfrom
docs/drop-changelog-add-contact

Conversation

@anilmurty

Copy link
Copy Markdown
Contributor

Two small README hygiene changes.

1. Drop `CHANGELOG.md`

The file was stale by three releases — its `## Unreleased` section still described v0.3.0-era work, and every release since landed only as GitHub Release notes. The inline release notes we publish at tag time are already richer than the per-version-bullet-list format that Keep-a-Changelog expects, so maintaining `CHANGELOG.md` would mean writing every release twice.

GitHub Releases is already the canonical channel:

  • Publish workflows (`publish-pypi.yml`, `publish-npm.yml`) fire on release events
  • `gh release view v<X.Y.Z>` reads from there
  • PyPI's "Homepage" link points to the repo, which surfaces Releases prominently

The README's Documentation table now points "Release notes" at the GitHub Releases page directly.

2. Add maintainer contact in the footer

Currently the only contact path from the README is filing an issue, which is fine for bugs but discourages "I'm trying this out, can I talk to you" conversations. New footer line:

TokenJam was created by Anil Murty — reach him at anil@metabldr.com.

No code changes.

🤖 Generated with Claude Code

…, add maintainer contact

Two small README hygiene changes:

1. Drop CHANGELOG.md entirely. The file was stale by three releases —
   its `## Unreleased` section still described v0.3.0-era work, and every
   release since 0.3.x landed only as GitHub Release notes. Maintaining
   it would mean writing every release twice; the inline release notes
   we publish at tag time are already richer than the per-version
   bullet-list format anyway. The README's Documentation table now
   points "Release notes" at the GitHub Releases page directly, which
   is already the canonical channel (publish workflows fire from it,
   `gh release view` reads from it, PyPI's "Homepage" links to it).

2. Add a maintainer contact line in the footer so readers have a
   direct way to reach out — currently the only contact path is
   filing an issue, which is fine for bugs but discourages "I'm
   trying this out, can I talk to you" conversations.

No code changes.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@anilmurty anilmurty merged commit 568b6a0 into main Jun 20, 2026
4 checks passed
@anilmurty anilmurty deleted the docs/drop-changelog-add-contact branch June 20, 2026 17:04
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