Release automation - #39
Merged
Merged
Conversation
bright77777
approved these changes
Aug 3, 2026
bright77777
requested changes
Aug 3, 2026
bright77777
left a comment
Collaborator
There was a problem hiding this comment.
ce PR a 3 commits , qui ont rien a voir avec le release automation
FoukengFranck
force-pushed
the
release-automation
branch
from
August 4, 2026 06:13
3209603 to
5d62c8b
Compare
Contributor
Author
|
c'est bon Mr |
bright77777
approved these changes
Aug 4, 2026
This file contains hidden or 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
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.
Description
Automatisation de la création des releases : plus besoin de mettre à jour package.json ou de créer les tags à la main.
feat:/fix:), calcule la version SemVer, génère le CHANGELOG.md
Si aucun commit feat:/fix: n'a été mergé depuis la dernière release, le workflow ne fait rien, pas besoin de vérifier "s'il y a eu des PR dans la semaine" à la main.
Veillez nous Résume clairement ce que fait cette PR et pourquoi
Type de changement
Package(s) concerné(s)
Comment ça a été testé ?
Pas encore testé, le workflow ne peut se déclencher utilement que depuis la branche master donc le vrai test se fera juste
après le merge de cette PR.
Décris les tests effectués : local, Docker, CI...
Checklist avant de demander une revue
npm run typecheckpasse sans erreurnpm run testpasse sans erreurNotes complémentaires
Contexte additionnel, captures d'écran, liens vers des tickets liés, etc.
Closes #