Skip to content

chore(analytics): update release churn statistics - #1600

Closed
github-actions[bot] wants to merge 1 commit into
mainfrom
chore/update-churn-20261025
Closed

github-actions[bot] wants to merge 1 commit into
mainfrom
chore/update-churn-20261025

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Automated update of release-over-release update churn, layer reuse efficiency, and zstd compression statistics triggered by updated SBOMs and OCI manifests. Requires maintainer approval before merge per repository policy.

@hivecommons-hive

Copy link
Copy Markdown
Contributor

🐝 Superseded regeneration series

github-actions[bot] has 3 open PRs regenerating the same file(s). This one is the newest, so the 2 older one(s) are superseded by construction:

Posted once on the newest PR rather than on each of them, so a daily regeneration does not produce a daily comment on every PR in the series.

Evidence — identical changed-file set (1 file(s)):

  • static/data/update-churn.json

This is a suggestion, not a verdict. Hive will not close, label, approve or merge anything here — a human decides.

It was produced by comparing changed-file sets across open PRs, which is a candidate generator: PRs that share a file are not necessarily the same work. Here the patches DIFFER, so this is the weaker tier: dependency-bump PRs that edit one shared manifest, and unrelated fixes to one busy file, both land in it. Read the diffs before acting.

@hivecommons-hive hivecommons-hive Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Reviewed — no findings from correctness, security, intent-alignment, style, docs-currency.

Confidence: 5/5 (safe)

— hive: agent=reviewer backend=copilot model=claude-fable-5.1 copilot=1.0.88

@Danathar

Copy link
Copy Markdown
Contributor

Closing as superseded: #1606 is the newer churn refresh, and both were generated by the old script, which rewrites already-published release points. #1604 makes the churn data append-only; the next scheduled run after it merges will produce a correct refresh.

@Danathar Danathar closed this Oct 26, 2026
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