snowykami/meilisearch
1
0
Fork 0
mirror of https://github.com/meilisearch/meilisearch.git synced 2025-09-03 19:26:33 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #5815 from meilisearch/curquiza-patch-2

Browse Source 
Minor update for release process
This commit is contained in:
Clément Renault
2025-08-11 17:14:48 +00:00
committed by GitHub
parent b7f32c5acd 68280bad9e
commit 3d271c25c7
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
documentation/release.md
View File

@ -22,7 +22,7 @@ This guide is to describe how to make releases for the current repository.
2. Go to the GitHub interface, in the [`Release` section](https://github.com/meilisearch/meilisearch/releases).
3. Select the already drafted release or click on the `Draft a new release` button if you want to start a blank one, and fill the form with the appropriate information.
⚠️ Publish on `main`
⚠️ Publish on a specific commit defined by the team. Or publish on `main`, but ensure you do want all the PRs merged in your release.
⚙️ The CIs will be triggered to:
- [Upload binaries](https://github.com/meilisearch/meilisearch/actions/workflows/publish-binaries.yml) to the associated GitHub release.
@ -31,7 +31,7 @@ This guide is to describe how to make releases for the current repository.
- [Move the `latest` git tag to the release commit](https://github.com/meilisearch/meilisearch/actions/workflows/latest-git-tag.yml).
### 🔥 How to do a patch release for an hotfix
### 🔥 How to do a patch release for a hotfix
It happens some releases come with impactful bugs in production (e.g. indexation or search issues): we obviously don't wait for the next cycle to fix them and we release a patched version of Meilisearch.