Update news for v2026.2#2038
Merged
Merged
Conversation
Member
Author
|
I'm intentionally targeting the |
lognaturel
approved these changes
Jul 3, 2026
| ODK Central v2026.1.2 | ||
| <span class="item-date">2026/07/03</span> | ||
| <a href="https://forum.getodk.org/t/58254" target="_blank"> | ||
| ODK Central v2026.2 |
Member
There was a problem hiding this comment.
I think we usually add the last .0
Member
Author
There was a problem hiding this comment.
I was wondering about that and thought I remembered that we usually don't. I thought we only added the patch number when it's relevant / once we have a patch release. In any case, I think .0 is quite reasonable, so I'll go ahead and make that change. 👍
matthew-white
commented
Jul 3, 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
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 updates news.html for v2026.2.
What has been done to verify that this works as intended?
Nothing, I just followed the existing pattern.
CI is failing, but it's also failing on the
masterbranch.