Skip to content

Refresh bundled schemas - #2

Merged
colinjlacy merged 2 commits into
runtimeconditions:mainfrom
itvi-1234:refresh-bundled-schemas
Nov 12, 2026
Merged

colinjlacy merged 2 commits into
runtimeconditions:mainfrom
itvi-1234:refresh-bundled-schemas

Conversation

@itvi-1234

Copy link
Copy Markdown
Member

Why

The Python profiler could not profile bindings built from the current extensions repo, for example env-configuration. Two things had drifted:

  1. schemas.json held older copies of the four binding schemas (binding manifest, binding model, binding release, extension semantic).
  2. Extension dependencies, dependency edges and package dependencies are now plain full-id strings instead of {id, version} objects. The profiler read a string as (id, ""), so it never matched the closure, which is keyed by (id, version). That gave "model dependency edges do not match extension closure".

What changed

  • schemas.json: refreshed from the extensions repo (upstream main).
  • project/verify.py: edges, dependencies and package dependencies look their version up from the extension closure.
  • profile/semantic.py: the profile closure does the same.
  • extension/identity.py: new resolve_reference. A bare id resolves to the one known (id, version) with that id. If an id has several versions it is left unresolved.
  • extension/definition.py, util.py, extension/artifact_validator.py: the closure, cycle and "dependency cannot be resolved" checks use it, so extension definition files with string dependencies work as well.
  • tests: installed-binding fixtures use the new shapes (the emitter value also needs a sha256 now), plus tests for string dependencies and for ambiguous ids.

…ncies

schemas.json held older copies of the four binding schemas, so bindings built
from the current extensions repo, such as env-configuration, failed
validation. It now carries the current schemas.

Dependencies, dependency edges and package dependencies now name an extension
by its full id string instead of an {id, version} object. The binding verifier
and the profile closure look the version up from the extension closure, so
the string form keys the same way as the closure entries. The installed-binding
test fixtures use the new shapes.
…h too

Extension definitions list dependencies by full id string, which carries no
version. The closure, cycle and unresolved-dependency checks keyed definitions
by (id, version), so a string dependency never matched. A bare id now resolves
to the one known (id, version) with that id. Ambiguous ids stay unresolved.
The semantic test helper reads string dependencies the same way.
@colinjlacy
colinjlacy merged commit c22a898 into runtimeconditions:main Nov 12, 2026
4 checks passed
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