Upgrade cryptpad from 0.5.4+v2026.2.0 to 0.6.0+v2026.5.0.
Image tag changes
Service
Old tag
New tag
app (cryptpad/cryptpad)
version-2026.2.0
version-2026.5.0
web (nginx)
1.29
1.31
CryptPad 2026.5.0 is the upstream "Spring release" (Diagram/Drawio 29 upgrade, theme switcher, private message notifications, accessibility fixes; intermediate fixes 2026.2.1/2026.2.2). No breaking changes, new env vars, or data migrations. nginx 1.31 brings several CVE fixes; its HTTP/2 header-rejection change does not affect this sidecar (runs HTTP/2-disabled, HTTP/1.1 to app).
Note: the cryptpad/cryptpadversion-* tag is unparseable by abra's upgrade checker, so the app bump was applied manually after confirming version-2026.5.0 on Docker Hub / GitHub releases.
⚠ N/A — SSO not configured on cctest (no authentik creds); not an upgrade regression
abra recipe lint cryptpad -C
✓ PASS (all error-severity rules satisfied)
Next steps (after PR review)
# 1. Review the PR on git.autonomic.zone:# <gitea-pr-url># 2. Pull the PR branch to your local dev machine:cd ~/.abra/recipes/cryptpad
git fetch git@git.autonomic.zone:recipe-maintainers/cryptpad.git upgrade-0.6.0+v2026.5.0:upgrade-0.6.0+v2026.5.0
git checkout upgrade-0.6.0+v2026.5.0
# 3. Push to your upstream fork:
git push dev HEAD:upgrade-0.6.0+v2026.5.0
# 4. Open a PR on upstream and merge it:# https://git.coopcloud.tech/coop-cloud/cryptpad/pulls# 5. After the upstream PR merges, push the tag to publish the release:
git push dev 0.6.0+v2026.5.0
Operators using SSO should set SSO_PLUGIN_VERSION=0.5.0 (recommended by 2026.5.0).
Upgrade `cryptpad` from `0.5.4+v2026.2.0` to `0.6.0+v2026.5.0`.
## Image tag changes
| Service | Old tag | New tag |
|---------|---------|---------|
| app (cryptpad/cryptpad) | version-2026.2.0 | version-2026.5.0 |
| web (nginx) | 1.29 | 1.31 |
CryptPad 2026.5.0 is the upstream "Spring release" (Diagram/Drawio 29 upgrade, theme switcher, private message notifications, accessibility fixes; intermediate fixes 2026.2.1/2026.2.2). No breaking changes, new env vars, or data migrations. nginx 1.31 brings several CVE fixes; its HTTP/2 header-rejection change does not affect this sidecar (runs HTTP/2-disabled, HTTP/1.1 to app).
Note: the `cryptpad/cryptpad` `version-*` tag is unparseable by abra's upgrade checker, so the app bump was applied manually after confirming `version-2026.5.0` on Docker Hub / GitHub releases.
## Test results
| Test | Result |
|------|--------|
| Deploy to cctest (`--chaos --force`) | ✓ PASS (app healthy, web up) |
| `tests/health_check.py` | ✓ PASS (HTTP 200) |
| URL `https://cryptpad.cctest.autonomic.zone` landing page | ✓ PASS |
| `tests/oidc_login.py` | ⚠ N/A — SSO not configured on cctest (no authentik creds); not an upgrade regression |
| `abra recipe lint cryptpad -C` | ✓ PASS (all error-severity rules satisfied) |
## Next steps (after PR review)
```bash
# 1. Review the PR on git.autonomic.zone:
# <gitea-pr-url>
# 2. Pull the PR branch to your local dev machine:
cd ~/.abra/recipes/cryptpad
git fetch git@git.autonomic.zone:recipe-maintainers/cryptpad.git upgrade-0.6.0+v2026.5.0:upgrade-0.6.0+v2026.5.0
git checkout upgrade-0.6.0+v2026.5.0
# 3. Push to your upstream fork:
git push dev HEAD:upgrade-0.6.0+v2026.5.0
# 4. Open a PR on upstream and merge it:
# https://git.coopcloud.tech/coop-cloud/cryptpad/pulls
# 5. After the upstream PR merges, push the tag to publish the release:
git push dev 0.6.0+v2026.5.0
```
Operators using SSO should set `SSO_PLUGIN_VERSION=0.5.0` (recommended by 2026.5.0).
cc @trav @notplants
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Upgrade
cryptpadfrom0.5.4+v2026.2.0to0.6.0+v2026.5.0.Image tag changes
CryptPad 2026.5.0 is the upstream "Spring release" (Diagram/Drawio 29 upgrade, theme switcher, private message notifications, accessibility fixes; intermediate fixes 2026.2.1/2026.2.2). No breaking changes, new env vars, or data migrations. nginx 1.31 brings several CVE fixes; its HTTP/2 header-rejection change does not affect this sidecar (runs HTTP/2-disabled, HTTP/1.1 to app).
Note: the
cryptpad/cryptpadversion-*tag is unparseable by abra's upgrade checker, so the app bump was applied manually after confirmingversion-2026.5.0on Docker Hub / GitHub releases.Test results
--chaos --force)tests/health_check.pyhttps://cryptpad.cctest.autonomic.zonelanding pagetests/oidc_login.pyabra recipe lint cryptpad -CNext steps (after PR review)
Operators using SSO should set
SSO_PLUGIN_VERSION=0.5.0(recommended by 2026.5.0).cc @trav @notplants
didn't pass SSO test, need to fix SSO in tests first
Pull request closed