test(nightly-next): each app reads the feed its publisher writes

Merged
TE
1mo ago
+88-0

Leo (2026-10-25 22:50Z): "but where are the nightlies? i dont see a new thing on the bottom left"

claude-sr2's order (2): "check that every build's SUFeedURL and the publish step point at the same feed, with a CI test that fails if the feed an app checks isn't the one the publisher writes."

Checked. Both nightly-next apps already read the feed their publisher writes:

  • cmux NEXT bakes SUFeedURL = ${CHANNEL_FEED_BASE}/${NIGHTLY_APPCAST}. feedBase is NIGHTLY_NEXT_FEED_BASE and the variant is arm64, so that's https://files-next.cmux.com/nightly-next/next/appcast-arm64.xml. "Upload nightly-next appcasts to R2" writes ${NIGHTLY_NEXT_R2_PREFIX}appcast-arm64.xml (nightly-next/next/), which is the same object.
  • cmux NIGHTLY (re-signed copy) bakes LEGACY_FEED_URL = ${NIGHTLY_NEXT_LEGACY_FEED_BASE}/${LEGACY_APPCAST} in sign-nightly-identity-legacy. publish-nightly-identity-legacy uploads nightly-next/appcast-arm64.xml, which is the same object.

Tonight's stale NIGHTLY wasn't a URL mismatch: the legacy jobs 403'd on the Actions token's rate limit. #25172 catches that at runtime (watching the feed and re-running the failed job).

What changes: tests/test_nightly_next_identity.py gains test_each_app_reads_the_feed_its_publisher_writes, which already runs in ci-guards. It binds each piece above, including the same LEGACY_APPCAST in the sign and publish jobs and the NEXT feed base equalling host + R2 prefix. It also pins the legacy feed URL to the one main's nightly_next_feed_watch.py watches.

Mutation check: pointing the legacy upload at $prefix/next/... fails the test, and so does changing NIGHTLY_NEXT_R2_PREFIX. 8/8 pass on the real workflow.

Test only; no workflow change. Risk: none at runtime.

No capture: CI test only, no UI.

Agent session: cosmic-gray

šŸ¤– Generated with Claude Code


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need.