From 095cba8fba6bc4faeeac364e1cdc93a72572152b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Cl=C3=A9mentine?= <clementine@meilisearch.com>
Date: Tue, 5 Aug 2025 15:29:42 +0200
Subject: [PATCH] Minor docs update about release.md

---
 documentation/release.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/documentation/release.md b/documentation/release.md
index f70fcf872..69ce32aff 100644
--- a/documentation/release.md
+++ b/documentation/release.md
@@ -7,7 +7,7 @@ This guide is to describe how to make releases for the current repository.
 1. A weekly meeting is done every Monday to define the release and to ensure minimal checks before the release.
 <details>
 <summary>Check out the TODO 👇👇👇</summary>
-- [ ] Define the version of the release (`vX.Y.Z`)
+- [ ] Define the version of the release (`vX.Y.Z`) based on our <a href="https://github.com/meilisearch/meilisearch/blob/main/documentation/versioning-policy.md">Versioning Policy</a></br>.
 - [ ] Manually test `--experimental-dumpless-upgrade` on a DB of the previous Meilisearch minor version</br>
 - [ ] Check recent <a href="https://github.com/meilisearch/meilisearch/actions">automated tests</a> on `main`</br>
     - [ ] Scheduled test suite</br>