Skip to content

Pin spec v0.64.0 for proposal 0073 (textual-only)#173

Merged
chris-colinsky merged 2 commits into
mainfrom
feature/0073-genai-semconv-adoption
Jun 20, 2026
Merged

Pin spec v0.64.0 for proposal 0073 (textual-only)#173
chris-colinsky merged 2 commits into
mainfrom
feature/0073-genai-semconv-adoption

Conversation

@chris-colinsky

Copy link
Copy Markdown
Member

Summary

Implements proposal 0073 (spec v0.64.0), "GenAI semconv adoption reconciliation": a governance + observability §5.5 rationale change with no emitted-attribute or conformance changes. Textual-only pin bump v0.63.1 -> v0.64.0.

What changed

0073 reconciles OA's gen_ai.* adoption with upstream reality: the whole GenAI semantic-conventions surface is at Development status, and gen_ai.system was removed upstream in favor of gen_ai.provider.name. The spec adds a GenAI-scoped de-facto-interoperability carve-out (adopt the recognized core gen_ai.* names directly even at Development; mirror peripheral ones to openarmature.*) and a post-adoption retention rule (an adopted name is kept through an upstream rename / removal). OA therefore retains gen_ai.system.

For python this is purely the pin advance: no emitted-attribute change and no new or changed fixtures. The existing gen_ai.* observability fixtures stand as the retention regression coverage. conformance.toml records 0073 textual-only; the gen_ai.system -> gen_ai.provider.name migration is a deferred follow-on.

Testing

  • Manifest guard 69/69; full suite green (1345 passed, unchanged); pyright and mkdocs clean.

Notes

  • The 0.15.0 changelog date is tentative pending the release tag.

0073 (GenAI semconv adoption reconciliation) is a spec governance +
observability §5.5 rationale change with no emitted-attribute and no
conformance-expectation change: OA retains gen_ai.system despite the
upstream rename to gen_ai.provider.name, and the existing gen_ai.*
fixtures stand as the retention regression.

Textual-only pin bump v0.63.1 -> v0.64.0: __spec_version__, pyproject,
smoke, regenerated AGENTS.md, conformance.toml 0073 textual-only, and
the 0.15.0 changelog pin bullet. No code, no new fixtures.
Copilot AI review requested due to automatic review settings June 20, 2026 00:09

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Pull request overview

Bumps the pinned openarmature-spec version to v0.64.0 (proposal 0073, textual-only) and updates the repo’s declared spec-version surfaces and release notes accordingly.

Changes:

  • Updated runtime and build metadata to spec v0.64.0 (__spec_version__, pyproject.toml, smoke test).
  • Updated bundled agent documentation to reflect the new spec version.
  • Added proposal 0073 (textual-only) to conformance.toml and updated the v0.15.0 changelog narrative.

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 1 comment.

Show a summary per file
File Description
tests/test_smoke.py Updates the pinned __spec_version__ assertion to v0.64.0.
src/openarmature/AGENTS.md Updates the bundled agent-guide spec-version references to v0.64.0.
src/openarmature/init.py Bumps __spec_version__ to v0.64.0.
pyproject.toml Bumps [tool.openarmature].spec_version to v0.64.0.
conformance.toml Adds proposal 0073 as textual-only (but needs manifest spec_pin update).
CHANGELOG.md Updates the v0.15.0 entry to include the v0.64.0 / proposal 0073 pin.

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

Comment thread conformance.toml
PR #173 review: conformance.toml [manifest].spec_pin was stale at
v0.60.0 -- a fourth pin-sync point the smoke test did not cover, so it
drifted across the v0.15.0 pin bumps. Update it to v0.64.0 and add a
smoke-test assertion that spec_pin tracks __spec_version__ so it cannot
drift again.
@chris-colinsky chris-colinsky merged commit a881c5f into main Jun 20, 2026
6 checks passed
@chris-colinsky chris-colinsky deleted the feature/0073-genai-semconv-adoption branch June 20, 2026 00:19
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