Skip to content

Allow TRO fallback for pinned certified datasets#368

Merged
MaxGhenis merged 1 commit into
mainfrom
codex/fix-us-trace-tro-release-manifest
May 18, 2026
Merged

Allow TRO fallback for pinned certified datasets#368
MaxGhenis merged 1 commit into
mainfrom
codex/fix-us-trace-tro-release-manifest

Conversation

@MaxGhenis
Copy link
Copy Markdown
Contributor

Summary

  • Allow TRACE TRO generation to proceed when the country release manifest pins the certified dataset SHA but the separate data release manifest does not list that dataset
  • Omit the stale/inapplicable data release manifest artifact in that fallback path
  • Add regression coverage for the fallback

Tests

  • uv run --locked --extra dev python -m pytest tests/test_trace_tro.py -q
  • uv run --locked --extra dev python -m pytest tests/test_bundle_refresh.py tests/test_release_manifests.py tests/test_us_long_term_datasets.py -q
  • uv run --locked ruff check src/policyengine/provenance/trace.py tests/test_trace_tro.py
  • uv run --locked ruff format --check src/policyengine/provenance/trace.py tests/test_trace_tro.py
  • git diff --check

@MaxGhenis MaxGhenis force-pushed the codex/fix-us-trace-tro-release-manifest branch from 458f771 to 2750c83 Compare May 18, 2026 03:00
@MaxGhenis MaxGhenis merged commit 9640940 into main May 18, 2026
11 checks passed
@MaxGhenis MaxGhenis deleted the codex/fix-us-trace-tro-release-manifest branch May 18, 2026 03:19
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.

1 participant