From bf5163c2f49e196aaa291cc93c3ef6281c90a3a1 Mon Sep 17 00:00:00 2001 From: Paul Berberian Date: Wed, 21 Feb 2024 15:07:20 +0100 Subject: [PATCH] doc: Replace forgotten mentions of the master branch --- doc/contributing/releases.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/contributing/releases.md b/doc/contributing/releases.md index be13e6b199..04300b767e 100644 --- a/doc/contributing/releases.md +++ b/doc/contributing/releases.md @@ -145,7 +145,8 @@ Before each official releases, a list of steps are performed by its maintainers: as a dependency. 10. If and only if no problem was seen perform a signed merge without - fast-forward of the release branch into master (`git merge -S --no-ff release/vXX.XX.XX master`) + fast-forward of the release branch into legacy-v3 + (`git merge -S --no-ff release/vXX.XX.XX legacy-v3`) 11. Launch script to update the gh-pages demo (`./scripts/update_gh-pages_demo`) @@ -156,7 +157,7 @@ Before each official releases, a list of steps are performed by its maintainers: 14. Check that the new demo and the new doc work as expected -15. If all seems good, push to origin/master your local master branch. +15. If all seems good, push to remote `legacy-v3` your local `legacy-v3` branch. 16. run `npm publish --tag legacy-v3` to publish the new version on npm's registry with the `legacy-v3` tag.