fix(#2086): downgrade Enketo to 7.6.1 - #2094
Merged
Merged
Conversation
Contributor
Author
|
@matthew-white @sadiqkhoja This seems to be the only place to update the Enketo version 🤔 Could you also please update the test server so the QA Team can start testing tomorrow? 🙏🏼 |
matthew-white
approved these changes
Jul 30, 2026
Member
|
I'm going to go ahead and merge so we can get this on staging/test. |
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
2 participants
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.
Warning
Branch off and target
next, notmaster. Themasteris stable and used in production (exception: documentation/infrastructure-only changes).Closes #2086
What has been done to verify that this works as intended?
CI passess and I checked how it was done in #1965
Why is this the best possible solution? Were any other approaches considered?
How does this change impact users? Describe intentional behavior changes from code updates. What are the regression risks?
Does this change require updates to documentation? If so, please file an issue here and include the link below.