fix: bootstrap first release as 0.1.0 and fix release workflow#6
Merged
Conversation
The first release-please run cut 1.0.0 (its default initial version) and the publish step failed, so nothing reached PyPI. Reset to 0.1.0 and fix two workflow bugs: - release-please-config: add `include-component-in-tag: false` so tags are `vX.Y.Z` (was `senderkit-vX.Y.Z`, which broke the tag/version check). - release.yml: install the built wheel before importing to read the version (the check imported an uninstalled package -> ModuleNotFoundError under the src/ layout). - Reset _version.py to 0.1.0, manifest to 0.0.0, and drop the auto 1.0.0 CHANGELOG section. The Release-As footer below forces the next release to 0.1.0, overriding release-please's 1.0.0 first-release default. One-time; not sticky. Release-As: 0.1.0 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
Why
The first release-please run cut 1.0.0 (release-please's default initial version, which ignores the
feat:→minor rule for the first release) and the publish job then failed, so nothing reached PyPI. The failure exposed two real workflow bugs.I deleted the erroneous
senderkit-v1.0.0tag + GitHub Release (never published). This PR resets to 0.1.0 and fixes the bugs.Fixes
ModuleNotFoundErrorin the version check — the build job ranimport senderkitwithout installing the package; with thesrc/layout it isn't importable from the repo root. Now it installs the freshly built wheel (pip install dist/*.whl) and imports that — verifying the actual artifact about to be published.simple+package-namemade release-please tagsenderkit-v1.0.0, which also broke${TAG#v}. Added"include-component-in-tag": false→ tags arevX.Y.Z._version.py→0.1.0, manifest→0.0.0, and removed the auto-generated## 1.0.0CHANGELOG section.Bootstrap
The commit carries a
Release-As: 0.1.0footer, which forces release-please's next release PR to 0.1.0 (overriding the 1.0.0 default). It's a one-time, per-commit override — nothing sticky to clean up later.After merge
Release-Asfooter reachesmain.v0.1.0, creates the Release, and publishessenderkit 0.1.0to PyPI.Verified locally
python -m build→senderkit-0.1.0; the new check (pip install dist/*.whl→ import) reports0.1.0and matches tagv0.1.0.🤖 Generated with Claude Code