release: prep 0.5.0rc1#28
Merged
Merged
Conversation
First real PyPI release after the 6-phase spec catch-up (v0.5.x → v0.10.0). Lands the version pin bump and the new CHANGELOG so the release pipeline (TestPyPI on rc tags, real PyPI on clean v0.5.0 tag) has a curated changelog and a matching version field to verify against. Per docs/RELEASING.md the release date in the CHANGELOG ``[0.5.0]`` heading stays as ``UNRELEASED`` until the ``release: 0.5.0`` PR drops the rc suffix and we tag.
There was a problem hiding this comment.
Pull request overview
Release-prep for 0.5.0rc1 ahead of the first (Test)PyPI publish, aligning the package version pins and adding a curated changelog for the upcoming 0.5.0 release.
Changes:
- Bumped package version to
0.5.0rc1acrosspyproject.toml,openarmature.__version__, the smoke test assertion, anduv.lock. - Added a new
CHANGELOG.mdin Keep-a-Changelog format with a0.5.0(UNRELEASED) entry capturing the spec catch-up work. - Updated README status line to reflect spec
v0.10.0.
Reviewed changes
Copilot reviewed 5 out of 6 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| uv.lock | Updates editable package version to 0.5.0rc1. |
| tests/test_smoke.py | Updates version-drift assertion to 0.5.0rc1. |
| src/openarmature/init.py | Bumps __version__ to 0.5.0rc1 (spec stays 0.10.0). |
| README.md | Updates stated implemented spec version to v0.10.0. |
| pyproject.toml | Bumps project version to 0.5.0rc1. |
| CHANGELOG.md | Adds curated changelog for the 0.5.0 release line. |
💡 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
Release-prep PR for the first real PyPI publish. Lands the version pin bump (0.4.0rc0 → 0.5.0rc1) and the new
CHANGELOG.mdso the tag-driven release pipeline has a curated changelog + a matching version field.This PR is the merge gate before tagging. Once it merges,
v0.5.0-rc1gets pushed and the release workflow fires:test → build → publish-testpypi(the-rcsuffix routes the rc track perdocs/RELEASING.md). After TestPyPI verification, a follow-up PR drops the rc suffix and we cutv0.5.0for real PyPI.What's in this PR
CHANGELOG.md(new, Keep-a-Changelog format) — single[0.5.0]entry covering the 6-phase spec catch-up: Phase 0 typed conformance harness, Phase 1 observer pair model (proposal 0005 §6), Phase 2 middleware (proposal 0004), Phase 3 fan-out runtime, Phase 4 llm-provider (proposal 0006), Phase 5 checkpointing (proposal 0008), Phase 6 observability/OTel (proposal 0007 + proposals 0011/0012/0013 from the 6.1 sub-phase). Date staysUNRELEASEDuntil the finalrelease: 0.5.0PR per the RELEASING flow.README.md— status line bumped fromImplemented against spec v0.8.2tov0.10.0.pyproject.toml/src/openarmature/__init__.py—version/__version__→0.5.0rc1.tests/test_smoke.py— version-drift assertion picks up the new pin (the engine-side gate against version-pin desync).uv.lock— regenerated by pre-commit on the pyproject stage.Test plan
uv run pytest -q, expects 401 passed / 2 skipped).v0.5.0-rc1and confirm the release workflow'stest → build → publish-testpypichain runs (publish-pypiandgithub-releaseshould skip per the tag-pattern table indocs/RELEASING.md).docs/RELEASING.md#3-verify-the-rc-install:pip install openarmature==0.5.0rc1from TestPyPI; import smoke check; package and spec versions match.Out of scope (follow-up)
release: 0.5.0PR (drops the rc suffix, fills in the CHANGELOG date) lands after RC verification.