Skip to content

feature: beta release channel builds + per-channel image retention#30

Open
lukepolo wants to merge 1 commit into
mainfrom
feature/beta-release-channel
Open

feature: beta release channel builds + per-channel image retention#30
lukepolo wants to merge 1 commit into
mainfrom
feature/beta-release-channel

Conversation

@lukepolo

@lukepolo lukepolo commented Jul 3, 2026

Copy link
Copy Markdown
Contributor

Part of the cross-repo beta release channel feature (admins switch channels from the web panel; the api reconciles deployment images to :beta/:latest).

Changes

  • Build the beta branch: pushes produce beta, beta-<sha> tags (main is unchanged: latest, <sha>)
  • Per-channel buildcache (buildcache-beta) so beta builds never thrash main's layer cache
  • Replaced actions/delete-package-versions with a tag-based prune script: the action's ignore-versions matches version digests, not container tags (ignore-versions doesn't work actions/delete-package-versions#120), so the old ^buildcache-* protection was a no-op and a beta channel head could be evicted by main-build churn
  • The prune only deletes versions belonging to the channel that was just built; untagged versions are never deleted
  • Added explicit contents: read + packages: write job permissions (prune needs package deletion; a partial permissions block would otherwise zero out checkout access)

🤖 Generated with Claude Code

Build the beta branch into beta-prefixed tags and buildcache, and replace
delete-package-versions (which matches version digests, not container tags)
with a tag-based prune that only touches the channel being built.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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