chore(release): v0.14.0#167
Merged
Merged
Conversation
Real release of v0.14.0 (retry & reliability; pinned spec v0.53.0 -> v0.60.0). Bump the package version from 0.14.0rc1 to 0.14.0 across pyproject, __version__, test_smoke, and the lockfile; regenerate the bundled AGENTS.md version stamp. The CHANGELOG [0.14.0] section is already dated 2026-06-17 (no drift). Tagging v0.14.0 publishes to PyPI and creates the GitHub Release. rc1 verified on TestPyPI (install, version, [otel] import, hello-world against a live LLM).
There was a problem hiding this comment.
Pull request overview
Release bump from 0.14.0rc1 to final 0.14.0, keeping the implementation’s runtime version, packaging metadata, lockfile, smoke tests, and bundled agent docs in sync for the v0.14.0 publish/tag.
Changes:
- Updated package version to
0.14.0inpyproject.tomlandsrc/openarmature/__init__.py. - Updated smoke test assertion to the new version.
- Updated generated/bundled docs stamp and
uv.lockeditable package version entry.
Reviewed changes
Copilot reviewed 4 out of 5 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| uv.lock | Updates the editable openarmature package version to 0.14.0. |
| tests/test_smoke.py | Updates the asserted runtime package version to 0.14.0. |
| src/openarmature/AGENTS.md | Updates the bundled agent guide version stamp to 0.14.0. |
| src/openarmature/init.py | Updates __version__ to 0.14.0. |
| pyproject.toml | Updates [project].version to 0.14.0 (spec pin remains 0.60.0). |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
The fan-out-with-retry degrade mode supplied its extra_outputs value
under the parent field name (`topics`) in degraded_update, but
proposal 0066 reads degraded_update in the subgraph's field-name space.
The subgraph field is `topic` (extra_outputs={topics: topic}), so the
parent-keyed entry was ignored, leaving the slot null (0069) and
tripping BatchState.topics: list[str] validation in degrade mode.
Key the degraded value by the subgraph field `topic` (the doc
walkthrough already documents `topic: other`). Caught running
MODE=degrade against the v0.14.0rc1 artifact; the example smoke test
only exercises fail_fast, so it slipped through #161.
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
Real-release bump for v0.14.0 (retry & reliability; pinned spec v0.53.0 -> v0.60.0). Follows the verified
v0.14.0-rc1.0.14.0rc1->0.14.0(pyproject.toml,__version__,tests/test_smoke.py,uv.lock).src/openarmature/AGENTS.mdversion stamp.[0.14.0]section already dated 2026-06-17 (no drift).examples/fan-out-with-retry): the degradedegraded_updatekeyed its extra-output by the parent name (topics) instead of the subgraph field (topic), so post-0066MODE=degradehit a null slot and trippedBatchState.topics: list[str]validation. Example-only (not in the wheel); caught running the rc against the degrade path. The doc walkthrough already documentedtopic.Per RELEASING.md: merging this and tagging
v0.14.0publishes to PyPI and creates a GitHub Release.rc verification (v0.14.0-rc1 on TestPyPI): fresh-venv install resolved
0.14.0rc1;import openarmaturereports the rc version + spec0.60.0;[otel]/[langfuse]extras install and import;hello-worldran against a live LLM;mkdocs build --strictclean. The folded example fix is example-only, so the rc's wheel verification still holds (no new rc needed).Testing
uv run pytest tests/: 1320 passed, 376 skipped.MODE=degradefan-out-with-retry now completes (was the bug above).ruff/pyrightclean; pyproject version matches thev0.14.0tag.