Skip to content

docs(changelog): port the 0.12.0 section from release/0.12.0 (Explore is a preview) - #27778

Merged
bolichen97 merged 1 commit into
mainfrom
docs/changelog-0.12.0-explore-preview
Nov 2, 2026
Merged

bolichen97 merged 1 commit into
mainfrom
docs/changelog-0.12.0-explore-preview

Conversation

@bolichen97

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: Make the ## [0.12.0] section of CHANGELOG.md on main byte-identical to release/0.12.0 again.

#27666 (0.12.0-rc.4) moved Explore into "Previews you can turn on" on the release branch after #27449 / #27603 put it behind a default-off Feature Preview. release.md "Changelog" asks that the section be ported to main verbatim.

Why it matters

Without this, main tells readers Explore is on for everyone, which is no longer true.

Not a goal

  • No code change. No other release section.

What changed (motivation → approach → change)

CHANGELOG.md only: the ## [0.12.0] section is replaced with the one on release/0.12.0 at 223be3e172. That moves Explore under previews, renames "Explore and settings" to "Settings and themes", and carries one wording change in "Mates and channels" that was already on the release branch. A diff of the two sections is empty.

Backwards compatibility

Compatible: docs only.

Tests

test_changelog_handler.py, test_changelog_history_gate.py, test_changelog_parse.py pass.

Proof: not provable -- CHANGELOG only, no behavior change

Manual verification

Diffed the ## [0.12.0] section of this branch against release/0.12.0: identical.

Screenshots / video

None: no UI change.

Related Issues

Part of #27424

Sibling sweep

Siblings: none -- one docs section.

Pattern harvest

Not generalizable: a routine CHANGELOG port.

Checklist

  • At most two commits (one is the norm), with a Conventional Commits title
  • Existing tests pass and new tests added for new functionality
  • Self-review completed; code follows project style guidelines
  • Documentation updated (if applicable)
  • No secrets, credentials, or internal references in the diff

@bolichen97
bolichen97 requested review from a team and KiroCrewCaptain as code owners November 2, 2026 05:50
@github-actions github-actions Bot added the readiness: checking Automated validation is still running label Nov 2, 2026
@github-actions

github-actions Bot commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — ⏭️ skipped

Revision f60be19274f564358d77ed5314526825d7cffcd1 ships no reviewable capability (docs, tests or generated files only), so there is nothing to inventory. Does not block merge.

@github-actions

github-actions Bot commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5) — ⏭️ skipped

Revision f60be19274f564358d77ed5314526825d7cffcd1 touches no user-facing surface (no changes under website/ or committed screenshots), so the UX review was skipped. Does not block merge.

@github-actions

github-actions Bot commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5) — ✅ PASS

Design-level review of f60be19274f564358d77ed5314526825d7cffcd1 — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

Design-Verdict: PASS

Docs-only change: it ports the CHANGELOG section verbatim from the release branch, which is the flow release.md "Changelog" sets out. Nothing renders, nothing is taken away, and no reader is affected.

[DESIGN-REVIEWED] f60be19

Description read

[DESCRIPTION-READ] acc9b31fac669cf56970cbb085c040e1246018a933da5784b86d8f14b6371888

That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@bolichen97
bolichen97 merged commit 322deaa into main Nov 2, 2026
34 of 37 checks passed
@bolichen97
bolichen97 deleted the docs/changelog-0.12.0-explore-preview branch November 2, 2026 05:52
@github-actions

github-actions Bot commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ✅ no blocking findings

GPT 6.1 completed its review of f60be19274f564358d77ed5314526825d7cffcd1 and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] f60be19

False positive or not applicable? A repository writer can comment:
/ai-review override gpt f60be19274f564358d77ed5314526825d7cffcd1 false-positive: <reason, 20 to 500 characters>

@github-actions github-actions Bot removed the readiness: checking Automated validation is still running label Nov 2, 2026
@github-actions

github-actions Bot commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ no blocking findings

Reviewed f60be19274f564358d77ed5314526825d7cffcd1 — this comment is updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] f60be19

Verdict parsed from the review's SHA-scoped output markers for commit f60be19274f564358d77ed5314526825d7cffcd1.

False positive or not applicable? A repository writer can comment:
/ai-review override fable f60be19274f564358d77ed5314526825d7cffcd1 false-positive: <reason, 20 to 500 characters>

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