Repository navigation
fix(release): make Filamentra source ZIP independent of generated caches - #13
Merged
DiegoV71 merged 2 commits intoNov 7, 2026
Merged
Conversation
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.
Problem
The current source ZIP builder traverses every file in
filamentra/after CI tests import the package. Python__pycache__and generated.pycmay be published, making outputs depend on interpreter state instead of repository content.Change
.DS_Storefrom shipped ZIP contents; preserve other potential runtime assets.Release impact
This PR intentionally changes
scripts/build_release.py, which is a release-eligible input. Merging intomainshould trigger an automatic GitVersion-based Filamentra source release, provided checks pass. Do not create a tag manually; inspect the resulting ZIP for cache files and release metadata.