Exclude release script from published crate - #106
Merged
Conversation
woodruffw
force-pushed
the
exclude-script
branch
from
August 28, 2026 19:00
5300cb4 to
800de64
Compare
woodruffw
approved these changes
Aug 28, 2026
woodruffw
left a comment
woodruffw
left a comment
Member
There was a problem hiding this comment.
Thanks @musicinmybrain! No concerns from me. We'll do this with the next patch release.
woodruffw
enabled auto-merge (squash)
August 28, 2026 19:01
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
2 participants
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.
This isn’t terribly important, but the contents of
scripts/are for maintainer use and don’t benefit users of published crates on crates.io. Omitting this directory will very slightly slim down the releases.This is also useful downstream in Fedora, where we would need to exclude
scripts/release.pyfrom distribution packaging to avoid an unwanted automatically-generated dependency onuv. This is certainly something we can handle downstream-only, but it’s what prompted me to open this PR.