Repository navigation
Show the 0.65.1 Cloud welcome whether Cloud is on or off - #18886
Conversation
|
All contributors have signed the CLA ✍️ ✅ |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (3)
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 2 remain after this review. 📝 WalkthroughWalkthroughCloud welcome eligibility now uses the campaign’s seen-version marker and managed-device policy. The CI workflow updates guard routing and preflight checks. The nightly notarization workflow sets polling paths through the runner environment and adds polling test coverage. ChangesCloud welcome eligibility
CI guard workflow
Nightly notarization checks
Priority: ⬇️ Low Estimated code review effort: 3 (Moderate) | ~20 minutes Change: Bug fix Merge Risk: ⚪ Minimal · up to The welcome eligibility and CI guard routing appear ready for normal validation before merge. No actionable issue was established by this review. Pre-merge checks |
|
Restore the reviewed guard routing from 575ab74 while retaining newer Testbox and protected-signing checks. The existing reusable-workflow permission and structure regressions fail before this repair and pass after it. Co-authored-by: Austin Wang <38676809+austinywang@users.noreply.github.com>
Restore the deleted fast-guard test registration cleanup and nightly polling test registration. Resolve notarization receipt paths at runtime, where RUNNER_TEMP is defined, instead of using an invalid job-level runner context.
|
Passes: CI passes on CI passes on Written by |
|
|
Dogfood tours of
|
|
Merge receipt for |
11ff257 Show the 0.65.1 Cloud welcome whether Cloud is on or off (manaflow-ai#18886) # Conflicts: # .github/workflows/auto-resume-nightly-notarization.yml # .github/workflows/ci-guards.yml
The 0.65.1 welcome currently skips people who have already turned Cloud on. This follow-up to merged #17243 shows the campaign once whether Cloud is on or off, except when an organization's MDM profile enforces
DisableCloud.Cloud starts off until the user turns it on; it has no rollout flag. The welcome now checks the managed policy directly and leaves the on/off preference untouched. Exact stable version
0.65.1, the marker written before presentation, and DEBUG/XCTest/UI-test suppression remain intact. Version0.64.25cannot trigger the campaign.Free users also see the welcome. Creating Cloud VMs still requires Pro: the existing welcome action sends signed-in Free users to “Upgrade to Pro” and signed-out users to sign-in.
The first CI run failed before any jobs because #18611's merge restored an older
ci-guards.ymlwhile retaining its new caller and tests. Restore the reviewed guard routing from575ab74328c, preserving the later Testbox and protected-signing checks. The first-classCI fast guardsjob remains authoritative; no validation is bypassed and no token permissions are widened.Also repair the stale test-registry entries from that merge and initialize nightly receipt paths in a runner step, where
RUNNER_TEMPis defined. The existing workflow linter rejected the previous job-levelrunner.tempexpressions; paths and notarization checks are unchanged.Testing
d0e95d6b5fband pass after the CI repair. All 36 guard-routing tests and 18 guard-runner tests pass; repository preflight passes its 16 applicable checks (Swift syntax skipped for the CI-only delta).DisableCloudpreference, exact release selection, marker upgrade/no-repeat, and dev/test suppression.337e4882586failed exactly once: Cloud on with no MDM block was incorrectly rejected. All other original CloudWelcome tests passed.571b8b76ca73ea187c9a576517a90100046f9596, including the Free-account upgrade CTA and all five bundled clips.acb409074603b24704b1e065completed onaws-m4pro-3. The published tagged artifact embeds571b8b76c; its SHA-256 is849c0d3a2ad9d3ef13091362980fc9e35de63c4ca07ad57eece0919c770dfa18. All five bundled MP4 files match the source bytes; workspace reset and cleanup receipts are present. Tagged build. This is a Debug artifact; stable-release eligibility is covered by the focused tests and production launch guards.childPID > 0launcher assertion during enumeration; the third succeeded unchanged on a healthy runner. The existing cleanup receipt repair remains owned by fix(ci): avoid app-host rsync metadata failures #18616.cmuxs-mac-mini-3-glaeda,cmuxs-mac-mini-5-glaeda,cmux11s-mac-mini-glaeda, andcmuxs-mac-mini-5-glaeda-1. The final failure reports an unlocked, awake console but cannot activate Finder; its frontmost-app diagnostics are[ NULL ]. Build and artifact preparation succeeded. No welcome assertion failed, and there is no current UI pass to claim. Fleet GUI recovery is needed before rerunning failed test job114057949055; no guards were weakened and no runner-policy override was applied.cmux11s-mac-mini-glaeda-1. That run confirmed socket readiness from real xcresult app stdout. It is historical evidence, not verification of this follow-up's head.48ba2090321ff4eb8222582ad1b7e03613d39d81; the worktree and submodules are clean.No UI strings, layouts, media or translations change.
Changelog
Fixed: The one-time 0.65.1 Cloud welcome also appears for people who have already turned Cloud on, unless MDM blocks Cloud.