Skip to content

Bump bundled wirelog to v0.51.0 and release 1.0.1#166

Merged
justinjoy merged 1 commit into
mainfrom
release/1.0.1-wirelog-0.51.0
Jun 13, 2026
Merged

Bump bundled wirelog to v0.51.0 and release 1.0.1#166
justinjoy merged 1 commit into
mainfrom
release/1.0.1-wirelog-0.51.0

Conversation

@justinjoy

Copy link
Copy Markdown
Contributor

Summary

Bumps the validated and bundled wirelog ref from v0.50.0 (272edf3…) to v0.51.0 (0c6e0cdaee7db069be5d8d896bb59bdcb15673e9) and bumps PyreWire to 1.0.1.

v0.51.0 ships the wirelog#914 fix (iteration context not reset for non-recursive strata), which resolves #165: a single relation(...)-body rule (e.g. requires_review(...)) now derives its head when the program also contains the recursive edge/path rules. PyreWire does no rule evaluation of its own, so bumping the bundled engine is the fix.

This is a wirelog-only rebuild — the PyreWire public API is unchanged and MINIMUM_WIRELOG_VERSION stays 0.44.0.

Changes

  • pyproject.toml: version1.0.1; cibuildwheel WIRELOG_VERSION (×4) → v0.51.0 SHA
  • src/pyrewire/__init__.py: __version__1.0.1
  • .github/workflows/ci.yml: default WIRELOG_VERSION → v0.51.0 SHA
  • docs/support.md: bundled engine → v0.51.0 / new SHA
  • docs/versioning.md: new 1.0.1 compatibility row (1.0.0 row left frozen)
  • CHANGELOG.md: new [1.0.1] section + compare links (1.0.0/0.41.0 sections frozen)
  • Tests updated to the new current-state pin; historical 1.0.0 assertions and the v1.0.0 RC checklist left frozen as historical records

Verification

  • black --check, isort --check-only, flake8, mypy src/pyrewire: clean
  • pytest: 473 passed, 2 skipped, coverage 93.7% (≥90%). The one local failure (test_pep561_packaging::…recognized_as_typed_by_mypy) is environmental — No module named mypy in a temp system_site_packages venv whose base interpreter lacks mypy; it has no reference to the pin/version and passes in CI.
  • mkdocs build --strict: clean
  • Release-notes extraction for 1.0.1: OK
  • End-to-end Single relation-body rule does not derive when recursive path rules are present #165 repro: built wirelog at the pinned v0.51.0 SHA and ran EasySession.step()requires_review("a","r") is now derived (was missing on v0.50.0).

Closes #165

Move the validated and bundled wirelog ref from v0.50.0
(272edf3a24b25676f12c4b843d55510f5048dd2f) to v0.51.0
(0c6e0cdaee7db069be5d8d896bb59bdcb15673e9) and bump PyreWire to 1.0.1.

v0.51.0 ships the wirelog#914 fix (iteration context not reset for
non-recursive strata), which resolves #165: a single relation()-body
rule now derives its head when recursive edge/path rules are present.
PyreWire performs no rule evaluation of its own, so bumping the bundled
engine is the fix. Verified end to end: EasySession.step() now derives
requires_review against a v0.51.0 build.

This is a wirelog-only rebuild; the PyreWire public API is unchanged and
MINIMUM_WIRELOG_VERSION stays 0.44.0. The 1.0.0 compatibility row,
CHANGELOG section, and RC checklist remain frozen as historical records;
current-state pins (pyproject cibuildwheel, ci.yml default, support
docs) and their tests move to the new ref.

Closes #165
@justinjoy justinjoy force-pushed the release/1.0.1-wirelog-0.51.0 branch from 32d0f3c to df92945 Compare June 13, 2026 12:24
@justinjoy justinjoy merged commit 7b70fa6 into main Jun 13, 2026
17 checks passed
@justinjoy justinjoy deleted the release/1.0.1-wirelog-0.51.0 branch June 13, 2026 12:30
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.

Single relation-body rule does not derive when recursive path rules are present

1 participant