Repository navigation
chore: adopt scion-sdk 0.10.1 and finish the ecosystem rename - #38
Merged
Merged
Conversation
Moves this connector onto scion-sdk 0.10.1 (its scion-sdk pin (scion-sdk>=0.10.1,<1.0.0) to >=0.10.1,<0.11), which removed the pre-layer module paths and collapsed the HTTP client factories into build_http_client(options, async_=...). A fresh install of the previous release resolved the newest SDK and failed to import, so the imports are updated to the paths that exist in 0.10.1, the lock is regenerated, and a test now asserts that every scion_sdk import (module and name) resolves on the installed release. The same change finishes the rename left in this repository: agent-utilities is now meristem, epistemic-graph is medulla, agent-connector-sdk is scion-sdk and graph-os is arbora, in code, docs, config, tests and file names. Hard cutover, no aliases. CHANGELOG history is left as written and ontology namespace IRIs are untouched. Spec: none (adopt scion-sdk 0.10 import paths) Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…up to core (scion-sdk 0.11) The connector's ontology now lives under the connector module of the one ontology base and every class declares a core parent through rdfs:subClassOf, so the pack loads in the engine instead of being rejected as an orphan or as a core conflict. The SDK floor moves to 0.11 and the lock is regenerated. Where the shared connector standard reported more, the same change fixes it: committed files the standard provides centrally are removed, and a missing tool-use contract, link, location, role or agent prompt is added. Impact: ontology IRIs of this connector change to the new base; consumers read them from the served ontology resource. Verification: the connector-standard gate from pipelines main passes on this tree, and the repository test suite was run on a build worker. Spec: none (ontology namespace move and class roll-up to core; no new requirement) Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
# Conflicts: # microsoft_agent/ontology/microsoft.ttl # pyproject.toml # uv.lock
…up to core (scion-sdk 0.11) The connector's ontology now lives under the connector module of the one ontology base and every class declares a core parent through rdfs:subClassOf, so the pack loads in the engine instead of being rejected as an orphan or as a core conflict. The SDK floor moves to 0.11 and the lock is regenerated. Where the shared connector standard reported more, the same change fixes it: committed files the standard provides centrally are removed, and a missing tool-use contract, link, location, role or agent prompt is added. Impact: ontology IRIs of this connector change to the new base; consumers read them from the served ontology resource. Verification: the connector-standard gate from pipelines main passes on this tree, and the repository test suite was run on a build worker. Spec: none (ontology namespace move and class roll-up to core; no new requirement) Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Member
Author
Pre-merge test run: PASSEDWhat this is: the full test and lint suite of this repository, run before merge on the tested tree below, because the hosted checks are not the gate for this change. Impact: the change is cleared to merge. Tested tree: the pull request head
Total time 1m42s. Verification: each check above was run on the tested tree and the result is the exit status of the repository's own commands. |
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.
What
Moves the connector to scion-sdk 0.10.1 (its scion-sdk pin (scion-sdk>=0.10.1,<1.0.0) to
>=0.10.1,<0.11) and finishes the rename of the old ecosystem names (agent-utilities to meristem, epistemic-graph to medulla, agent-connector-sdk to scion-sdk, graph-os to arbora).Why
The previous floor was uncapped or on an older line; a fresh install resolves scion-sdk 0.10.1, which removed the pre-layer module paths and the separate HTTP client factories, so the published release fails to import. Doing the rename in the same change means the connector is gated once.
Impact
Imports now use paths that exist in 0.10.1 (
build_http_client(options, async_=...)and the relocated modules). No aliases or fallbacks remain. Ontology namespace IRIs and CHANGELOG history are untouched.Verification
tests/test_scion_sdk_0_10_imports.pychecks that every scion_sdk module and imported name resolves on the installed release.Row: none (adopt scion-sdk 0.10 import paths).
🤖 Generated with Claude Code