release process: mention the `[Unreleased]` link clearly
What the developer wrote
Authored by Jonas Nick
release process: mention the `[Unreleased]` link clearly
Adding this link was forgotten in the first version of the 0.7.1 release PR but
caught in PR review.
What changed, and why it matters
This commit is a one-line update to the project's internal release-process documentation. It reminds maintainers to add a matching '[Unreleased]' hyperlink at the bottom of the changelog, not just the section header. There is no code change, no cryptographic change, and no security relevance.
No security action needed. This is a documentation-only process clarification.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies doc/release-process.md, expanding a bullet in the post-release cleanup checklist. The original instruction said to add an ‘[Unreleased]’ section header to CHANGELOG.md; the revised instruction also requires adding the corresponding ‘[Unreleased]’ link at the bottom of the file. No source files, build scripts, tests, or cryptographic logic were changed.
Changed components
doc/release-process.mdInspect captured patch +1 / −1
diff --git a/doc/release-process.md b/doc/release-process.md
index a64bae0..3cf183d 100644
--- a/doc/release-process.md
+++ b/doc/release-process.md
@@ -61,7 +61,7 @@ Perform these checks when reviewing the release PR (see below):
4. Open a PR to the master branch with a commit (using message `"release cleanup: bump version after $MAJOR.$MINOR.$PATCH"`, for example) that
* sets `_PKG_VERSION_IS_RELEASE` to `false` and increments `_PKG_VERSION_PATCH` and `_LIB_VERSION_REVISION` in `configure.ac`,
* increments the `$PATCH` component of `project(libsecp256k1 VERSION ...)` and `${PROJECT_NAME}_LIB_VERSION_REVISION` in `CMakeLists.txt`, and
- * adds an `[Unreleased]` section header to the [CHANGELOG.md](../CHANGELOG.md).
+ * adds an `[Unreleased]` section header and a corresponding `[Unreleased]` link at the bottom of [CHANGELOG.md](../CHANGELOG.md).
If other maintainers are not present to approve the PR, it can be merged without ACKs.
5. Create a new GitHub release with a link to the corresponding entry in [CHANGELOG.md](../CHANGELOG.md).
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.