Repository navigation
Release span-panel-api 3.8.0b1 and span-panel-api-schema-1 1.4.0b1 - #211
Merged
Merged
Conversation
AGENTS.md, for any maintainer or coding agent: the rule that an unpublished value is None, never a constant; the tables a new snapshot field or adapter read must reach (field metadata and discovery, conformance, the public API and the adapter fidelity harness); how the harness rules, pinned drops and capture cells work; the expected-failure registry; and the byte-pinned captures and the reference tree. It points to DEVELOPMENT.md and RELEASE.md for procedures. CLAUDE.md imports it.
span-panel-api 3.8.0b1 and span-panel-api-schema-1 1.4.0b1; schema-0 stays at 1.3.0b1, as on main. schema-1 floors on span-panel-api 3.8.0b1, whose snapshot fields it fills, and the core schema-1 extra floors on 1.4.0b1. The changelogs carry the one line for this release under [Unreleased], and schema-1's records the moved reference tree.
The docstring still described the range as widened to occupied spaces outside the model's range. It is the table's range, and the adapter warns once for a panel whose circuits fall outside it.
The schema-1 extra floors on 1.4.0, not 1.3.0; the schema-0 extra stays on 1.3.0.
SHA256SUMS pins the captures and the LICENSE; README.md and SHA256SUMS themselves are records the check does not pin.
The stale-row check judged only rows whose file the run had collected, so a renamed or deleted test file left its rows marking nothing. It now reads each named file from disk and requires the test to be defined there, at module level or on a Test class, before any test runs; a partial run judges every row exactly as a full run does, with no false alarm while the rows hold. Tests pin a missing file, a missing test, a non-test and a method off a Test class as stale, a partial run stopping on one, and the registry itself as clean. AGENTS.md and the registry docstring describe it.
… optional Both snapshot fields become bool | None for consumers: is_240v is None where the pole count is unpublished, and lugs_at_service_entrance while the upstream lugs declare their feed but leave it unpublished.
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.
Release span-panel-api 3.8.0b1 and span-panel-api-schema-1 1.4.0b1 from
prerelease/3.8.3.8.0b1; span-panel-api-schema-11.4.0b1, floorspan-panel-api>=3.8.0b1,<4.0; span-panel-api-schema-0 stays1.3.0b1, as onmain. The core'sschema-1extra floors on1.4.0b1.uv.lockupdated.[Unreleased], the core and schema-1 changelogs carry the one line for this release, and schema-1's records the moved reference tree (a changed capture is a release of the adapter that ships it). The core changelog also marksSpanCircuitSnapshot.is_240vandSpanPanelSnapshot.lugs_at_service_entrancebecomingbool | Noneas breaking for consumers.first_position's docstring and the extras' changelog floors are corrected.AGENTS.md: what to keep current when a snapshot field or adapter read changes (field metadata and discovery, conformance, the public API, the adapter fidelity harness), how the harness rules, pinned drops and capture cells work, the expected-failure registry, and the byte-pinned captures and reference tree, pointing to DEVELOPMENT.md and RELEASE.md.CLAUDE.mdimports it.Checks:
pytest tests -q: 1856 passed, 7 skipped, 9 xfailed.pre-commit run --all-files: all hooks pass.uv buildof all three distributions;twine check: 6 of 6 passed.Requires-Dist: schema-1span-panel-api<4.0,>=3.8.0b1, schema-0span-panel-api<4.0,>=3.7.0b1, core extrasschema-0>=1.3.0b1,schema-1>=1.4.0b1.span-panel-api==3.8.0b1,span-panel-api-schema-0==1.3.0b1andspan-panel-api-schema-1==1.4.0b1from the built wheels into a clean environment resolves.