Skip to content

fix(release): prune old deb packages and preserve docs on gh-pages#650

Merged
camathieu merged 1 commit intomasterfrom
fix/apt-release-pool-pruning
Feb 28, 2026
Merged

fix(release): prune old deb packages and preserve docs on gh-pages#650
camathieu merged 1 commit intomasterfrom
fix/apt-release-pool-pruning

Conversation

@camathieu
Copy link
Copy Markdown
Member

What

Fix two issues in apt_release.sh that cause gh-pages bloat and break the docs site.

Why

Each release was adding ~180 MB of .deb packages to the pool without removing old versions. After RC3 + RC5, gh-pages was 530 MB. Additionally, git add apt/ was only staging the APT directory in the orphan commit, silently dropping the VitePress docs on every release force-push.

Changes

  • Pool pruning — before copying new .deb files, remove old versions of the same package/architecture from the pool
  • Docs preservation — change git add apt/git add -A so the orphan commit includes all existing content (docs, Helm index, etc.)

Testing

  • Manually pruned RC3 packages from gh-pages and verified RC5 APT install in a debian:bookworm container
  • Both plik-client and plik-server install and report correct version 1.4-RC5

- Before copying new .deb files to the APT pool, remove old versions of
  the same package/architecture. This prevents the pool from growing by
  ~180 MB per release indefinitely.
- Change 'git add apt/' to 'git add -A' so the orphan force-push to
  gh-pages preserves the VitePress docs site instead of nuking it.
Copy link
Copy Markdown
Member

@bodji bodji left a comment

Choose a reason for hiding this comment

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

LGTM

@camathieu camathieu merged commit 474b296 into master Feb 28, 2026
7 checks passed
@camathieu camathieu deleted the fix/apt-release-pool-pruning branch March 7, 2026 11:12
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.

2 participants