Update news for v2026.2.1 - #2101
Merged
Merged
Conversation
matthew-white
commented
Jul 30, 2026
matthew-white
left a comment
matthew-white
left a comment
Member
Author
There was a problem hiding this comment.
Leaving a comment to facilitate async code review
| <a href="https://forum.getodk.org/t/58254" target="_blank"> | ||
| ODK Central v2026.2.0 | ||
| <span class="item-date">2026/07/30</span> | ||
| <a href="https://forum.getodk.org/t/58254/3" target="_blank"> |
Member
Author
There was a problem hiding this comment.
It will be /3, not /2, because the pinning of the forum topic qualifies as /2.
29 tasks
latin-panda
approved these changes
Jul 30, 2026
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.
This PR prepares the patch release v2026.2.1 by updating news.html.
This PR intentionally targets the
masterbranch, notnext. That's because (1) it's not a code change that affects deployments (it's arguably closer to documentation), and (2) we will mergenextintomasterand tag the release before then merging this PR intomaster(i.e., we release first, then announce in news).What has been done to verify that this works as intended?
I followed the usual patterns, but I didn't do anything special to verify.