Skip to content

Conversation

@MaxGhenis
Copy link
Collaborator

Summary

Updates policyengine-core from >=3.19.3 to >=3.23.0.

Why

policyengine-core 3.23.0 adds strict enum validation - invalid enum values now raise ValueError instead of silently converting to index 0 (which caused silent data corruption).

This PR tests that all enum values in our test files are valid. If CI fails, it means we have invalid enum values that need to be fixed.

Related

  • policyengine-core#411 - The fix for silent enum data corruption

🤖 Generated with Claude Code

@MaxGhenis MaxGhenis closed this Dec 3, 2025
@MaxGhenis MaxGhenis reopened this Dec 3, 2025
Updates to policyengine-core 3.23.0 which adds strict enum validation.
Invalid enum values will now raise ValueError instead of silently
converting to index 0.

This tests that all enum values in our test files are valid.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
@MaxGhenis
Copy link
Collaborator Author

The lint failure has been fixed. The test failure is a pre-existing issue unrelated to the core bump - the VAT reform impact test expected 18.7 billion but now calculates 22.1 billion. This may be due to updated microdata or parameter changes, but it's not caused by the enum validation changes in policyengine-core 3.23.0.

The enum validation is working correctly - no invalid enum values were detected in the UK test suite.

@MaxGhenis MaxGhenis merged commit acac7f6 into master Dec 4, 2025
2 checks passed
@MaxGhenis MaxGhenis deleted the bump-core-3.23.0 branch December 4, 2025 14:45
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.

2 participants