[codex] add xcode 26 requirement blog article#595
Merged
Conversation
Contributor
|
Caution Review failedAn error occurred during the review process. Please try again later. 📝 WalkthroughWalkthroughA new blog post is added documenting Apple's requirement that starting April 28, 2026, App Store Connect will reject uploads built with older toolchains unless using Xcode 26 and iOS 26 SDK. The post provides guidance for updating local builds, CI systems, and dependencies. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (3)
apps/web/src/content/blog/en/xcode-26-requirement-for-capacitor-apps.md (3)
41-44: Anchor the “Capgo Build is already on Xcode 26” internal claim to a source/date to avoid staleness.The statement is likely true, but it’s a long-lived blog post and could become inaccurate as Capgo Build updates over time. Consider adding:
- the “as of” date (e.g., publish date 2026-04-29), and/or
- a link to a “native build list” / status page that proves the current Xcode version.
(Your post already has a “native build list” image + alt text at the top, so you may just want to link it into this paragraph.)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/web/src/content/blog/en/xcode-26-requirement-for-capacitor-apps.md` around lines 41 - 44, Edit the paragraph that claims "our current iOS build system is already running on Xcode 26" to anchor it to a verifiable source/date: add an "as of" date (e.g., "as of 2026-04-29") and include a link to the existing native build status (the native build list image/status page referenced earlier) so readers can verify current Xcode versions; update the sentence that mentions Capgo Build/Xcode 26 to read with the date and a parenthetical link to the status page or native build list image.
55-60: Tighten the closing sentence to avoid redundancy and keep it consistent with the earlier “Xcode 26 or later” wording.Line 57 (“since April 28, 2026, older Xcode builds are no longer enough…”) is consistent in spirit, but since earlier wording is being corrected to “Xcode 26 or later”, the final takeaway should follow the same precision. (developer.apple.com)
Suggested edit (consistency)
-This is Apple’s normal yearly toolchain cutoff, but the enforcement date is real: **since April 28, 2026**, older Xcode builds are no longer enough for App Store uploads. +This is Apple’s normal yearly toolchain cutoff, but the enforcement date is real: **from April 28, 2026 onward**, you need Xcode 26+ (with the required 26.x SDKs) for App Store uploads.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/web/src/content/blog/en/xcode-26-requirement-for-capacitor-apps.md` around lines 55 - 60, The closing sentence under the "Final Take" heading is redundant and should be tightened to match the earlier precise phrasing "Xcode 26 or later"; replace the current sentence that reads "If you build elsewhere, now is the time to update your environment before your next iOS release window." with a concise variant that explicitly says to update to "Xcode 26 or later" (e.g., "If you build elsewhere, update your environment to Xcode 26 or later before your next iOS release."), keeping the rest of the paragraph unchanged.
33-36: Reduce repetitive “If …” bullet starters (matches your static analysis hint).The three consecutive bullets starting with “If” is flagged by your static analysis. It’s not wrong, but rewording improves readability and keeps the article in a polished “Capgo voice” style.
Suggested edit (bullet readability)
-- If you build locally on a Mac, you need Xcode 26 installed and selected. -- If you use your own CI pipeline, your macOS runner image needs Xcode 26. -- If you have native dependencies or older plugins, rebuild once on the new SDK and test a fresh archive before your next release. +- For local Mac builds, you need Xcode 26 installed and selected. +- For self-managed CI, your macOS runner image needs Xcode 26. +- If you have native dependencies or older plugins, rebuild once on the new SDK and test a fresh archive before your next release.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/web/src/content/blog/en/xcode-26-requirement-for-capacitor-apps.md` around lines 33 - 36, The three consecutive bullets beginning "If you build locally on a Mac, you need Xcode 26 installed and selected.", "If you use your own CI pipeline, your macOS runner image needs Xcode 26.", and "If you have native dependencies or older plugins, rebuild once on the new SDK and test a fresh archive before your next release." are repetitive; rephrase them to remove repeated "If" starters and improve flow by adding a short lead-in sentence (e.g., "Ensure Xcode 26 is used in all build environments:") and then convert the three lines into concise, parallel items that start with distinct verbs or nouns (e.g., "Local mac builds: install and select Xcode 26", "CI runners: use a macOS image with Xcode 26", "Native deps/plugins: rebuild on the new SDK and verify a fresh archive"). Ensure the original meanings of the three bullets are preserved while applying consistent tone and parallel structure.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@apps/web/src/content/blog/en/xcode-26-requirement-for-capacitor-apps.md`:
- Around line 19-28: Update the article wording to match Apple’s precise
phrasing by replacing instances of “Xcode 26” with “Xcode 26 or later” and
replacing vague phrases like “older baseline” with an explicit phrase such as
“earlier than Xcode 26 / the matching SDK versions” (e.g., change the opening
sentence that starts “As of April 28, 2026, Apple requires…” and the paragraph
beginning “Starting on **April 28, 2026**, uploads built with the older
baseline…”), and ensure the sentence about SDKs reads “built with Xcode 26 or
later using the iOS 26 SDK (or matching SDKs for iPadOS, tvOS, visionOS, and
watchOS)” so all occurrences (including the Capgo Build note) use the exact
“Xcode 26 or later” phrasing.
---
Nitpick comments:
In `@apps/web/src/content/blog/en/xcode-26-requirement-for-capacitor-apps.md`:
- Around line 41-44: Edit the paragraph that claims "our current iOS build
system is already running on Xcode 26" to anchor it to a verifiable source/date:
add an "as of" date (e.g., "as of 2026-04-29") and include a link to the
existing native build status (the native build list image/status page referenced
earlier) so readers can verify current Xcode versions; update the sentence that
mentions Capgo Build/Xcode 26 to read with the date and a parenthetical link to
the status page or native build list image.
- Around line 55-60: The closing sentence under the "Final Take" heading is
redundant and should be tightened to match the earlier precise phrasing "Xcode
26 or later"; replace the current sentence that reads "If you build elsewhere,
now is the time to update your environment before your next iOS release window."
with a concise variant that explicitly says to update to "Xcode 26 or later"
(e.g., "If you build elsewhere, update your environment to Xcode 26 or later
before your next iOS release."), keeping the rest of the paragraph unchanged.
- Around line 33-36: The three consecutive bullets beginning "If you build
locally on a Mac, you need Xcode 26 installed and selected.", "If you use your
own CI pipeline, your macOS runner image needs Xcode 26.", and "If you have
native dependencies or older plugins, rebuild once on the new SDK and test a
fresh archive before your next release." are repetitive; rephrase them to remove
repeated "If" starters and improve flow by adding a short lead-in sentence
(e.g., "Ensure Xcode 26 is used in all build environments:") and then convert
the three lines into concise, parallel items that start with distinct verbs or
nouns (e.g., "Local mac builds: install and select Xcode 26", "CI runners: use a
macOS image with Xcode 26", "Native deps/plugins: rebuild on the new SDK and
verify a fresh archive"). Ensure the original meanings of the three bullets are
preserved while applying consistent tone and parallel structure.
🪄 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: defaults
Review profile: CHILL
Plan: Pro
Run ID: 56120c74-dbdd-431e-850a-ba96cc95235c
📒 Files selected for processing (1)
apps/web/src/content/blog/en/xcode-26-requirement-for-capacitor-apps.md
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why
Apple now requires App Store Connect submissions to be built with Xcode 26. We need a site article covering the requirement in Capgo’s voice without referencing Capawesome.
Validation
bun run ci:verify:webSummary by CodeRabbit