v26.3 Release Plan

[yoshiokatsuneo]

How about the idea of just releasing new version like v26.3 as it passed more than half a year from the previous release (v 25.8) ?

[eradman]

I think a v26.3 release is a fine idea!
So far the update to Python 3.13 has been trouble-free, but if we run into any problems we can plan on releasing v26.4 instead

[yoshiokatsuneo]

We are also using Redash with Python 3.13 in our organization without problem so far.

[yoshiokatsuneo]

So, let's start v26.3 releasing process !

Here is the ToDo list.

• Update Release Note
• Create a release branch
• Create new GitHub Release
• Push image to Docker Hub
• Update Redash website ( PR for v25.1 )
• Announcement in discussions

References:

v25.8 Release Plan
v25.1 Release Plan
New-version-release-checklist
v6 Release Plan
Release Notes
Release Candidates and Release Versioning

[yoshiokatsuneo]

I updated the Release Note.
I used following command to generate the list of merged PRs, and tweaked .

 gh pr list   --repo getredash/redash   --state merged   --search "merged:>=2025-08-01"   --json number,title,url   --limit 200   --jq '.[] | "* \(.title) ([#\(.number)](\(.url)))"'

[yoshiokatsuneo]

Now, 26.03.0-dev branch was created, and I think we can use the branch for the new release.

[yoshiokatsuneo]

I think following is the command to create the new branch for releasing, based on the comment for v25.1 .

git checkout 26.03.0-dev
git checkout -b v26.3
vim package.json redash/__init__.py pyproject.toml  # set version to 26.3.0
git commit -a -m "26.3.0 release"
git push --set-upstream origin v26.3
gh release create v26.3.0 --target v26.3 --title v26.3.0 --notes "v26.3.0 release"