Release notes
Per-version release notes for nano, with the security fixes each release includes and how Self-run deployments learn about new versions.
Each nano release has its own page here. A page says what changed and whether the release includes security fixes. Links to these pages are stable: the new-version email, the Update available banner in nano, and the deployment page in app.nano.rs all point to them.
nano Hosted is upgraded by nano. If you run nano yourself (self-hosted: Open or Self-run, on one host, several hosts or Kubernetes), you choose when to upgrade. See Upgrade a self-hosted deployment.
Versions
| Version | Released | Security fixes | Notes |
|---|---|---|---|
2.0.34 | November 2026 | Yes. | v2.0.34 |
2.0.33 | November 2026 | Yes. Superseded by 2.0.34. | v2.0.33 |
2.0.32 | November 2026 | Yes. Superseded by 2.0.34. | v2.0.32 |
2.0.31 | November 2026 | No. Superseded by 2.0.34. | v2.0.31 |
2.0.30 | November 2026 | Yes. Superseded by 2.0.34. | v2.0.30 |
2.0.29 | November 2026 | Yes. Superseded by 2.0.34. | v2.0.29 |
2.0.28 | November 2026 | No. Superseded by 2.0.34. | v2.0.28 |
2.0.27 | November 2026 | No. Superseded by 2.0.34. | v2.0.27 |
2.0.26 | November 2026 | Yes. Superseded by 2.0.34. | v2.0.26 |
2.0.25 | November 2026 | Yes. Superseded by 2.0.34. | v2.0.25 |
2.0.24 | November 2026 | Yes. Superseded by 2.0.34. | v2.0.24 |
2.0.23 | November 2026 | No. Superseded by 2.0.34. | v2.0.23 |
2.0.22 | November 2026 | No. Superseded by 2.0.34. | v2.0.22 |
2.0.20 | November 2026 | Yes. Superseded by 2.0.34. | v2.0.20 |
2.0.19 | November 2026 | No. Superseded by 2.0.34. | v2.0.19 |
2.0.18 | November 2026 | No. Superseded by 2.0.34. | v2.0.18 |
2.0.17 | November 2026 | No. Superseded by 2.0.34. | v2.0.17 |
2.0.16 | Not released | Not applicable. | Replaced by v2.0.17 |
2.0.15 | November 2026 | No. Superseded by 2.0.34. | v2.0.15 |
2.0.14 | Not released | Not applicable. | Replaced by v2.0.15 |
2.0.13 | November 2026 | No. Superseded by 2.0.34. | v2.0.13 |
2.0.12 | November 2026 | No. Superseded by 2.0.34. | v2.0.12 |
2.0.11 | November 2026 | Yes. Superseded by 2.0.34. | v2.0.11 |
2.0.10 | November 2026 | Yes. Superseded by 2.0.34. Minimum licensed release for nano Self-run. | v2.0.10 |
2.0.9 | November 2026 | Yes. Superseded by 2.0.34. | v2.0.9 |
2.0.8 | November 2026 | Yes. Superseded by 2.0.34. | v2.0.8 |
2.0.7 | November 2026 | Yes. Superseded by 2.0.34. | v2.0.7 |
2.0.6 | November 2026 | Yes. Superseded by 2.0.34. | v2.0.6 |
2.0.5 | November 2026 | Yes. Superseded by 2.0.34. | v2.0.5 |
2.0.4 | November 2026 | Yes. Superseded by 2.0.34. | v2.0.4 |
2.0.1 | November 2026 | Yes. Superseded by 2.0.34. | v2.0.1 |
How you hear about a new version
- Email. When a version is published, nano emails the owners and admins of every organization with a Self-run deployment. You get one email per version, even if you belong to several organizations. A release with security fixes says so in the subject.
- In nano. Admins of a Self-run deployment see an Update available banner once the deployment's daily license check-in reports a newer version. You can dismiss it; it comes back for the next version.
- In app.nano.rs. The deployment page shows Update available with links to these notes and the upgrade steps.
- For scripts.
GET https://api.nano.rs/api/releases/latestreturns the newest version, its summary, both links and the security flag. It needs no authentication.
Air-gapped deployments make no check-in, so nano shows no banner there. Watch this page or the email instead.
Turn the email off or on
Use the Email me when a new nano version is released checkbox on your Self-run deployment's page in app.nano.rs, or the one-click link at the bottom of any new-version email. The setting is per user. The banner and the deployment page are not affected.