Skip to content

Show cooldown only for ecosystems that apply it - #629

Merged
andrew merged 2 commits into
git-pkgs:mainfrom
simonchrz:fix/cooldown-unsupported-ecosystems
Oct 30, 2026
Merged

andrew merged 2 commits into
git-pkgs:mainfrom
simonchrz:fix/cooldown-unsupported-ecosystems

Conversation

@simonchrz

Copy link
Copy Markdown
Contributor

Follow-up to #618. The package page showed the default cooldown for every ecosystem, also for Debian, Alpine, OCI and generic files, where the proxy applies none.

  • handler.CooldownSupported lists the ecosystems whose handlers check cooldown. A test scans the handler sources for cooldown checks and fails when the list and the handlers disagree.
  • The package page shows no cooldown for other ecosystems.
  • The dashboard marks an ecosystem override for one as "(not supported)", e.g. deb: "0".
  • Docs: Helm added to the supported list, with a short note on how it uses created from index.yaml; docs/architecture.md had only npm, PyPI, pub.dev and Composer.

The package page showed the default cooldown for every ecosystem, also
for Debian, Alpine, OCI and generic files, which have no publish time to
check. It now shows none there, and the dashboard marks an ecosystem
override for one as not supported. The docs list Helm, which applies
cooldown from the index's created times.
@simonchrz simonchrz added the bug Something isn't working label Oct 29, 2026
@andrew
andrew merged commit 54ad028 into git-pkgs:main Oct 30, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants