Skip to content

Upgrade pyxform to 4.3.1#1688

Merged
lognaturel merged 1 commit intogetodk:nextfrom
lognaturel:pyxform-4.3.1
Mar 15, 2026
Merged

Upgrade pyxform to 4.3.1#1688
lognaturel merged 1 commit intogetodk:nextfrom
lognaturel:pyxform-4.3.1

Conversation

@lognaturel
Copy link
Member

What has been done to verify that this works as intended?

Verified on dev server

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

Minimal fix for regression. I'm going to cherry pick this for the point release.

How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?

It's intended to fix a regression. Risk is limited to forms with Entity declarations.

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

Before submitting this PR, please make sure you have:

  • branched off and targeted the next branch OR only changed documentation/infrastructure (master is stable and used in production)
  • verified that any code or assets from external sources are properly credited in comments or that everything is internally sourced

@lognaturel lognaturel requested a review from yanokwa March 15, 2026 05:47
@lognaturel lognaturel merged commit 9ea3088 into getodk:next Mar 15, 2026
5 checks passed
@lognaturel lognaturel deleted the pyxform-4.3.1 branch March 15, 2026 05:49
lognaturel added a commit to lognaturel/central that referenced this pull request Mar 15, 2026
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