Repository navigation
Ne plus générer les CHANGELOGs avec release-please - #2803
Open
StephaneTrebel wants to merge 3 commits into
Open
StephaneTrebel wants to merge 3 commits into
StephaneTrebel wants to merge 3 commits into
Conversation
StephaneTrebel
marked this pull request as ready for review
September 30, 2026 13:51
shikanime
previously approved these changes
Oct 1, 2026
Refs #2802 Generated with AI assistance, reviewed by @StephaneTrebel
StephaneTrebel
force-pushed
the
docs/release-notes-changelogs
branch
from
October 13, 2026 15:32
a8aa528 to
87fb4ca
Compare
release-please
Refs #2802 Generated with AI assistance, reviewed by @StephaneTrebel
Refs #2802 Generated with AI assistance, reviewed by @StephaneTrebel
StephaneTrebel
force-pushed
the
docs/release-notes-changelogs
branch
from
October 13, 2026 15:35
87fb4ca to
e0b3075
Compare
|
shikanime
approved these changes
Oct 14, 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.

0 New Issues
0 Fixed Issues
0 Accepted Issues
No data about coverage (23.50% Estimated after merge)
Issues liées
Issues numéro: #2802
Quel est le comportement actuel ?
release-please génère
CHANGELOG.mdà partir des types de commits conventionnels. Ce fichier ne distingue pas le périmètre du milestone, la livraison présente dans le tag et les anomalies d’attribution.Quel est le nouveau comportement ?
release-please conserve le versionnement, les tags et les GitHub Releases sans écrire de changelog.
cpn-release-notesproduit les notes validées et leurs audits dansCHANGELOGS/; l’historique généré est archivé dansCHANGELOGS/CHANGELOG_ARCHIVE.md.Cette PR introduit-elle un breaking change ?
Non.
Autres informations
Contrôles exécutés : validation JSON, vérification de l’archive et de l’absence de
CHANGELOG.md,pnpm format,pnpm lint,pnpm buildetpnpm test.