feat(blog): "Capgo Build leaves beta" announcement post#740
feat(blog): "Capgo Build leaves beta" announcement post#740WcaleNieWolny wants to merge 3 commits into
Conversation
New EN post announcing Capgo Build graduating from beta, in the WcaleNieWolny first-person voice. Includes a CSS timeline of what shipped (Oct 2025 -> GA) and source-verified sections on guided onboarding (the CLI build-init wizard, iOS + Android), AI build-log analysis, and the reliability work that hardened the build fleet. Cross-links /native-build/, the cloud-build docs, and the Windows tutorial; NewsArticle JSON-LD + OG tags auto-derive from frontmatter. Adds an on-brand hero (apps/web/public/capgo-build-leaves-beta.webp) built on the Capgo design system (Airbnb Cereal, azure on gray-900, diamond-mark watermark), rendered at 2x, optimized to ~60KB, with a safe margin for the 3:2 object-cover crop.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughA new blog post announces that Capgo Build has graduated from beta to production. The post includes metadata, an introductory narrative about cloud compilation capabilities, a timeline of beta improvements from October 2025 to May 2026, features that stabilized during beta, guidance on integrating with Live Updates, and a call-to-action with a sample CLI command. ChangesBlog Post Launch
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c9365aa5f1
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@apps/web/src/content/blog/en/capgo-build-leaves-beta.md`:
- Around line 16-21: The frontmatter key published: true conflicts with the
in-body draft warning comment; update them to be consistent by either (A) set
published: false in the frontmatter to keep the draft state (change the value of
published) or (B) if ready to publish, remove the draft-warning comment and
ensure published: true stays; make this change in the same PR so the file no
longer contains both the draft comment and published: true simultaneously.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: f06d9b76-f518-4b0b-a823-74b621d5cb58
📒 Files selected for processing (2)
apps/web/public/capgo-build-leaves-beta.webpapps/web/src/content/blog/en/capgo-build-leaves-beta.md
head_image is emitted as og:image/twitter:image by SEO.astro; AGENTS.md requires png or jpg (not webp) for social meta images. Replaced the webp hero with a 1600x900 JPEG (~217KB, grain-dithered to avoid banding on the dark gradient) and repointed head_image. Flagged by Codex on PR #740.
There was a problem hiding this comment.
♻️ Duplicate comments (1)
apps/web/src/content/blog/en/capgo-build-leaves-beta.md (1)
16-21:⚠️ Potential issue | 🟠 Major | ⚡ Quick winResolve draft/publish contradiction before merge.
published: trueconflicts with the in-body draft warning (“do not publish”). Keep only one state in this PR (either draft or publish-ready) to avoid accidental release.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@apps/web/src/content/blog/en/capgo-build-leaves-beta.md` around lines 16 - 21, The frontmatter currently has published: true but the body contains a DRAFT warning; resolve the contradiction by either setting published: false (or removing the published field) if the post remains a draft, or remove the draft warning/comment block and ensure no "PLACEHOLDER" markers remain if you intend to publish; locate the frontmatter key published and the in-body DRAFT/PLACEHOLDER comment and make them consistent.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Duplicate comments:
In `@apps/web/src/content/blog/en/capgo-build-leaves-beta.md`:
- Around line 16-21: The frontmatter currently has published: true but the body
contains a DRAFT warning; resolve the contradiction by either setting published:
false (or removing the published field) if the post remains a draft, or remove
the draft warning/comment block and ensure no "PLACEHOLDER" markers remain if
you intend to publish; locate the frontmatter key published and the in-body
DRAFT/PLACEHOLDER comment and make them consistent.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: fc96d931-71f0-4739-a498-e9d5125fc850
⛔ Files ignored due to path filters (1)
apps/web/public/capgo-build-leaves-beta.jpgis excluded by!**/*.jpg
📒 Files selected for processing (1)
apps/web/src/content/blog/en/capgo-build-leaves-beta.md
…raft guard Resolves the published: true vs in-body draft-warning contradiction flagged by CodeRabbit. The post still has open pre-merge items (confirm Android onboarding shipped to prod, final copy pass), so it stays published: false. Also rewrote the stale draft comment (it referenced placeholders that are now all filled).
|



What
apps/web/src/content/blog/en/capgo-build-leaves-beta.md— "Capgo Build leaves beta", announcing Capgo Build graduating from beta.apps/web/public/capgo-build-leaves-beta.webp(2560×1440, ~60 KB).Why
First-party product news for the builder — a canonical, shareable announcement (vs. the SEO/tutorial bulk of the blog). Doubles as a rankable evergreen page and the
og:imagefor social.Details
a-brand-new-organization-system/capacitor-social-login-releaseposts.build initwizard (iOS via App Store Connect API; Android via Google OAuth auto-provisioning).capgo_builderai-analyzeendpoint (--ai-analytics).build-orchestration(single-source-of-truth status, audit trail, status reconciliation, auto-retry).#119effongray-900, the diamond mark as a background watermark. Rendered at 2×, designed with a safe left margin so the blog's 3:2object-covercrop never clips the headline.articletags auto-derive from frontmatter. Verified rendering in the dev server.build init --platform androidas live, but per the wiki it wasCap-go/capgoPR #2064 (draft) + #2317 (in review) as of 2026-05-22. If it hasn't merged to prod, soften or hold that paragraph.<!-- DRAFT … -->comment at the top of the post body — no placeholders remain.published: true— merging publishes it live.Notes
thumbnails/working files (the options gallery, render source, fonts, intermediate PNG) are intentionally not committed — scratch only.Summary by CodeRabbit