Patch release v2026.3.2

Open
#2,336 0 comments 0 reactions 0 assignees View on GitHub

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 for central, central-backend, and central-frontend, so the central release URL (https://github.com/getodk/central/releases/tag/vXXXX.X.Y) can be referenced from the central-frontend and central-backend release bodies.
  • List all the issues in central and web-forms repos 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 central repository 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 central repository, check out the master branch. Otherwise, use a hotfix branch off master (never next, 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 central repository, then there should be a PR for the patch as a whole, targeting master. Merge it to master.
    • 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 docs repository. Using a new branch in your fork of the docs repository, copy central-backend/docs/api.yaml to docs/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 release label.
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 the master branch.
    • Link to the forum post. Limit the number of news items to 2. Target the master branch.
  • 🔎 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 next branch that isn't on the master branch, then merge the master branch into the next branch. If there has not been a commit, then reset the next branch to the tip of the master branch.
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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getodk/central

All issues in getodk/central

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.