Skip to content

Upgrade jsonschema conformance dependency #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
evanfollis merged 1 commit into from
Jul 26, 2026
Merged

Upgrade jsonschema conformance dependency #3

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 10 additions & 4 deletions CURRENT_STATE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,10 +7,9 @@ updated: 2026-07-26

# CURRENT_STATE — context-repository

**Last updated**: 2026-07-26 — attended session. Executed the ADR-0050
contract-repository migration (repo.toml, Makefile + `make check`, AGENTS.md,
docs/architecture.md, CI, legacy decoys quarantined). Published contract left in
place. `make check` green; conformance 19/19.
**Last updated**: 2026-07-26 — attended dependency closure. The deterministic
checker is pinned to current jsonschema 4.26.0; the published contract and
fixtures are unchanged. `make check` remains green with conformance 19/19.

---

Expand Down Expand Up @@ -48,6 +47,13 @@ deliberate exception, not an oversight (ADR-0050 review finding B3).

## Active / recent work

- **Dependency closure — LANDED 2026-07-26.** Updated the sole checker
dependency from jsonschema 4.10.3 to 4.26.0 after the full 19-fixture
conformance suite passed. No schema, canon, fixture, or published path
changed. The runner still uses the library's legacy `RefResolver`
compatibility surface; removal of that surface requires a separately
reviewed implementation migration, not a blind dependency merge.

- **ADR-0050 contract migration — LANDED 2026-07-26 (this session).** Added
`repo.toml` (shape=contract, lifecycle=active, agentic_risk=none), `Makefile`
with a non-masking `make check`, `AGENTS.md` (canonical instructions) +
Expand Down
9 changes: 5 additions & 4 deletions requirements.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,8 @@
# The sole dependency: the JSON-Schema validator used by the canon conformance
# checker (spec/discovery-framework/conformance/run.py). Pinned exactly for a
# reproducible `make check` across environments (standard §11). This version uses
# the stable RefResolver API and is verified against the 19 conformance fixtures.
# reproducible `make check` across environments (standard §11). The conformance
# checker still uses jsonschema's legacy RefResolver compatibility surface; all
# 19 fixtures verify that surface before an upgrade is accepted.
# Dependabot (.github/dependabot.yml) proposes bumps; re-run `make check` before
# accepting one, since a jsonschema major could drop RefResolver.
jsonschema==4.10.3
# accepting one, since a future jsonschema release may remove RefResolver.
jsonschema==4.26.0