Problem
The current HF `main`-branch `release_manifest.json` pins `compatible_model_packages: [{name: policyengine-us, specifier: '==1.637.0'}]`. `policyengine-us==1.637.0` through `1.645.0` all fail parameter validation at class-creation against `policyengine-core>=3.25.0` (`gov.contrib.additional_tax_bracket.bracket.rates` parameter has out-of-range children). `1.650.0` and newer import cleanly.
Net: downstream consumers (`policyengine.py`, `policybench`) that want to run the 1.83.x dataset through the certified-bundle path have no working model version to pin.
Fix
Once #798 merges (which exposes `additional_compatible_specifiers` on `build_release_manifest`), a release run can pass e.g. `">=1.637.0,<2.0.0"` as an additional specifier and republish `release_manifest.json` on HF. The companion consumer PR (PolicyEngine/policyengine.py#284) teaches the certifier to accept full PEP 440 specifiers, not only `==`.
Also
The 1.83.x version on HF `main` has no corresponding revision/tag — only up to `1.78.2` exists as an HF ref. That means `hf://policyengine/policyengine-us-data/enhanced_cps_2024.h5@1.83.3` 404s. Please tag the published release so consumers can reference it immutably.
🤖 Generated with Claude Code
Problem
The current HF `main`-branch `release_manifest.json` pins `compatible_model_packages: [{name: policyengine-us, specifier: '==1.637.0'}]`. `policyengine-us==1.637.0` through `1.645.0` all fail parameter validation at class-creation against `policyengine-core>=3.25.0` (`gov.contrib.additional_tax_bracket.bracket.rates` parameter has out-of-range children). `1.650.0` and newer import cleanly.
Net: downstream consumers (`policyengine.py`, `policybench`) that want to run the 1.83.x dataset through the certified-bundle path have no working model version to pin.
Fix
Once #798 merges (which exposes `additional_compatible_specifiers` on `build_release_manifest`), a release run can pass e.g. `">=1.637.0,<2.0.0"` as an additional specifier and republish `release_manifest.json` on HF. The companion consumer PR (PolicyEngine/policyengine.py#284) teaches the certifier to accept full PEP 440 specifiers, not only `==`.
Also
The 1.83.x version on HF `main` has no corresponding revision/tag — only up to `1.78.2` exists as an HF ref. That means `hf://policyengine/policyengine-us-data/enhanced_cps_2024.h5@1.83.3` 404s. Please tag the published release so consumers can reference it immutably.
🤖 Generated with Claude Code