Repository navigation
chore: release v0.8.186 - #6072
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
Edit accuracy: accurate 271 (base branch 271), smooth 158 of thoseThe gate passes. Quarantined, measured but not gated (0) |
vanceingalls
left a comment
There was a problem hiding this comment.
Approving the release at 3f692cb1. Its parent is main's tip, 934c88ba (#6061).
Versions: all 19 published manifests go from 0.8.185 to 0.8.186. That covers the 14 packages/* packages, the three .claude/.codex/.cursor plugins, plugin.json and gemini-extension.json. Only private packages stay unbumped: the root, sdk-playground, studio/frontend, the registry block sources and the skill test corpus.
Notes: v0.8.185 is tagged at 11023821, an ancestor of 934c88ba. git log v0.8.185..934c88ba lists 17 commits. Each one's full SHA appears exactly once in releases/v0.8.186.md and exactly once in the new docs/changelog.mdx entry, next to the matching #N. The API shows each PR merged with that same commit as its merge commit. There are 17 commit links in total, so nothing extra is listed.
Claims: I checked the summary and entries against the PR bodies of #5969, #5971, #5990, #5991, #5992, #5984, #6056 and #6061. Capture motion blur stays opt-in: a root sets data-motion-blur="on" (#5969), and the summary doesn't say it's on by default. "Turns itself off, saying why" matches what shipped: the defect list (#5971) and the once-per-timeline decision (#5990) turn blur off, the reason codes (#5991) say why, and check's motion_blur_off warning (#5992) tells the author. The history fix applies to the read commands only (history, show, peek); undo, restore and the other write commands still fail as before. The headline matches that. The init --video entry matches #5984.
Scope: 21 files, +96/-19: 19 one-line version bumps, +39 in the changelog and the new 38-line release file. Nothing else changes.
CI: green at 3f692cb1. All 8 required checks pass (Build, Typecheck, Test, Test: runtime contract, Tests on windows-latest, Render on windows-latest, Semantic PR title, regression), and none of the 77 check-runs failed. Comments was skipped, since no source changed.
Verdict: APPROVE
Reasoning: Every published manifest is bumped, all 17 merged PRs are in the notes once each with the right SHAs, the headline claims match what shipped, the diff contains only the release, and required CI is green at this head.
— Via
Capture motion blur now reaches renders and Studio, and it turns itself off, saying why, on pages it cannot blur safely.
hyperframes historylists its entries even when it cannot write them, andinit --videoframes the project to the clip's shape.Changes
release:prepare 0.8.186 --from v0.8.185 --no-tag; the release workflow tags on merge).releases/v0.8.186.md: 17 PRs, every one merged since v0.8.185. Checked againstgit log v0.8.185..main: none missing.docs/changelog.mdx: the matching v0.8.186 entry.No visible change
Version bump and changelog only; each change was captured in its own PR.