Skip to content

test(updater-probe): remove the probe casks after the per-cask updater test - #52

Merged
edbfi merged 1 commit into
mainfrom
test/remove-updater-probes
Oct 12, 2026
Merged

edbfi merged 1 commit into
mainfrom
test/remove-updater-probes

Conversation

@edbfi

@edbfi edbfi commented Oct 12, 2026

Copy link
Copy Markdown
Owner

What changed

Removes everything #51 added: both probe casks, their pipelines, the inspect-macos.py entries and the test entries. git diff 2e23e76 (#50's merge) is empty after this PR.

Evidence: the production test of #49/#50

run setup result
A both probes 0.0.1 → upstream 0.0.2 success. publish (updater-probe) and publish (updater-probe-b) ran in parallel (20:48:31–40). Then push (updater-probe-b) (20:49:40–54) and push (updater-probe) (20:49:56–50:03) ran one after the other: 075ab3c → cb19908 → 0b4bb0e, both fast-forwards from the deploy key, both rule suites bypass, and push CI passed on both. The hosted digests equal the built DMGs.
B dispatched again success. All eight checks reported no update and nothing after plan ran.
C both → upstream 0.0.3; a different UpdaterProbeB-0.0.3.dmg put on updater-probe-b-latest first failure, as intended. publish (updater-probe-b) failed with "Hosted UpdaterProbeB-0.0.3.dmg differs from upstream". publish (updater-probe) succeeded, published listed only it, and it went through verify and push (0b4bb0e → c14cf2a, bypass). probe-b got no verify or push jobs.

With eight casks, update-casks.yml needed no timeout change.

After merge

Delete updater-probe-latest and updater-probe-b-latest here, then the four updater-probe{,-b}-v0.0.{2,3} releases and tags in edbfi/edbfi-ci-playground. Doing it in that order keeps a scheduled run from hitting a missing release.

Owner actions

None.

…r test

Returns the tree to its state at #50 (2e23e76). After this merges, the probes' -latest releases here and their upstream releases and tags in edbfi/edbfi-ci-playground are deleted.

Signed-off-by: edbfi <326875205+edbfi@users.noreply.github.com>

@pullfrog pullfrog Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ No new issues found.

Reviewed changes: the single commit on test/remove-updater-probes, reviewed against main.

  • Probe casks removed: Casks/test/updater-probe.rb and Casks/test/updater-probe-b.rb are deleted.
  • Probe pipelines removed: pipelines/updater-probe{,-b}/{config.env,resolve.sh} are deleted, so discover.sh no longer globs them.
  • Registries trimmed: both APPS entries in scripts/inspect-macos.py and both tokens in test_discovery_separates_kinds are dropped, and the two sets still match.

A tree-wide grep for updater-probe and UpdaterProbe is now empty. Nothing else references Casks/test: the remaining uses are temp trees built inside tests/test_updater.py and scripts/tests/test_pipeline.py. With fewer casks the DeadlineTests arithmetic against update-casks.yml only gets looser. The out-of-tree cleanup of the -latest releases and playground tags is described in the PR body in a safe order.

Pullfrog  | Fix it ➔ | View workflow run | Using claude-sonnet-5-5 | 𝕏

@edbfi
edbfi merged commit b6d9f34 into main Oct 12, 2026
8 checks passed
@edbfi
edbfi deleted the test/remove-updater-probes branch October 12, 2026 20:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant