Repository navigation
Conversation
A subpackage's release notes listed every pull request merged and every issue closed in the repository since its previous release, so in a monorepo they mostly described other packages. Keep only the pull requests that changed files in the subpackage's directory, and leave out issues, which can't be attributed to a subpackage.
The conventional changelog started from the newest GitHub release in the repository, whatever package or version it belonged to, and listed every commit since then. For a subpackage, that is usually another package's release; for a backport, a higher version. Start from the package's highest earlier version tag instead, using the lookup the default changelog already uses, and for a subpackage only list commits that changed its directory. Tags created earlier in the same run are added to the tag cache, so that a backfilled release starts from the one created just before it.
maleadt
force-pushed
the
tb/subdir-changelog
branch
from
November 17, 2026 10:32
eccc3de to
4317f86
Compare
This branch has not been deployed
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.
A subpackage's release notes list every pull request merged and every issue closed in the repository since its previous release. In a monorepo they mostly describe other packages. For example, OrdinaryDiffEqPDIRK-v2.5.4 lists Extrapolation and DAE initialization changes, and KernelInterface-v0.4.6 repeats the notes of KernelAbstractions v0.10.6.
For subpackages:
conventionalformat: the log only covers the subpackage's directory. It also now starts from the package's own previous version tag, not from the newest release in the repository, which could belong to another package or a higher version. That second change fixes backports of top-level packages too.githubformat: unchanged, because GitHub's release-notes API has no path filter.