Patch release v2026.3.2
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 1/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github, javascript
- Domain
- release
Research direction
This issue is the release checklist for ODK Central v2026.3.2; start by reading the checked and unchecked steps in the issue. The checklist shows the central release and news update are complete, while API docs, future release PRs, and syncing the next branch remain. The release work is done when those remaining steps are completed and reviewed.
Written by the indexing model from the issue text.
Description
Complete the steps below to release a patch version of ODK Central. For a major release, use the Release issue template instead.
Legend
- 🔎 Requires the second person (reviewer)
Releasing requires two people: one person to push PRs and complete other tasks and another person to review the PRs.
Steps
- Decide the release version (
vXXXX.X.Y). The same version is used forcentral,central-backend, andcentral-frontend, so thecentralrelease URL (https://github.com/getodk/central/releases/tag/vXXXX.X.Y) can be referenced from thecentral-frontendandcentral-backendrelease bodies. - List all the issues in
centralandweb-formsrepos to be included in this release, and tick them off when they have been cherry-picked into the release branch- Upgrade nginx
- Upgrade postgres
Get the repository
- Get the latest version of the
centralrepository locally.- If you have not cloned the repository: clone it.
- If you had already cloned the repository:
git pull
- Check out the correct branch. If the patch involves a single change/PR to the
centralrepository, check out themasterbranch. Otherwise, use a hotfix branch offmaster(nevernext, which may contain changes not intended for the patch); check out that branch.
Merge
- If the patch involves more than a single change/PR to the
centralrepository, then there should be a PR for the patch as a whole, targetingmaster. Merge it tomaster.- Select "Create a merge commit" when you merge.
Release central
-
Create a GitHub release for
central. This will also create a Git tag.- Set as the latest release. Don't set as a pre-release.
- Publish once you're ready to create the release and tag.
-
Add release notes to the release.
📋 Release notes template — expand, fill in links, and paste into the GitHub release
## Release Notes ### 🛠 Technical Changelogs For a detailed list of technical updates, fixes, and improvements, please review the specific changelogs below: <!-- CHANGELOG section anchors drop dots from the version number: 0.25.0 → #0250 --> * User interface * The user interface is made up of multiple component parts; each has its own changelog. * [apps/central](https://github.com/getodk/central-frontend/tree/master/apps/central/CHANGELOG.md#<version-without-dots>) * [apps/forms](https://github.com/getodk/central-frontend/tree/master/apps/forms/CHANGELOG.md#<version-without-dots>) * [packages/web-forms](https://github.com/getodk/central-frontend/blob/master/packages/web-forms/CHANGELOG.md#<version-without-dots>) * [packages/xforms-engine](https://github.com/getodk/central-frontend/blob/master/packages/xforms-engine/CHANGELOG.md#<version-without-dots>) * [packages/xpath](https://github.com/getodk/central-frontend/tree/master/packages/xpath/CHANGELOG.md#<version-without-dots>) * [API](https://docs.getodk.org/central-api-changelog/) * [Operations infrastructure](https://github.com/getodk/central/blob/master/CHANGELOG.md#<version-without-dots>)
Update API docs
- Update the API docs in the
docsrepository. Using a new branch in your fork of thedocsrepository, copycentral-backend/docs/api.yamltodocs/docs/_static/api-spec/central.yaml. Create a new PR for the branch. - 🔎 Review the PR.
- Merge any other relevant docs PRs.
- Check future release PRs. When you merge one of these, remove the
future releaselabel.
Announce the release
- Reply to the topic for the latest release.
Update news
- Create a new PR to update
central/docs/news.html, branching off themasterbranch.- Link to the forum post. Limit the number of news items to 2. Target the
masterbranch.
- Link to the forum post. Limit the number of news items to 2. Target the
- 🔎 Review the PR. Feel free to "Squash and merge" when you merge.
Update the next branch
Do this once the news PR has been merged.
- If there has been a commit to the
nextbranch that isn't on themasterbranch, then merge themasterbranch into thenextbranch. If there has not been a commit, then reset thenextbranch to the tip of themasterbranch.
- Dominant language
- JavaScript
- Stars
- 233
- Forks
- 241
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 13
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from getodk/central
-
sessions are not reapedPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Maintainers usually reply within 1 day
-
The `New Submission` button on the Submissions tab is now harder to access on mobilePossibly taken @sadiqkhoja claimed this 1 day ago. Openfrontend
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
getodk/central#2334 · 1 assignee ·
Maintainers usually reply within 1 day
-
Copying text from table clicks on the rowPossibly taken @sadiqkhoja claimed this 1 day ago. Openfrontend needs testing
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
getodk/central#2331 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
Hide closed formsPossibly taken @nicoleorlowski claimed this 8 days ago. Openfrontend needs testing
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
getodk/central#2323 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
Similar issues
-
Escaped `*` followed by `*` (`\**`) never matchesPossibly taken @bardrop claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 71/100
editorconfig/editorconfig-core-js#172 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
fb55/htmlparser2#2579 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Provider editor: multiple top plugin options overlap Models because .top caps the container at 46pxOpen
Difficulty 2/5 1-3 hours Newbie friendliness 74/100