Clean non-stable seeded release assets#27
Conversation
- Broaden seeded release cleanup to all stale Installer-* releases.\n- Previously, cleanup only matched older stable semver tags, so release-candidate tags could keep bundled seeded IMG assets.\n- That conflicted with the policy that bundled images should only exist for the latest stable release.\n- The workflow now removes seeded IMG assets from any non-current Installer-* tag that is older than the current stable version or is not a stable semver tag.\n- Online installer assets are left untouched when present, and docs now call out older or non-stable cleanup.
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro (Legacy) Run ID: 📒 Files selected for processing (3)
Comment |
Summary
Installer-*tags, not just older stable semver tagsWhy
The latest-stable seeded image policy should not leave bundled seeded artifacts on release-candidate tags. Older and non-stable releases should use the online installer path instead.
Validation
.github/workflows/update-unraid-release-lock.ymlgit diff --check