fix(ci): prune snap assets from dev release#2302
Merged
Merged
Conversation
Signed-off-by: Piotr Mlocek <pmlocek@nvidia.com>
6e5c785 to
0c75dc8
Compare
drew
approved these changes
Jul 15, 2026
6 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Prune versioned Snap packages from the rolling
devrelease before publishing the current builds. This prevents Snap assets from accumulating while preserving the existing behavior for unmanaged assets.Right now, the dev release has 370 artifacts on it: https://github.com/NVIDIA/OpenShell/releases/tag/dev
The ones that are not cleaned up are

.snap.Changes
.snapfiles with theopenshellprefix as managed dev-release assetsTesting
mise run pre-commitpassesgit diff --checkpassesChecklist