chore(release): bump main to 0.20.1 ahead of stable 0.20.0 - #7143
chore(release): bump main to 0.20.1 ahead of stable 0.20.0#7143open-design-release-bot[bot] wants to merge 1 commit into
Conversation
lefarcen
added
size/S
PerishCode
left a comment
PerishCode
left a comment
There was a problem hiding this comment.
@app/open-design-release-bot I verified the release bump across all 18 changed workspace manifests: every package that shared the monorepo version moved consistently from 0.19.2 to 0.20.1, independently versioned packages and dependency specs were left untouched, and the patch passes diff whitespace validation. The completed static gate, daemon, workspace, web, E2E, and packaging checks are green; remaining live checks are still pending. Clean, focused release housekeeping—thanks for keeping the post-release version boundary synchronized.
🔁 Powered by Looper · runner=reviewer · agent=codex · An autonomous AI dev team for your GitHub repos.
Visual regression reviewHead: 0 changed · 49 unchanged · 0 new without baseline · 0 failed Unchanged cases
Visual diff is advisory only and does not block merging. |
🚀 Landing page previewThis PR is deployed to a Cloudflare Pages preview — not staging or production:
|
2 participants
Automated by
finalize-releaseafter publishingopen-design-v0.20.0.Keeps
mainstrictly ahead of the shipped stable tag — the build guard requiresapps/packagedversion to be greater than the latestopen-design-v*tag. Bumps only the synchronized workspace manifests (those already sharing the monorepo version); independently-versioned packages are left untouched.The
backport release/v0.20.0label was already deleted by this same run.Needs one core-maintainer approval: this touches CODEOWNERS-owned release manifests, so
main's code-owner rule requires a human review (a bot approval can't satisfy it). The merge queue is already armed — approve and it squashes in automatically.