Repository navigation
ci: attach only the builds and SHA256SUMS.txt to a release - #3
Merged
Merged
Conversation
The artifacts were downloaded into assets/, the repository's screenshot folder, so the v0.5.0 release also got the README images. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015QW7EoWE2iLGGzadZAsN6d
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 release job downloaded the build artifacts into
assets/, which is the repository's screenshot folder, so the re-published v0.5.0 release also got the README images (and their checksums). Artifacts now go torelease-files/, and onlyLDAPilot-*plusSHA256SUMS.txtare uploaded.🤖 Generated with Claude Code
https://claude.ai/code/session_015QW7EoWE2iLGGzadZAsN6d