refactor(ci): drop dedicated update-package-index-* chain #74

Merged

pat-s merged 1 commit from pr/drop-update-package-index-chain into main

2026-05-28 12:00:37 +00:00

pat-s commented

2026-05-28 11:42:09 +00:00

Owner

Summary

process-updates-* already calls bincraft::upload_package_index() at the end of every daily delta run, and with #71 the CDN purge happens there too.

The dedicated update-package-index-* chain re-ran the same upload_package_index() against the same S3 prefixes — once per platform per day — and was serialized via depends_on: purely to dodge S3 rate limits.

Net effect: ~40 min cold rebuild × 14 platforms = ~9 h/day of duplicated work, with no consumer waiting on it (process-updates had already published the fresh index).

This deletes the 14 chain files (~1.1k lines). The matching update-package-index / update-package-index-* cron entries on the Crow side become inert with the YAMLs gone and can be removed in a follow-up cron-config change.

Best reviewed alongside (or after):

#71 — purge CDN after process-updates
#72 — guard bincraft reinstall
#73 — drop redundant cranlike/desc installs

Risks

If process-updates-* ever fails for a given platform, the chain used to act as a daily safety net for the PACKAGES index. Failures will now surface only via the missing daily push instead of being silently masked. The existing weekly-audit-missing-* workflow continues to flag stale state.
local/manual-package-index-update.R still exists for one-off manual rebuilds.

## Summary `process-updates-*` already calls `bincraft::upload_package_index()` at the end of every daily delta run, and with #71 the CDN purge happens there too. The dedicated `update-package-index-*` chain re-ran the same `upload_package_index()` against the same S3 prefixes — once per platform per day — and was serialized via `depends_on:` purely to dodge S3 rate limits. Net effect: ~40 min cold rebuild × 14 platforms = ~9 h/day of duplicated work, with no consumer waiting on it (process-updates had already published the fresh index). This deletes the 14 chain files (~1.1k lines). The matching `update-package-index` / `update-package-index-*` cron entries on the Crow side become inert with the YAMLs gone and can be removed in a follow-up cron-config change. Best reviewed alongside (or after): - #71 — purge CDN after process-updates - #72 — guard bincraft reinstall - #73 — drop redundant cranlike/desc installs ## Risks - If `process-updates-*` ever fails for a given platform, the chain used to act as a daily safety net for the PACKAGES index. Failures will now surface only via the missing daily push instead of being silently masked. The existing `weekly-audit-missing-*` workflow continues to flag stale state. - `local/manual-package-index-update.R` still exists for one-off manual rebuilds.

pat-s added 1 commit

2026-05-28 11:42:10 +00:00

refactor(ci): drop dedicated update-package-index-* chain 9a0e47a2e8

process-updates-* already calls bincraft::upload_package_index() at
the end of each daily run, and PR #71 added the CDN purge there too.
The 14-step update-package-index-* chain duplicated that work
(~40 min cold rebuild per platform) and serialized purely to dodge
S3 rate limits, even though no one was waiting for the index after
process-updates had landed it.

Deletes the chain. The 'update-package-index' and 'update-package-index-*'
cron names referenced inside those files become inert with the YAMLs;
the matching cron entries on the Crow side can be removed in a follow-up.

pat-s force-pushed pr/drop-update-package-index-chain from 9a0e47a2e8 to 1b297b1194

2026-05-28 11:59:50 +00:00

Compare

pat-s merged commit 9cbb43dada into main

2026-05-28 12:00:37 +00:00

pat-s referenced this pull request from a commit

2026-05-28 12:00:37 +00:00

refactor(ci): drop dedicated update-package-index-* chain (#74)

pat-s deleted branch pr/drop-update-package-index-chain

2026-05-28 12:00:37 +00:00