chore: bump to 0.4.0rc0 for release pipeline smoke test#12
Merged
Conversation
One-shot bump so we can tag v0.4.0-rc0 and verify the TestPyPI publish flow end-to-end (OIDC trusted publisher, build, upload, install). The rc0 slot on TestPyPI is a throwaway — it never goes to real PyPI and doesn't conflict with any future v0.5.0 release plans. After the smoke test verifies, main stays at 0.4.0rc0 until Phase 6 release prep bumps it forward to whatever the real release version is (likely 0.5.0rc1).
There was a problem hiding this comment.
Pull request overview
Bumps the OpenArmature package version to 0.4.0rc0 to enable tagging v0.4.0-rc0 from main and exercising the TestPyPI release pipeline end-to-end (build/upload/install smoke test) without impacting real PyPI.
Changes:
- Update package version to
0.4.0rc0inpyproject.tomlandsrc/openarmature/__init__.py. - Update the smoke test assertion to match the new version.
- Update
uv.lockto reflect the new editable package version.
Reviewed changes
Copilot reviewed 3 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
pyproject.toml |
Bumps project version to 0.4.0rc0. |
src/openarmature/__init__.py |
Updates runtime __version__ constant to 0.4.0rc0. |
tests/test_smoke.py |
Adjusts version assertion for the smoke test. |
uv.lock |
Aligns lockfile package entry with the bumped version. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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
One-shot version bump to
0.4.0rc0so we can tagv0.4.0-rc0from main and verify the TestPyPI publish pipeline end-to-end (OIDC trusted publisher, build, upload, fresh-venv install). Therc0slot on TestPyPI is a throwaway — it never lands on real PyPI (the-in the tag keeps it off) and doesn't conflict with any futurev0.5.0plans.Plan
v0.4.0-rc0from main, push:git tag v0.4.0-rc0 && git push origin v0.4.0-rc0.test → build → publish-testpypi.publish-pypiandgithub-releaseskip (gate is no-in tag).pip install --index-url https://test.pypi.org/simple/ \ --extra-index-url https://pypi.org/simple/ openarmature==0.4.0rc0 python -c "import openarmature; print(openarmature.__version__)"Aftermath
Main stays at
0.4.0rc0until Phase 6 release prep bumps it forward (likely to0.5.0rc1). No revert PR; transient pre-release version.Test plan
uv buildproducesopenarmature-0.4.0rc0artifacts cleanly.pip installfrom TestPyPI in fresh venv works.