Skip to content

Bump spec pin to v0.17.1 for proposal 0019#65

Merged
chris-colinsky merged 1 commit into
mainfrom
feature/0019-multi-provider-framing
May 24, 2026
Merged

Bump spec pin to v0.17.1 for proposal 0019#65
chris-colinsky merged 1 commit into
mainfrom
feature/0019-multi-provider-framing

Conversation

@chris-colinsky
Copy link
Copy Markdown
Member

Summary

  • Bumps the spec submodule pin from v0.17.0 to v0.17.1
  • Refreshes §8.X references in code and comments per proposal 0019's renumbering of llm-provider §8 as a catalog of wire-format mappings
  • Adds [Unreleased] section to CHANGELOG with the pin-bump entry

Proposal 0019 is purely textual on the spec side, so this PR is correspondingly small. No new fixtures, no behavioral change. All existing conformance fixtures continue to pass under the renumbered §8.X structure.

This is PR 1 of the next-release bundle (0019, agent-docs, 0010, 0009). Each subsequent PR bumps the pin further alongside its impl.

Test plan

  • uv run pytest tests/test_smoke.py (version sync, 3 passed)
  • uv run pytest tests/conformance/ (392 passed, 10 expected skips)
  • uv run ruff check . (clean)
  • uv run pyright src/ tests/ (0 errors)

Proposal 0019 reframes llm-provider §8 as a catalog of wire-format
mappings, with the existing OpenAI-compatible body nested under
§8.1. Purely textual on the spec side, no behavioral change, no
new fixtures.

Refresh code and doc references to §8.X to match the new structure:
§8.1 → §8.1.1, §8.2 → §8.1.2, §8.3 → §8.1.3, §8.5.1 → §8.1.5.1,
§8.1.1 → §8.1.1.1.
Copilot AI review requested due to automatic review settings May 24, 2026 20:29
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the repository’s pinned OpenArmature spec version from v0.17.0 → v0.17.1 and refreshes in-code/spec references to align with proposal 0019’s llm-provider §8 renumbering (OpenAI-compatible mapping moved under §8.1), with no intended behavior change.

Changes:

  • Bump __spec_version__ and [tool.openarmature].spec_version to 0.17.1 and update the version sync smoke test.
  • Update spec section references in provider code and tests to match the new §8.1.* structure.
  • Add an [Unreleased] CHANGELOG entry documenting the pin bump and renumbering context.

Reviewed changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated no comments.

Show a summary per file
File Description
tests/unit/test_llm_provider.py Updates spec section reference for classify_http_error mapping table.
tests/test_smoke.py Updates spec version assertion to 0.17.1.
tests/conformance/test_llm_provider.py Updates docstring spec reference to §8.1.
tests/conformance/harness/directives.py Updates docstring spec reference to §8.1.
src/openarmature/llm/providers/openai.py Refreshes spec section references throughout provider documentation/comments.
src/openarmature/init.py Bumps __spec_version__ to 0.17.1.
pyproject.toml Bumps [tool.openarmature].spec_version to 0.17.1.
CHANGELOG.md Adds [Unreleased] entry documenting the spec pin bump and renumbered references.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@chris-colinsky chris-colinsky merged commit b30f8da into main May 24, 2026
7 checks passed
@chris-colinsky chris-colinsky deleted the feature/0019-multi-provider-framing branch May 24, 2026 20:34
chris-colinsky added a commit that referenced this pull request May 24, 2026
Cloudflare Pages' deployment API rejected the PR #65 docs deploy
with "Invalid commit message, it must be a valid UTF-8 string."
The commit message contained section sign and arrow glyphs which
the API does not accept despite being valid UTF-8.

Pass an explicit ASCII commit message based on the GitHub SHA so
the deploy step is no longer coupled to the upstream git commit
message's character set.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants