Prune the sdist and prepare 0.5.0 release - #6
Merged
Merged
Conversation
setuptools-scm's file finder hands the sdist every git-tracked file, so the example notebooks and the sample rasters they read were swept in automatically: 4.9 MB of a 7.2 MB tarball, none of it read by anything in the package. The README artwork under assets/ went the same way, even though the README loads it over raw.githubusercontent.com rather than from the package. Add a MANIFEST.in pruning notebooks/, assets/ and .vscode/. The sdist drops to 3.9 MB and still builds and tests after unpacking (573 passed). Wheels were never affected -- they are built from `packages` alone -- and are byte-for-byte unchanged. Same fix as OmniWatermask 0.6.1, with one difference worth recording: that project keeps tests/ because its conda-forge recipe runs the suite against the sdist. MultiClean's recipe only import-checks, so tests/ is kept here for the weaker reason that an unpacked sdist should be verifiable. Its 4.9 MB of fixture rasters are now most of what is left. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Promote the [Unreleased] changelog section to [0.5.0] - 2026-08-14 and add the comparison link for the new version. A minor bump rather than a patch: the even-kernel fix changes output for even smooth_edge_size, and the default is 2, so anyone on defaults gets different results from the same input. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Two commits: the sdist fix, then the 0.5.0 changelog promotion. Merging this gives a
maincommit that is ready to tagv0.5.0per RELEASING.md.1. Keep notebooks and README artwork out of the sdist
setuptools-scm's file finder hands the sdist every git-tracked file, so the example notebooks and the sample rasters they read were swept into every release automatically.Before
After
3.9 MB.
notebooks/,assets/and.vscode/are pruned via a newMANIFEST.in.The wheel was never affected — it is built from
packagesalone — and is byte-for-byte unchanged at 12 KB.What is kept, and why
tests/pytest, 573 passed..github/workflows/RELEASING.md,CHANGELOG.md.gitignore,.pre-commit-config.yamlassets/is safe to drop because the README references its images by absoluteraw.githubusercontent.comURL, not by relative path, so nothing in the sdist reads them. The notebooks stay on GitHub, where the README's tutorial badge links them.Difference from OmniWatermask 0.6.1
This is the same fix that project shipped, but its
MANIFEST.inkeepstests/on the grounds that "downstream packagers (conda-forge) run the suite against the sdist." That reason does not hold here — MultiClean's feedstock recipe only doesimports:plus apip checkand a version assertion; it never invokes pytest.tests/is kept anyway, deliberately, so that an unpacked sdist stays verifiable. Its 4.9 MB of fixture rasters is now most of what remains in the tarball; theMANIFEST.incomment records that as the only thing left to reconsider if size ever becomes a concern again.2. Prepare 0.5.0
Promotes
[Unreleased]to[0.5.0] - 2026-08-14and adds the comparison link.A minor bump rather than a patch, because the even-kernel fix in #5 changes output for even
smooth_edge_sizeand the default is2— anyone running on defaults gets different results from the same input. The changelog entry says so explicitly and tells them to regenerate cached results.0.5.0 contains
smooth_edge_size.After merging
git checkout main && git pull git tag v0.5.0 git push origin v0.5.0Then approve the
pypienvironment deployment in Actions.🤖 Generated with Claude Code