Repository navigation
Release 1.11.0: cut the changelog, and stop the release notes naming people - #91
Merged
Merged
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configuration
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
…ople [Unreleased] becomes [1.11.0] - 2026-10-08. It had accumulated 18 `###` headings against 5 canonical ones — four separate `### Added`, five `### Changed`, three `### Fixed` — because each was appended at the time of writing. Merged into Keep a Changelog order (Added, Changed, Removed, Fixed, Security) with all 57 items kept; verified item-for-item, not by eye. Three items had also been written without a newline before the next `- **`, so two entries rendered as one paragraph each. Fixed. Release plumbing, which is what actually leaked: - release.yml used `generate_release_notes: true`, composing the body from PR titles and author handles. That is where "@Cipher208 and Murat" came from in the dead v1.10.0 draft. The body now comes from the CHANGELOG section for the tag, and the step fails when that section is absent — a tag with no written notes should stop the release, not quietly generate a list of names. - release-drafter.yml carried `@$AUTHOR` in `change-template` and a `$CONTRIBUTORS` block. Both removed; the drafter remains a working aid. - The dead v1.10.0 draft (never tagged) is deleted. - bug_report.yml asked for `pip show mcp-ariel-memory`, which resolves nothing: the distribution is `a-memory`, and mcp-ariel-memory is one of three console scripts. Now `pip show a-memory`. Artifacts built and inspected before this commit: wheel 276 files with no tests, docs or logs; sdist 727 files carrying both, and no venv; the wheel is built from the sdist (so the sdist is self-sufficient); installed into a fresh venv it loads config.yaml, all 23 top-level keys, the entry point and all three console scripts.
Cipher208
force-pushed
the
release/v1.11.0
branch
from
October 7, 2026 23:57
87c36e3 to
6e27aee
Compare
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.
Prepares
v1.11.0. No tag yet — the tag is pushed after this merges, and that iswhat triggers PyPI.
The changelog
[Unreleased]→## [1.11.0] - 2026-10-08. It had accumulated 18###headingsagainst 5 canonical ones — four
### Added, five### Changed, three### Fixed—because each was appended when written. Merged into Keep a Changelog order (Added,
Changed, Removed, Fixed, Security) with all 57 items kept, verified item-for-item
rather than by eye.
Three entries had also been written without a newline before the next
- **, so twoitems each rendered as one paragraph. Fixed.
The leak in the release plumbing
This is the part that matters beyond the version bump:
release.ymlusedgenerate_release_notes: true. That composes the body from PRtitles and author handles — it is exactly where the dead draft's closing line
"@Cipher208 and Murat" came from. The body now comes from the CHANGELOG section for
the tag, and the step fails when that section is missing: a tag with no written
notes should stop the release rather than quietly generate a list of names.
release-drafter.ymlcarried@$AUTHORinchange-templateand a$CONTRIBUTORSblock. Both removed; the drafter stays as a working aid.
v1.10.0draft — never tagged, body generated — is deleted.bug_report.ymlasked forpip show mcp-ariel-memory, which resolves nothing: thedistribution is
a-memory, andmcp-ariel-memoryis one of three console scripts.Anyone following the form got "Package(s) not found". Now
pip show a-memory.Verified before this commit
tests/,docs/,.github/or logsconfig.yamlpresent, all 23 top-level configkeys load, the entry point imports, 3 of 3 console scripts installed
exits non-zero
v1.11.0is 157 lines and contains zero person namesruff,ruff format, the full pytest gate — clean on commit.