What the developer wrote
Authored by Nicolas Dorier
Document post release process
What changed, and why it matters
This commit only adds documentation describing what maintainers should do after a software release. It does not change any code, configuration, or security behavior of BTCPay Server itself.
No security action needed; this is a documentation-only process update.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff appends a ‘Post-release’ section to docs/maintainers/README.md with three procedural steps: bump the version in btcpayserver-docker, publish the GitHub release, and bump the version/submodule in btcpayserver-plugin-template. No source code, build scripts, dependencies, or runtime logic are modified.
Changed components
docs/maintainers/README.mdInspect captured patch +12 / −0
### docs/maintainers/README.md
@@ -131,3 +131,15 @@ When creating a release:
8. After CI builds the Docker images, copy the new version's changelog section into the GitHub release.
Before publishing, confirm that the release type and timing follow the [release cycle policy](#release-cycles).
+
+### Post-release
+
+After the release tag and Docker images are available:
+
+1. Bump the BTCPay Server version in
+ [`btcpayserver-docker`](https://github.com/btcpayserver/btcpayserver-docker).
+2. Publish the release on GitHub.
+3. In
+ [`btcpayserver-plugin-template`](https://github.com/btcpayserver/btcpayserver-plugin-template),
+ bump the BTCPay Server version in `Plugin.cs` and update the BTCPay Server
+ submodule to the release.Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.