chore: refresh GHCR + Maven Central counts (2026-05-16)#658
Merged
Conversation
Peeked at https://github.com/orgs/runcycles/packages and the per-package pages, and updated manual-package-counts.json: cycles-server-admin: 1290 -> 1290 (no change; still 1.29K on both org and per-package pages) cycles-server: 1030 -> 1040 (1.04K on both pages, +/- 5) cycles-dashboard: 669 -> 669 (exact integer, no change) cycles-server-events: 373 -> 424 (exact integer) Aggregate ghPackages: 3362 -> 3423 (+61). The cached value in installs-cache.json (2959) is below both old and new sums; the HWM logic in installs.data.ts:498 takes the manual sum as ghPackages and will refresh the cache on the next build. Convention for these refreshes (per past chores like 986f905): - Per-package pages below ~1K show exact integers; record as integers. - Per-package pages above ~1K round (1.04K -> 1040); accuracy +/- 5. - Only the manual file is edited here; the cache catches up on build. - lastVerifiedAt updated to today.
From Sonatype Central portal Statistics: io.runcycles: 1589 -> 1889 (+300) Unique sources: 225 -> 253 (+28) Companies: 55 -> 56 (+1) `_mavenBreakdown` carries totals only this refresh (no monthly split captured). mavenLastVerifiedAt updated to today. The cached `maven: 1477` in installs-cache.json is below both old (1589) and new (1889) manual values; the HWM logic in installs.data.ts:487 (`Math.max(mavenFetched, cached.maven)`) lifts it to 1889 on the next build, contributing to the displayed total alongside the +61 GHCR update in the previous commit on this branch.
amavashev
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Refreshed both GHCR pull counts and Maven Central download stats in `.vitepress/theme/manual-package-counts.json`. Two commits on this branch — one for GHCR, one for Maven — both follow the file's existing convention.
GHCR pull counts (commit a6c4f8a)
Source: https://github.com/orgs/runcycles/packages and per-package pages.
Maven Central counts (commit 25c92b4)
Source: Sonatype Central portal → Statistics → Downloads.
`lastVerifiedAt` and `mavenLastVerifiedAt` both updated to 2026-05-16.
Why this matters
The GitHub REST API does not populate `download_count` for container packages (verified 2026-05-07 per the file's `_note`), and Maven Central has no public downloads API. So this manual file is the source of truth for both `ghPackages` and `maven` in installs-cache.json. The build-time loader takes both sums via HWM and rolls them into the displayed total.
Convention applied
Matches prior refresh chores like 986f905 (GHCR) and b3d417d (Maven).
Cache impact (corrected)
This PR's own contribution to the displayed total is +361. The cache happens to be further behind because the last write to `installs-cache.json` was the scheduled `update-github-counts.mjs` script on 2026-05-15, and that script doesn't read the manual file for `ghPackages` / `maven` (only the build-time loader does). So a separate +515 of catch-up to the prior manual file will land on the same build, regardless of this PR.
So:
Test plan