From c649a261b39c267e34ad6b0b2db9436500aed870 Mon Sep 17 00:00:00 2001
From: Anonymoussaurus <50231698+AnonymousWP@users.noreply.github.com>
Date: Mon, 10 Mar 2025 20:25:58 +0100
Subject: [PATCH] docs(release): mention that we need to update `Cargo.lock`

---
 RELEASE.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/RELEASE.md b/RELEASE.md
index 07bc697..c029638 100644
--- a/RELEASE.md
+++ b/RELEASE.md
@@ -16,7 +16,7 @@ In that case, we should closely review the PR and 'compare' it with what semanti
 - [ ] Make sure the Milestone is completed and if not, check what needs to be done to complete it.
 - [ ] Make sure all merged PRs regarding the application follow the Conventional Commit Messages style. This makes sure that when generating a changelog, the changes look consistent, which in turn improves readability.
 - [ ] Make sure all merged PRs have the correct labels assigned, as the changelog is generated based on labels.
-- [ ] Create a release preparation PR that bumps the UAD-ng version in `Cargo.toml`
+- [ ] Create a release preparation PR that bumps the UAD-ng version in `Cargo.toml` and `Cargo.lock`.
 
 When all the above has been checked, you can push a tag to `main` to trigger the GitHub Action that creates a release: