Skip to content

release: v3.5.0 - #951

Merged
github-actions[bot] merged 3 commits into
mainfrom
release/v3.5.0
Jun 4, 2026
Merged

github-actions[bot] merged 3 commits into
mainfrom
release/v3.5.0

Conversation

@robotrocketscience

@robotrocketscience robotrocketscience commented Jun 4, 2026

Copy link
Copy Markdown
Owner

Cuts v3.5.0 as a single tag spanning the v3.4.0 cadence-policy / conversation-aware retrieval work that never tagged (PR #924, opened 2026-05-26, closed today as superseded) plus the visibility / observability wave that landed today.

What ships

v3.5.0 (today's wave) — runtime

v3.4.0 (carried forward, never tagged) — runtime

Release mechanics

  • pyproject.toml: 3.3.0 → 3.5.0.
  • uv.lock: re-resolved (uv lock).
  • CHANGELOG/v3.md: [Unreleased] cleared; added [3.5.0] - 2026-06-04 (today's wave) above [3.4.0] - 2026-05-26 (preserved historically; never tagged as a standalone release).
  • PR release: v3.4.0 #924 closed as superseded; its body content is preserved in the [3.4.0] section.

Verification

  • pytest tests/ -x -q: 5168 passed, 68 skipped, 75 xfailed.
  • uv run python -c 'import aelfrice; print(aelfrice.__version__)'3.5.0.
  • Discretion grep on diff: clean.

After merge

  1. git tag v3.5.0 <merge-commit-sha>
  2. git push github v3.5.0
  3. .github/workflows/publish.yml triggers on the v* tag and publishes to PyPI via Trusted Publishing.
  4. The release-drafter draft promotes per the precedent established by PR ci(publish): promote release-drafter draft on tag push (#804) #805.

Summary by Sourcery

Cut the v3.5.0 release, capturing both the new observability/visibility features and the previously untagged v3.4.0 cadence-policy work in a single published version.

New Features:

  • Document and expose the v3.5.0 observability wave, including new belief feed logging, stale listing, speculative belief listing, contradiction markers, a weekly review workflow, and an audit command for cross-store deduplication.
  • Add CLI-level safeguards and UX improvements such as a pre-issue duplicate detection hook and enhanced statusline counters for belief states.

Build:

  • Bump the project version from 3.3.0 to 3.5.0 and refresh the uv.lock dependency lockfile.

Documentation:

  • Add detailed changelog entries for v3.5.0 and the historically untagged v3.4.0 release, including a note on how both sets of changes ship together.
  • Tweak existing documentation text for accuracy around benchmark fixtures and latency framing across README and ROADMAP.

Single tag spanning the v3.4.0 cadence-policy completion / conversation-
aware retrieval work (#876, #909) plus today's visibility / observability
wave (#931, #932, #933, #934, #935, #936, #937, #938, #941, #928, #923,
#925). PR #924's v3.4.0 cut was never tagged; its body is preserved as
the [3.4.0] section in CHANGELOG/v3.md for historical accuracy. Both
sections ship in this one PyPI publish.

- pyproject.toml: 3.3.0 -> 3.5.0
- uv.lock: re-resolved
- CHANGELOG/v3.md: [Unreleased] cleared; [3.5.0] + [3.4.0] added
@sourcery-ai

sourcery-ai Bot commented Jun 4, 2026

Copy link
Copy Markdown

Reviewer's Guide

Cuts runtime release v3.5.0 (including previously untagged v3.4.0 changes) by updating the v3 changelog, bumping the Python package version, and regenerating the uv.lock to prepare for tagging and PyPI publication.

Flow diagram for v3.5.0 release and publish pipeline

flowchart LR
    A[Merge PR release_v3_5_0] --> B[git tag v3.5.0]
    B --> C[git push github v3.5.0]
    C --> D[GitHub Actions workflow publish.yml]
    D --> E[PyPI publish via Trusted Publishing]
    C --> F[release-drafter draft updated]
Loading

File-Level Changes

Change Details Files
Document the v3.5.0 release contents and retroactively document the previously untagged v3.4.0 wave in the v3 changelog.
  • Add a new [3.5.0] section describing the observability- and review-focused features, fixes, and docs work shipping in this release.
  • Adjust the cadence replay benchmark description to reference a generic host directory instead of ~/.claude/.
  • Move the former Unreleased body into a [3.4.0] section, add a historical note that it was never tagged, and clarify that v3.5.0 ships both 3.4.0 and 3.5.0 changes in one publish.
CHANGELOG/v3.md
Bump the package version to 3.5.0 for distribution.
  • Update the project version field from 3.3.0 to 3.5.0 in the project metadata.
pyproject.toml
Refresh dependency lock state for the new release.
  • Regenerate uv.lock via uv lock so the locked dependency graph matches the 3.5.0 release cut.
uv.lock

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@coderabbitai

coderabbitai Bot commented Jun 4, 2026

Copy link
Copy Markdown

Important

Review skipped

Ignore keyword(s) in the title.

⛔ Ignored keywords (2)
  • docs:
  • release:

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 512d029c-c55c-45c0-a0c0-daed9d92c81c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release/v3.5.0

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.

❤️ Share

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

@sourcery-ai sourcery-ai 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.

Hey - I've found 1 issue

Prompt for AI Agents
Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="CHANGELOG/v3.md" line_range="26-29" />
<code_context>
+- **`.aelfrice-feed.jsonl` per-project belief-write log + `aelf feed`
+  reader (#931).** Append-only JSONL row per write event across all five
+  write paths (lock / onboard / wonder-promote / feedback / ingested).
+  Writes are swallow-errors so a feed failure can't break the write path
+  that triggered it. Rotates at 100 MB. Reader supports `--since`
+  filtering and a JSONL passthrough mode. Default-on, opt-out via
</code_context>
<issue_to_address>
**suggestion (typo):** Clarify or rephrase "Writes are swallow-errors" for grammatical correctness

The phrase "Writes are swallow-errors" is ungrammatical. Consider rewording to something like "Writes swallow errors, so a feed failure can't break the write path" to clearly describe the behavior.

```suggestion
  reader (#931).** Append-only JSONL row per write event across all five
  write paths (lock / onboard / wonder-promote / feedback / ingested).
  Writes swallow errors, so a feed failure can't break the write path
  that triggered it. Rotates at 100 MB. Reader supports `--since`
```
</issue_to_address>

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Comment thread CHANGELOG/v3.md Outdated
release-docs-check requires a [3.5.0]: ... footnote near the bottom of
CHANGELOG/v3.md. Added both [3.5.0] and [3.4.0] (the latter pointing at
the same v3.3.0...v3.5.0 range since v3.4.0 was never tagged
standalone). [Unreleased] retargets v3.5.0...HEAD.
@robotrocketscience robotrocketscience added the ready-to-merge Trigger merge-train: FF main to this PR's head label Jun 4, 2026
@github-actions

github-actions Bot commented Jun 4, 2026

Copy link
Copy Markdown

merge-train: blocked

1 review thread(s) are unresolved on these files: CHANGELOG/v3.md. Resolve them on the PR (click 'Resolve conversation' on each) and re-add the label.

The ready-to-merge label has been removed. Address the issue above and re-add the label when you're ready for another attempt.

@github-actions github-actions Bot removed the ready-to-merge Trigger merge-train: FF main to this PR's head label Jun 4, 2026
Sourcery flagged 'Writes are swallow-errors' as ungrammatical. Reworded
to 'Write-side errors are swallowed'.
@robotrocketscience robotrocketscience added the ready-to-merge Trigger merge-train: FF main to this PR's head label Jun 4, 2026
@github-actions

github-actions Bot commented Jun 4, 2026

Copy link
Copy Markdown

merge-train: blocked

required check(s) failed: pytest (3.13). Fix CI and re-add the label.

The ready-to-merge label has been removed. Address the issue above and re-add the label when you're ready for another attempt.

@github-actions github-actions Bot removed the ready-to-merge Trigger merge-train: FF main to this PR's head label Jun 4, 2026
@robotrocketscience robotrocketscience added the ready-to-merge Trigger merge-train: FF main to this PR's head label Jun 4, 2026
@github-actions

github-actions Bot commented Jun 4, 2026

Copy link
Copy Markdown

merge-train: merged 23f60c1main via FF push.

@github-actions github-actions Bot removed the ready-to-merge Trigger merge-train: FF main to this PR's head label Jun 4, 2026
@github-actions
github-actions Bot merged commit 23f60c1 into main Jun 4, 2026
33 of 35 checks passed
@robotrocketscience
robotrocketscience deleted the release/v3.5.0 branch June 10, 2026 22:20
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