Update news for v2026.1.1#1812
Merged
Merged
Conversation
matthew-white
commented
Apr 14, 2026
| <a href="https://forum.getodk.org/t/57925" target="_blank"> | ||
| ODK Central v2026.1.0 | ||
| <span class="item-date">2026/04/14</span> | ||
| <a href="https://forum.getodk.org/t/57925/5" target="_blank"> |
Member
Author
There was a problem hiding this comment.
It'll be /5 because /2, /3, /4 correspond to pinning or unpinning the forum topic.
lognaturel
approved these changes
Apr 14, 2026
Member
lognaturel
left a comment
lognaturel
left a comment
There was a problem hiding this comment.
We've got the right date, we've got the right version, we've got the right link 🎉
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 release of v2026.1.1, updating news.html.
What has been done to verify that this works as intended?
Nothing.
Why is this the best possible solution? Were any other approaches considered?
I followed the existing pattern.
Before submitting this PR, please make sure you have:
nextbranch OR only changed documentation/infrastructure (masteris stable and used in production)