Repository navigation
Fix CI release notes and package assets - #53
Merged
Merged
Conversation
|
✅ No security or compliance issues detected. Reviewed everything up to 1e73042. Security OverviewDetected Code Changes
|
joshrmcdaniel
changed the title
joshrmcdaniel
added a commit
that referenced
this pull request
Oct 2, 2026
* fix: include curated CI release notes * fix: exclude stale packages from release assets
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.
The tag-triggered CI job creates GitHub releases, but it currently ignores the curated
RELEASE.mdand can upload old DEB/RPM packages left in cachedtarget/directories. Check out the tagged source and passRELEASE.mdtosoftprops/action-gh-release; clear Privaxy's cached packages before packaging on native and MIPS targets, and restrict RPM uploads toprivaxy-*.rpm.The existing flow remains
develop→main, followed by pushing a version tag on the merged commit. The workflow's triggers, build dependencies, package/image publishing, and permissions are unchanged.Validation: workflow YAML parses, the checkout precedes release creation, the configured notes file exists, and
git diff --checkpasses. A temporary package-output fixture verifies both cleanup steps remove older Privaxy packages while preserving the binary and unrelated files. Thebody_pathinput is supported by the action's upstream documentation.