Skip to content

chore(release): 0.3.2 is dated the day it ships - #20

Merged
izgorodin merged 1 commit into
mainfrom
release/0.3.2-dated
Oct 2, 2026
Merged

izgorodin merged 1 commit into
mainfrom
release/0.3.2-dated

Conversation

@izgorodin

@izgorodin izgorodin commented Oct 2, 2026 •

Copy link
Copy Markdown
Member

What

One line in CHANGELOG.md: the ## [0.3.2] heading is dated 2026-10-02, the day the tag is pushed, instead of 2026-09-25, the day the section was written. Version strings are unchanged (pyproject.toml and __version__ already read 0.3.2).

Pre-release check, 2026-10-02

  • pytest: 57 passed; mypy mnemoverse: clean (local, Python 3.12).
  • Request fields of read, write, feedback, graph and recent compared with the live core.mnemoverse.com/openapi.json: the SDK's OpenAPI snapshot differs from live only in five admin billing paths outside the SDK's scope; no request schema the SDK speaks has changed.
  • Open issues: only Package metadata on PyPI carried a personal contact address #10 (the contact address in PyPI metadata), which this release closes once 0.3.2 is served by PyPI.

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Documentation
    • Updated the changelog date for version 0.3.2 to October 2, 2026.
    • The release notes continue to cover package and README description updates, keyword changes, and an author email update.

The section was written on 2026-09-25 together with the metadata fix and
sat unreleased for a week. Keep a Changelog dates a section by its
release date; the tag goes on today's merge commit.

Co-Authored-By: Σ <sigma@mnemoverse.ai>
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Oct 2, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Team

Run ID: a1eb742b-36d9-460a-a8e0-8af655892484

📥 Commits

Reviewing files that changed from the base of the PR and between 352f1e6 and ce941be.

📒 Files selected for processing (1)
  • CHANGELOG.md

Included review availability: This review used your included allowance. 1 included review remains after this review. Your included PR review attempts over the past 7 days set your current allowance at 2 reviews per hour.


📝 Walkthrough

Walkthrough

The 0.3.2 changelog date changed from 2026-09-25 to 2026-10-02. The release classification and listed changes remain unchanged.

Changes

Release Notes

Layer / File(s) Summary
Update release date
CHANGELOG.md
The 0.3.2 release date changed to 2026-10-02. The release classification and listed changes remain unchanged.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~2 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to ce941

No actionable merge-blocking risk is apparent in this date-only changelog update.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly describes the main change: updating the 0.3.2 changelog date to the release date.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
  • Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Autopilot is currently an internal CodeRabbit preview.


A rabbit checks the release date,
Then marks the page: October two.
The patch notes stay just as they were,
While carrots wait beside the queue.
One neat hop, and changelog’s through.

Comment @coderabbitai help to get the list of available commands.

@sigma-mnemoverse sigma-mnemoverse Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sigma Charlie v6 (subscription) reviewed ce941be3fb2b5d3fcc0252c90d9884ce9f0a6389 against base 352f1e6c148fd07cfe2e6fafbeb14c728e009bd4.

Executor: owner-login (producer on the owner's subscription login in Sigma's sandbox; verifier on Sigma's API keys through the credential gateway).

Verified findings: 0. Run: adea33cd-909c-452a-a4f2-10cfd11b05ad.

Cost

producer: owner subscription, observed CLI usage 18 in / 3576 out tokens (≈$0.173676 at API list price, not billed by Sigma)

verifier: metered by Sigma, $0.000000 settled (0 microUSD).

Scope notes

runtime/dependencies:

Dependencies were not prepared: the repository declares dependencies Sigma cannot prepare offline (it needs a root uv.lock, or only a root package.json with its package-lock.json). The project was not installed in the sandbox, so its tests could not run there.

producer/claude-review:

The change is a single-line date correction in CHANGELOG.md (0.3.2 release date changed from 2026-09-25, which duplicated the 0.3.1 entry's date, to 2026-10-02). Checked README.md, pyproject.toml, mnemoverse/__init__.py and _openapi.json for conflicting version/date references; found none, and pyproject.toml/__init__.py already report version 0.3.2, consistent with this entry. No shared mechanism (endpoint, status code, threshold, etc.) is affected by this edit, so no further cross-file comparison was applicable.

producer/claude-review:

Could not check whether any external release/tag metadata or PyPI listing references the old 2026-09-25 date for 0.3.2, since those are outside the supplied repository snapshot.

@izgorodin
izgorodin merged commit f10afc2 into main Oct 2, 2026
9 checks passed
@izgorodin
izgorodin deleted the release/0.3.2-dated branch October 2, 2026 20:29
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