[FEATURE] Génére correctement le changelog pour une release après une correction de release à chaud #120
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
francois2metz
added
Tech Review Needed
team-captains
…elease après une correction de release à chaud"" This reverts commit d84e854.
github-actions
bot
force-pushed
the
fix-changelog
branch
from
f0f1af7 to
aa26f8d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🦄 Problème
Reprise de #101
En cas de hotfix, si des PRs sont mergé sur dev avant le hotfix (qui crée un tag sur une autre branche), le changelog de la version suivante ne contient pas ces PRs mergés.
🤖 Solution
On récupére la derniere version qui a été releaser via le package.json.
💯 Pour tester
npm run test