From b39c2aad9952d2f11fa0801ad017588bfa81f846 Mon Sep 17 00:00:00 2001 From: Tim Ruffing Date: Wed, 8 Mar 2023 18:34:51 +0100 Subject: [PATCH] Update doc/release-process.md Co-authored-by: Hennadii Stepanov <32963518+hebasto@users.noreply.github.com> --- doc/release-process.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/release-process.md b/doc/release-process.md index abff034f46..2fd3d3161a 100644 --- a/doc/release-process.md +++ b/doc/release-process.md @@ -17,7 +17,7 @@ This process also assumes that there will be no minor releases for old major rel 1. Open a PR to the master branch with a commit (using message `"release: prepare for $MAJOR.$MINOR.$PATCH"`, for example) that * finalizes the release notes in [CHANGELOG.md](../CHANGELOG.md) (make sure to include an entry for `### ABI Compatibility`), * updates `_PKG_VERSION_*`, `_LIB_VERSION_*`, and sets `_PKG_VERSION_IS_RELEASE` to `true` in `configure.ac`, and - * updates `(package secp256k1 VERSION ...` and `LIB_VERSION_*` in `CMakeLists.txt`. + * updates `project(secp256k1 VERSION ...` and `*_LIB_VERSION_*` in `CMakeLists.txt`. 2. After the PR is merged, tag the commit and push it: ``` RELEASE_COMMIT=