Set the version to 0.17.0 for the release tag - #311
Merged
Merged
Conversation
Second of the two bumps RELEASING.md calls for. The rc tag needed 0.17.0rc1 in pyproject so the workflow's Version comparison matched; the real-release tag needs 0.17.0, and the two normalized forms are not equal, which is why they cannot be one commit. Verified against the workflow's own comparison: v0.17.0 matches and v0.17.0-rc1 no longer does, which is correct now that the rc is published. The CHANGELOG heading stays 2026-10-04. It is still the 4th locally, and the project dates headings by the maintainer's local tag day, which v0.16.0 and v0.14.0 both show with UTC timestamps on the following day.
There was a problem hiding this comment.
Copilot review overview
🟢 Approval recommended
All version references are consistently updated to 0.17.0 and align with the documented release process.
Review effort: Balanced
Findings: None
What changed in this PR
Updates OpenArmature from release candidate 0.17.0rc1 to final release 0.17.0.
Changes:
- Synchronizes package and lockfile versions.
- Updates runtime metadata, generated agent documentation, and smoke-test expectations.
| File | Description |
|---|---|
pyproject.toml |
Sets the release version. |
uv.lock |
Synchronizes locked package metadata. |
src/openarmature/__init__.py |
Updates the runtime version. |
src/openarmature/AGENTS.md |
Updates generated bundled documentation. |
tests/test_smoke.py |
Updates the expected package version. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
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.
Second of the two version bumps. This must merge before
v0.17.0is pushed, or the tag fails.v0.17.0-rc1is published to TestPyPI and verified: the artifact installs,conformance.tomland the bundledAGENTS.mdresolve from the installed package, and both examples run against it (the reask demo recovers 3 of 3 against a live endpoint,provider-extrasruns with no credentials).Why two commits
release.ymlcompares pyproject's version to the tag throughpackaging.version.Version, and the normalized forms differ:The second line is correct and expected now that the rc is out.
RELEASING.md:64-65requires these as separate commits for exactly this reason.Five files
pyproject.toml,src/openarmature/__init__.py,tests/test_smoke.py, plusuv.lockandsrc/openarmature/AGENTS.md, which both embed the version and regenerate from it. One line each.The CHANGELOG date is unchanged, deliberately
The heading stays
2026-10-04. It is still the 4th in the maintainer's local timezone, and that is the convention this project dates by:v0.16.0andv0.14.0both carry headings one day behind their UTC tag timestamps. If this PR and the tag slip past local midnight, the heading needs refreshing first.What the tag will do
testbuildtestpublish-testpypicontains(ref, '-rc')publish-pypi!contains(ref, '-')github-release!contains(ref, '-')So
v0.17.0publishes to PyPI and creates a GitHub Release with auto-generated notes. Unlike the rc, this one is not reversible.Release contents, for the record
79 commits since
v0.16.0, 139 files, +29,092 / -4,734. Spec pin0.88.0to0.118.2, agreeing across all four sync points. Manifest 93 to 125 proposals, with eight advancing fromnot-yetorpartialtoimplemented.Three ship as
partial, labelled rather than held, with spec's sign-off:0064(blocked on0020, closes at v0.19.0),0085and0124(both folded into 0.18.0).