Skip to content

release: v1.7.0 - #447

Merged
robotrocketscience merged 3 commits into
mainfrom
release/v1.7.0
May 8, 2026
Merged

release: v1.7.0#447
robotrocketscience merged 3 commits into
mainfrom
release/v1.7.0

Conversation

@yoshi280

@yoshi280 yoshi280 commented May 5, 2026

Copy link
Copy Markdown
Collaborator

v1.7.0 release cut (refreshed 2026-05-07).

What changed since the original PR was opened

v1.7.0 surface (per CHANGELOG)

Default-on

New CLI verbs

v2.0 detector wave

Internal refactor

Retrieval/contradiction surface

CI / observability

Surface ergonomics

Opt-in (lane wiring / bench evidence pending)

Test plan

  • uv lock resolves cleanly at 1.7.0.
  • CHANGELOG ## [1.7.0] section + [1.7.0]: compare-link footnote present (fixes release-docs-check).
  • No duplicate section headings.
  • CI matrix (pytest (3.12), pytest (3.13)) + staging-gate green.
  • FF-merge to main.
  • Tag v1.7.0 and push (deferred — separate user step per CLAUDE.md release process).

Sequence

First half of the v2.0 release sequence. Once v1.7.0 lands, a follow-up release: v2.0.0 PR bumps to 2.0.0 (the reproducibility-cut tag).

@coderabbitai

coderabbitai Bot commented May 5, 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: 43f56468-7c27-4331-9735-3b2a1de59a46

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/v1.7.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 commented May 5, 2026

Copy link
Copy Markdown

Reviewer's Guide

Release PR that cuts v1.7.0: bumps the project version, adds a detailed 1.7.0 CHANGELOG section describing new retrieval / contradiction-detection / CI features, and refreshes uv.lock; no functional changes are made directly in this diff beyond documentation and metadata for the already-landed features.

File-Level Changes

Change Details Files
Add CHANGELOG entry for v1.7.0 describing newly shipped retrieval, contradiction-detection, stale-edge handling, replay-soak gate, and CI workflow changes.
  • Insert [1.7.0] section with release date and high-level theme description.
  • Document BM25F anchor-text retrieval as default-on and note remaining retrieval lanes as opt-in flags.
  • Describe new edge-type-keyed rerank consumer, POTENTIALLY_STALE edge writer, and related markers/APIs.
  • Describe semantic contradiction detector v3 with typed-slot value-comparison and associated tests/bench-gate.
  • Describe new /aelf:confirm slash/CLI command behavior and semantics.
  • Describe replay-soak gate workflow, streak computation, and scope/requirements.
  • Clarify CI workflow behavior including paths-filter migration and docs-only gate behavior, including note about subsumption of earlier approach.
CHANGELOG.md
Bump project version from 1.6.0 to 1.7.0 for release cut.
  • Update [project] version field to 1.7.0 in pyproject.toml.
pyproject.toml
Refresh dependency lockfile for v1.7.0.
  • Regenerate uv.lock to align with the 1.7.0 version cut and current dependency graph.
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

@yoshi280 yoshi280 mentioned this pull request May 5, 2026
5 tasks

@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 left some high level feedback:

  • The new 1.7.0 CHANGELOG section repeats the full 'Differential CI gates for docs-only PRs' entry under both the 1.6.0 and 1.7.0 headings with only a parenthetical note; consider trimming or rephrasing the 1.7.0 copy to focus on what changed in this release (e.g., referencing the prior entry) to avoid duplication and potential confusion about when the behavior originally landed.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- The new 1.7.0 CHANGELOG section repeats the full 'Differential CI gates for docs-only PRs' entry under both the 1.6.0 and 1.7.0 headings with only a parenthetical note; consider trimming or rephrasing the 1.7.0 copy to focus on what changed in this release (e.g., referencing the prior entry) to avoid duplication and potential confusion about when the behavior originally landed.

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.

@github-actions github-actions Bot added the attn:merge-conflict PR branch needs rebase label May 5, 2026
@github-actions

github-actions Bot commented May 5, 2026

Copy link
Copy Markdown

This PR is now behind main. Rebase locally so your commit signatures stay intact:

git fetch origin && git checkout 'release/v1.7.0' && git rebase origin/main
# resolve conflicts if any, then
git push --force-with-lease

Auto-rebase was removed because the bot has no signing key; rebasing as the bot strips author signatures and the required_signatures rule on main then blocks the merge. See #341.

The quickstart block bundled `aelf lock "never push directly to main"`
as the third of four lines, indistinguishable from a required step.
Users ran it verbatim and ended up with a permanent locked belief
about a publish script that doesn't exist in their repo.

Split the block: install + setup + onboard are the install. The
`aelf lock` example is now in its own block under "add your first
rule", explicitly called out as an example to substitute or skip.

Also switch `pip install` to `pipx install` (with `uv tool install`
as alternative). `aelf` is a global CLI; `pipx`/`uv tool` are the
right install paths and `pip install` fails outright on PEP 668
systems and on macOS where no `pip` shim is on PATH.

Reorder `aelf setup` before `aelf onboard`: setup is the
load-bearing one-time hook install, onboard is re-runnable and can
fail noisily on user code (e.g. ingest-time SyntaxWarnings).
The May 5 [1.7.0] section under-specified the release: missing the
#264 derivation-worker refactor (19-commit, biggest internal change),
the entire detector wave (#197 dedup, #201 contradiction, #228 wonder-
consolidation, #422 value-comparison, #193 sentiment), the four new
CLI verbs (#389 reason / #390 wonder, #391 unlock+promote, #440 delete,
#441 confirm), the #379 always-inject lock change, the #383-388 edge-
type ship gates, #291 query-strategy router, #288 rebuild-log UPS
instrumentation, #374 directive-detection Path A, #192 session_id T3
close-out, #334 e2e matrix, #370 testing-strategy split, #364 rebuild
relevance floor, #452 aelf health enhancements, #461 replay-soak
branch refactor, #360 docs realignment, #414 lychee fix, README
quickstart fix.

Also fixes `release-docs-check` by adding the
`[1.7.0]: https://github.com/.../compare/v1.6.0...v1.7.0`
compare-link footnote and pointing `[Unreleased]` at v1.7.0...HEAD.

Bumps the release date 2026-05-05 -> 2026-05-07 to match merge
state. Removes the duplicate `### Added` heading.
@robotrocketscience
robotrocketscience merged commit b0f9a2f into main May 8, 2026
20 checks passed
@robotrocketscience
robotrocketscience deleted the release/v1.7.0 branch May 8, 2026 03:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

attn:merge-conflict PR branch needs rebase

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants