ci: open release pull requests with a workflow - #14
Merged
Merged
Conversation
dnd-mapp-bot
approved these changes
Sep 26, 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
2 participants
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.
Adds a manually started
prepare-release.yamlthat callsdnd-mapp/action-prepare-releasev1.1.0. It runschangelog release --bump, commits the result through the API with the dnd-mapp GitHub App, and opens thechore: release X.Y.Zpull request with auto-merge on.CONTRIBUTING.mdnow starts the workflow instead of preparing the commit by hand.AGENTS.mdsays release pull requests come from the workflow.No changelog entry, because this changes only contributor tooling.
This is the same change as dnd-mapp/changelog-tools#15. The workflow has already released
action-prepare-release1.1.0 andchangelog-tools1.1.1: both release commits showed as Verified,CIran, and auto-merge turned on.