Skip to content

Conversation

@lognaturel
Copy link
Contributor

@lognaturel lognaturel commented Jan 8, 2026

Prepares release

Why is this the best possible solution? Were any other approaches considered?

Followed https://github.com/XLSForm/pyxform?tab=readme-ov-file#releasing-pyxform
Verified by converting intersects_function.xlsx

What are the regression risks?

I think the biggest source or risk is likely the Validate update because it wasn't on the public server. I think #789 is a bit risky too.

Does this change require updates to documentation? If so, please file an issue here and include the link below.

No.

Before submitting this PR, please make sure you have:

  • included test cases for core behavior and edge cases in tests
  • run python -m unittest and verified all tests pass
  • run ruff format pyxform tests and ruff check pyxform tests to lint code
  • verified that any code or assets from external sources are properly credited in comments

@lognaturel lognaturel merged commit 91f1d94 into XLSForm:master Jan 8, 2026
14 checks passed
@lognaturel lognaturel deleted the prepare-4.2.0 branch January 8, 2026 22:41
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