ci: finish soldr build migration for PyO3 ext + final else arm (#1012 PR 2 followup) - #799
Conversation
…PR 2 followup) Completes the soldr#1012 PR 2 migration in fbuild's template. PR 6 (#797) migrated the win-msvc xwin arm; this followup migrates the remaining \`soldr cargo build\` invocations to \`soldr build\`: * PyO3 ext, Linux→win-msvc arm: \`cargo xwin build\` → \`soldr build\` * PyO3 ext, macos_cross arm: \`soldr cargo build\` → \`soldr build\` * PyO3 ext, macOS native arm: \`soldr cargo build\` → \`soldr build\` * PyO3 ext, fallback arm: \`soldr cargo build\` → \`soldr build\` * release binaries, final else arm: \`soldr cargo build\` → \`soldr build\` After this every soldr-surface invocation in the template uses the blessed verb. The explicit-legacy-tool invocations (\`cargo zigbuild\` for linux musl, \`soldr cargo zigbuild\` for mac cross via zigbuild) stay on their existing tools — they absorb into the blessed path under soldr#1010 Phase 5 (mac zigbuild) and Phase 8 (legacy opt-in flags) tracking. Supersedes PR #796 (which was forked from main before PR 6 and caught merge conflicts during rebase). Same surface effect. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
Warning Review limit reached
More reviews will be available in 14 minutes and 36 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
template_native_build.yml pinned soldr v0.7.63 in #797/#799 for the blessed-cross-compile + soldr-clang-shim work, but soldr's latest published release is v0.7.59 (zackees/soldr has no v0.7.63 yet). The 404 from the GitHub release fetch failed every native-build lane in release-auto, blocking the 2.3.12 release fbuild needed to ship the #800 (Phase 4 stage 2) embedded-zccache work. Reverts both halves of the pin (action ref + version arg) to the last working pair. Restore to v0.9.63 + 0.7.63 once soldr cuts that release. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
soldr v0.7.65 published, unblocking the configuration #797/#799 was authored against. Brings back the soldr-clang-shim that routes ring 0.17.x's hardcoded c.compiler("clang") to clang-cl for the *-pc-windows-msvc targets, and re-adds the aarch64-pc-windows-msvc release lane that the v2.3.12 release was deferred without. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
1 participant
Completes the soldr#1012 PR 2 migration. PR #797 (PR 6) handled the win-msvc xwin arm; this followup migrates the remaining soldr-surface invocations. Same byte-identical artifacts today.
Supersedes #796 which was forked from main before PR 6 landed and caught merge conflicts during rebase.