recipe-maintainers/cc-ci-orchestrator
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
1f7fc7eb39c1c3ca12fedbf0bf4ddffc8d6a2573
cc-ci-orchestrator/cc-ci-plan/upstream/cryptpad.md
autonomic-bot f0716764db feat(recipe-upgrade): upstream release-notes registry + recipe-README read (recipe-maintainer parity) 
Close the two gaps vs recipe-maintainer's recipe-upgrade-plan:
- Per-recipe release-notes registry at cc-ci-plan/upstream/<recipe>.md (discover the source repo +
  releases/changelog URL for each image once, persist+commit, reuse) — fetch release notes FROM those
  URLs instead of rediscovering ad-hoc each run. Format doc + cryptpad seed included.
- Explicitly read the recipe's README for shipped upgrade/migration notes.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-05 01:28:27 +00:00

772 B
Raw Blame History

Upstream sources — cryptpad

service image source repo releases / changelog
app cryptpad/cryptpad https://github.com/cryptpad/cryptpad https://github.com/cryptpad/cryptpad/releases
web nginx https://github.com/nginx/nginx https://nginx.org/en/CHANGES

Standing notes

  • abra recipe upgrade cannot parse the version-YYYY.M.D tag format of the cryptpad/cryptpad image, so the app image is bumped by hand; the nginx sidecar is what abra recipe upgrade actually moves.
  • nginx is HTTP/1.1-only here (sidecar on :8083, proxy_http_version 1.1), so HTTP/2/3 CVE changes in nginx releases generally don't affect this recipe — but still note them.