Skip to content

Conversation

@lognaturel
Copy link
Contributor

@lognaturel lognaturel commented Oct 20, 2025

Prepares next release, following checklist

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

In the changes doc, I ordered by version number, not by date (v3.1.0 was released after 4.0.0 which is unusual for us).

What are the regression risks?

This is a somewhat risky release because of the changes in how triggers are processed and in how relative references in repeats are treated. It has been on https://getodk.org/xlsform/ for a while now and all reported issues have been addressed so that should mitigate risk somewhat.

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

Issues filed for individual features.

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 requested a review from yanokwa October 20, 2025 17:20
Copy link
Contributor

@yanokwa yanokwa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@lognaturel lognaturel merged commit 5b0ac3d into XLSForm:master Oct 20, 2025
14 checks passed
@lognaturel lognaturel deleted the prep-4.1.0 branch October 20, 2025 17:27
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