Repository navigation
Conversation
This was referenced Oct 6, 2026
anth-volk
force-pushed
the
fix/3864-acs-local-regional-defaults
branch
from
October 7, 2026 14:03
9a7ab5e to
04e3d48
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #3868 +/- ##
=======================================
Coverage 45.22% 45.22%
=======================================
Files 183 183
Lines 11073 11073
Branches 1905 1905
=======================================
Hits 5008 5008
Misses 5644 5644
Partials 421 421 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This branch had an error being deployed
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.
Fixes #3864
Summary
policyengine[models]==6.2.5in the API runtime and generic container image, including the temporary ACS WIC compatibility fix. The lockfile refresh is pending publication.populace_us_2024as the national default.populace_us_2024_acs_localis a certified dataset and that standardregion_datasetsentries select its artifact path for state and congressional-district simulations.dataset_overlays.Dependency order
PolicyEngine/policyengine.py#552 published the original ACS-local selection in 6.2.2. This PR now targets 6.2.5, expected to include the temporary WIC compatibility fix in PolicyEngine/policyengine.py#566.
As of this update, 6.2.5 is not published on PyPI. The runtime and Docker pins now request it, but the checked-in
uv.lockstill resolves 6.2.2. Frozen installs still use that old version; a fresh generic Docker build requests the unpublished version and cannot complete. This intermediate state must not be merged or deployed.uv lock --upgrade-package policyengine, verifyuv lock --check, install from the frozen lockfile, and rerun the relevant checks. Align and relock Use ACS-local data for US regional simulations policyengine-sim-api#726 as well.If another release changes the version assigned to #566, align both PRs to the actual publication before relocking.
Provisioning
This change adds no environment variables, secrets, service accounts, data stores, or deployment targets.
Validation
Prior local validation against published 6.2.2, before this pending 6.2.5 pin update:
tests/unit/test_constants.py: 33 passed.RUN_V2_CATALOG_COMPATIBILITY=1 uv run --frozen pytest tests/integration/test_v2_catalog_installed.py -q: 1 passed. This fixes the newly observed CI failure caused by obsolete dataset-count and regional-selection expectations.uv lock --check: passed.git diff --check: passed.The full API suite, database-backed integration suite, Docker builds, and live deployment checks were not run locally for this update. Pushing the branch triggers fresh PR checks; the simulation deployment prerequisite remains in place.
Pending 6.2.5 pin validation
uv lock --checkfails becausepolicyengine[models]==6.2.5is not yet available; PyPI's complete release listing and exact-version endpoint both confirm this.uv.lockremains unchanged; no package URLs, hashes, or release metadata were fabricated.