Repository navigation
chore: release v0.8.219 - #6775
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
There was a problem hiding this comment.
Verdict: APPROVE · 0 blockers · 0 important · 0 nits · head da2f1b03
The range v0.8.218..head has exactly #6771, #6767 and #6766, and main has nothing past it. The notes' bullets match draft-changelog.ts for that range word for word, and the summary is accurate. All 13 non-private packages and the 5 plugin manifests are at 0.8.219, the same file set as v0.8.218. None of the three PR bodies has a release prerequisite. Every Actions run at this head passed, including CI (Release checks, Build, Lint), Windows render verification, regression and CodeQL. CI's change detection skipped the test jobs for this version-only diff.
Description
Release v0.8.219: version bump to 0.8.219 across the packages and plugin manifests, and the release notes in
releases/v0.8.219.mdanddocs/changelog.mdx.Changes since v0.8.218: #6771 (a locked Chrome debug.log on Windows no longer fails check, snapshot or render), #6767 (normalize-audio never cuts a clip that is quieter than the target) and #6766 (render with no
-owrites into the project's renders folder). #6771 is the reason for cutting now: Windows exports were failing for some users.No visible change
Version bump and changelog only. Each change in this release was captured in its own PR.