Repository navigation
docs: prepare changelog for 0.1.1 release - #68
Merged
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
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.
Summary
CHANGELOG.mdwith release notes for0.1.1setuptools-scmso tag pushes derive the published versiondist/*assetsRelease behavior
After this PR merges, release is driven by a tag such as
v0.1.1. The workflow builds package metadata from the tag, verifies the built wheel version matches the tag, publishes to PyPI, extracts## [0.1.1]notes fromCHANGELOG.md, and creates a GitHub Release.Verification
conda run -n cc pytest— 320 passedconda run -n cc ruff check .— All checks passedv0.1.1build check confirmedpt_snap_cli-0.1.1-py3-none-any.whl: Version: 0.1.1