Skip to content

docs: publish release notes for v2026.6.11#98273

Closed
hannesrudolph wants to merge 1 commit into
openclaw:mainfrom
hannesrudolph:docs/release-notes-v2026.6.11
Closed

docs: publish release notes for v2026.6.11#98273
hannesrudolph wants to merge 1 commit into
openclaw:mainfrom
hannesrudolph:docs/release-notes-v2026.6.11

Conversation

@hannesrudolph

@hannesrudolph hannesrudolph commented Jun 30, 2026

Copy link
Copy Markdown
Member

What Problem This Solves

Resolves a problem where the published v2026.6.11 changelog and release-note surfaces do not yet use the human-approved public release story or the docs release page as the canonical full-notes destination.

Why This Change Was Made

This publishes the approved v2026.6.11 public changelog section and adds the matching Mintlify release-notes page under docs/releases/2026.6.11.md. The docs release page becomes the full-notes target, while the GitHub release body remains a separate post-merge update so its live release verification block can be preserved exactly.

User Impact

Readers get a clearer v2026.6.11 release story focused on rough edges from real use, including misplaced replies, stuck sends, reconnects, model setup failures, and safer admin defaults. Technical readers still get linked source and contributor detail without making the public changelog read like raw maintainer accounting.

Evidence

  • Human review approved release-notes eval iteration 10.
  • The approved iteration is preserved under evals/v2026.6.11/iterations/10/outputs/.
  • Structural generation validation passed for the approved artifact set.
  • Independent editorial evaluation passed with zero findings.
  • Publication comparison is approved with one intentional warning about replacing the previous raw contribution-heavy changelog section with the approved public-vs-maintainer boundary.

@openclaw-barnacle openclaw-barnacle Bot added docs Improvements or additions to documentation size: M maintainer Maintainer-authored PR labels Jun 30, 2026
@clawsweeper

clawsweeper Bot commented Jun 30, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Codex review: found issues before merge. Reviewed June 30, 2026, 5:32 PM ET / 21:32 UTC.

Summary
The PR rewrites the v2026.6.11 changelog section, adds a dedicated Mintlify release-notes page, and links it from the release index and docs navigation.

PR surface: Docs +121. Total +121 across 4 files.

Reproducibility: not applicable. this is release documentation publication, not a runtime bug. Source inspection shows current main still has the release-index placeholder and no dedicated v2026.6.11 page.

Review metrics: 2 noteworthy metrics.

  • Release publication surfaces: 1 page added, 1 index link added, 1 nav entry added, 1 changelog section rewritten. This is release-publication and docs IA work where editorial approval matters before merge.
  • Approval artifact files in tree: 0 files found under evals/v2026.6.11/iterations/10/outputs. The PR body names that path as approval evidence, so maintainers need to confirm where that proof lives.

Stored data model
Persistent data-model change detected: persistent cache schema: CHANGELOG.md, vector/embedding metadata: CHANGELOG.md. Confirm migration or upgrade compatibility proof before merge.

Merge readiness
Overall: 🐚 platinum hermit
Proof: 🌊 off-meta tidepool
Patch quality: 🐚 platinum hermit
Result: ready for maintainer review.

Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch.

Rank-up moves:

  • Convert the internal docs links in the new release page to root-relative Mintlify routes.
  • Confirm the approved release-note artifact and PR-head docs validation before publication.

Risk before merge

  • [P1] The PR intentionally replaces the published raw v2026.6.11 release accounting with curated public release notes, so maintainers need to confirm the approved public-vs-maintainer boundary before publication.
  • [P1] The approval artifact path named in the PR body was not present in current main or PR head in this checkout, so artifact provenance needs maintainer confirmation outside the diff.
  • [P1] The live PR check rollup showed the docs check skipped on this head; this read-only review only confirmed git diff whitespace sanity.
  • [P1] The new release page still uses absolute docs.openclaw.ai links for internal docs pages, which conflicts with the docs-scoped Mintlify link rule.

Maintainer options:

  1. Confirm artifact and clean docs links (recommended)
    Convert the internal docs links on the new release page to root-relative routes, confirm the approved release-note artifact, and run or confirm PR-head docs validation before marking ready.
  2. Accept the editorial replacement
    Release maintainers may intentionally accept the curated public notes if they confirm the approved public-vs-maintainer boundary outside automated checks.
  3. Keep the draft parked
    Leave the PR open as draft if the approval artifact or release-copy boundary is not ready for publication.

Next step before merge

  • [P2] Manual review is appropriate because this maintainer-labeled draft release publication needs release/editorial confirmation and docs validation, not an autonomous repair lane.

Security
Cleared: The diff only changes release documentation, changelog text, and docs navigation; it does not touch executable code, workflows, dependencies, lockfiles, secrets, or package resolution.

Review findings

  • [P3] Use root-relative internal docs links — docs/releases/2026.6.11.md:74-95
Review details

Best possible solution:

Publish the dedicated release page after converting internal docs links to root-relative routes and confirming the approved release-note artifact plus PR-head docs validation.

Do we have a high-confidence way to reproduce the issue?

Not applicable; this is release documentation publication, not a runtime bug. Source inspection shows current main still has the release-index placeholder and no dedicated v2026.6.11 page.

Is this the best way to solve the issue?

Mostly yes; a dedicated release page plus index and navigation entry is the right Mintlify publication path. The safer pre-merge shape is to fix the internal docs links and confirm the release artifact plus docs checks for the current head.

Full review comments:

  • [P3] Use root-relative internal docs links — docs/releases/2026.6.11.md:74-95
    docs/AGENTS.md requires internal links in docs/**/*.md to stay root-relative with no suffix. This new release page links Slack, Raft, and Discord through https://docs.openclaw.ai/..., which sends previews and non-production docs builds out to the public site; change them to /channels/slack#relay-mode, /channels/raft, and /channels/discord.
    Confidence: 0.91

Overall correctness: patch is correct
Overall confidence: 0.84

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 44ec7580e2f0.

Label changes

Label justifications:

  • P3: This is low-risk release documentation and navigation work with no runtime, config, dependency, or package behavior change.
  • merge-risk: 🚨 other: Merging intentionally changes the public release story, an editorial release decision that automated checks cannot validate.
  • rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.
  • status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: Contributor real-behavior proof is not applicable because this is a MEMBER maintainer-labeled release documentation PR; the relevant gate is release artifact confirmation plus docs validation.
Evidence reviewed

PR surface:

Docs +121. Total +121 across 4 files.

View PR surface stats
Area Files Added Removed Net
Source 0 0 0 0
Tests 0 0 0 0
Docs 4 455 334 +121
Config 0 0 0 0
Generated 0 0 0 0
Other 0 0 0 0
Total 4 455 334 +121

What I checked:

Likely related people:

  • vincentkoc: The current v2026.6.11 changelog section on main blames to the release closeout commit authored and committed by vincentkoc. (role: recent release/changelog contributor; confidence: high; commits: 66e676d29b92; files: CHANGELOG.md)
  • dwc1997: The release index page and Release and CI navigation scaffold that this PR extends both blame to commit 28347ba. (role: recent docs navigation contributor; confidence: medium; commits: 28347ba51c3d; files: docs/releases/index.md, docs/docs.json)
What the crustacean ranks mean
  • 🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
  • 🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
  • 🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
  • 🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
  • 🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
  • 🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
  • 🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

How this review workflow works
  • ClawSweeper keeps one durable marker-backed review comment per issue or PR.
  • Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
  • A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
  • PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
  • Maintainers can also comment @clawsweeper review to request a fresh review only.
  • Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
  • Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
  • Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

@hannesrudolph
hannesrudolph force-pushed the docs/release-notes-v2026.6.11 branch from 9d3b4a5 to 519f58a Compare June 30, 2026 21:02
@clawsweeper clawsweeper Bot added rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR. P3 Low-priority cleanup, docs, polish, ergonomics, or speculative work. merge-risk: 🚨 other 🚨 Merging this PR has meaningful risk outside the owned taxonomy. labels Jun 30, 2026
@hannesrudolph
hannesrudolph force-pushed the docs/release-notes-v2026.6.11 branch from 519f58a to 259ecee Compare June 30, 2026 21:17
@hannesrudolph
hannesrudolph force-pushed the docs/release-notes-v2026.6.11 branch from 259ecee to 2effc39 Compare June 30, 2026 21:32
@hannesrudolph

hannesrudolph commented Jun 30, 2026

Copy link
Copy Markdown
Member Author

Closing this draft while we repair the release-notes workflow coverage. The current v2026.6.11 candidate does not fully reconcile against the upstream changelog contribution record.

@clawsweeper clawsweeper Bot mentioned this pull request Jul 1, 2026
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

docs Improvements or additions to documentation maintainer Maintainer-authored PR merge-risk: 🚨 other 🚨 Merging this PR has meaningful risk outside the owned taxonomy. P3 Low-priority cleanup, docs, polish, ergonomics, or speculative work. rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. size: M status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@hannesrudolph