Merged
Conversation
kazuma0129
reviewed
Nov 14, 2025
nana4gonta
approved these changes
Nov 14, 2025
Merged
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.
This PR fixes several issues found after testing the workflow introduced in the previous PR (#31).
PRs were not categorized by labels
→ Added a configuration file at
.github/release.yml.See: https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes#configuring-automatically-generated-release-notes
Generated release notes included all PRs in the repository instead of only those since the previous release
→ Added
previous_tag_nameandtarget_commitishparameters to the generate-notes API call.Release PRs created by GitHub Actions could not be merged due to branch protection rules
→ Added the
ready_for_reviewactivity type to the build workflow trigger.→ Release PRs are now created as draft PRs.
→ When maintainers mark the PR as Ready for review, the build workflow is automatically triggered and the PR becomes mergeable once checks pass.
Note
Just Specifying
means
See https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows#pull_request