Skip to content

fix: make fixture TOML validation portable - #2

Merged
ORESoftware merged 1 commit into
mainfrom
codex/den-551-portable-toml-checks
Jul 30, 2026
Merged

fix: make fixture TOML validation portable#2
ORESoftware merged 1 commit into
mainfrom
codex/den-551-portable-toml-checks

Conversation

@ORESoftware

Copy link
Copy Markdown
Contributor

Summary

Run the fixture manifest-consistency check in a pinned Python 3.12 container instead of the host interpreter.

Why

The scripts import tomllib, which is unavailable in the macOS system Python used for local canary runs. The checks already require Docker, so the pinned container makes the validation reproducible locally and in CI.

Validation

  • Full Node symlink/copy/fresh-container canary passed.
  • Full Rust symlink/copy/fresh-container canary passed.

@linear-code

Copy link
Copy Markdown

DEN-551

@ORESoftware
ORESoftware merged commit 66418d2 into mainJul 30, 2026
1 check passed
ORESoftware added a commit that referenced this pull request Jul 30, 2026
Records the branch as merged. It was squash-merged as #1, so its commits
were never ancestors of main and it lingered as unmerged.
The add/add conflict on scripts/zed-e2e.sh resolves to main content, and
not as a side-pick: diffing the two sides shows the branch version is
byte-identical to main except that it lacks the python:3.12-bookworm
containerization added afterwards in #2. main is therefore a strict
superset -- the union of both sides IS main here, and the merged tree is
unchanged, so nothing from the branch is dropped.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for freeto 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.

1 participant

@ORESoftware