Repository navigation
chore: explain how CHANGES.md works with release-please - #312
Merged
lhoupert merged 1 commit intoNov 10, 2026
Merged
Conversation
Breaking changes noted only in CHANGES.md made release-please propose a patch release.
Contributor
Author
|
@vincentsarago happy to keep writing changes by hand for tipg vs automatating that in titiler-pgstac https://github.com/stac-utils/titiler-pgstac/pull/356/changes ? |
vincentsarago
approved these changes
Nov 10, 2026
This was referenced Nov 10, 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.
Spells out how CHANGES.md works with release-please: contributors add entries under
[unreleased]and mark breaking commits with!, and maintainers add the version heading at release time, with aRelease-Asline when needed (as in #311).