Skip to content

V2025.2 deps#1135

Merged
lognaturel merged 2 commits intogetodk:nextfrom
lognaturel:v2025.2-deps
Jun 10, 2025
Merged

V2025.2 deps#1135
lognaturel merged 2 commits intogetodk:nextfrom
lognaturel:v2025.2-deps

Conversation

@lognaturel
Copy link
Member

@lognaturel lognaturel commented Jun 10, 2025

Closes #978

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

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

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?

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 changed the base branch from master to next June 10, 2025 00:17
@lognaturel lognaturel marked this pull request as ready for review June 10, 2025 01:28
@lognaturel lognaturel requested a review from sadiqkhoja June 10, 2025 01:28
@lognaturel lognaturel merged commit b7ac8b6 into getodk:next Jun 10, 2025
9 of 10 checks passed
@lognaturel lognaturel deleted the v2025.2-deps branch June 10, 2025 04:20
@matthew-white matthew-white linked an issue Jun 10, 2025 that may be closed by this pull request
4 tasks
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.

Update infrastructure dependencies for v2025.2

2 participants