chore: release 0.3.7 — README screenshots and defense_demo.py - #39
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
1 participant
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.
Docs-only release. Bumps
0.3.6 → 0.3.7so the README screenshots merged in #36 reach the PyPI project page — the published 0.3.6 sdist carries the pre-screenshot README, and PyPI bakes its description from the sdist, so the images don't show there until a new version ships.No code changes since 0.3.6. 96 tests still pass.
What this publishes
defense_demo.pyin the sdist (added to the allowlist in docs: add real terminal screenshots for the scanner and the shield #36, verified present in the 0.3.7 build; the PNGs are correctly excluded from the package).After merge
I'll publish to PyPI, tag
v0.3.7, cut the release, and smoke-test the published artifact.