Skip to content

fix: use the native generated Changelog version PR title #50

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
coisa merged 1 commit into from
Oct 26, 2026
Merged

fix: use the native generated Changelog version PR title #50

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions .changelog/native-version-pr-title.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
---
category: fixed
type: patch
---

Uses the published Changelog 0.4.1 lifecycle's native repository and version title
template when preparing or refreshing the managed version pull request, without
overriding the generated title in this repository.
2 changes: 1 addition & 1 deletion .github/workflows/repository-changelog.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ jobs:
pull-requests: write
issues: read
statuses: write
uses: php-fast-forward/changelog/.github/workflows/changelog.yml@85474de5a16bb08f83c9f30e0ed72f331a210f07 # v0.3.0
uses: php-fast-forward/changelog/.github/workflows/changelog.yml@203db95e68fc974e95ba1a921f08d01f88851be1 # v0.4.1
with:
runs-on: '["ubuntu-latest"]'
base-branch: main
Expand Down
8 changes: 7 additions & 1 deletion docs/automation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -65,8 +65,14 @@ The initial `.changelog` fragment is explicitly `minor`; Changelog's supported
baseline `0.0.0` yields `0.1.0` without a manual tag or engine change. Before wiring
publication, verify the selected published Changelog tag, source workflow inputs,
release transaction and token availability. The caller selects the verified
published `v0.3.0` commit `85474de5a16bb08f83c9f30e0ed72f331a210f07`.
published `v0.4.1` commit `203db95e68fc974e95ba1a921f08d01f88851be1`.
Its documented no-tag baseline and minor fragment support initial `0.1.0`.
The caller deliberately omits `version-pr-title`: the selected lifecycle supplies
its native `chore(release): {repository} v{current_version} → v{next_version}`
template. Repository and version values come from the validated release plan;
this is not a manually renamed PR or a title copied into consumer configuration.
The generator can refresh an existing managed PR's title without replacing human
body text. This change does not itself authorize merging a version PR or publishing.
It uses the existing GitHub Actions token; if repository policy prevents PR
creation, report the gate without changing that setting or creating credentials.
0.x policy requires reviewing every prepared version PR; reject any plan
Expand Down
Loading