Repository navigation
chore(analytics): update release churn statistics - #1606
github-actions[bot] wants to merge 1 commit into
Conversation
🐝 Superseded regeneration series
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)):
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. |
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.