brooktrails/forgejo-runner-operator
Watch
1
0
Fork
You've already forked forgejo-runner-operator
 0
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity Actions

fx(ci): update changelog inside publish instead of a tag-triggered workflow #34

Merged
rcsheets merged 2 commits from fix/changelog-in-publish into master 2026-06-26 00:28:43 +00:00
Conversation 1 Commits 2 Files changed 3 +57 -66
rcsheets commented 2026-06-26 00:28:22 +00:00
Owner
Copy link

This Forgejo instance does not fire workflows for tags pushed by a CI job
(Actions-originated events are suppressed to prevent loops), so the
tag-triggered changelog.yml never ran when publish pushed v0.4.1.

Make the step explicit and imperative instead of relying on that implicit,
instance-specific trigger behavior: publish now runs hack/update-changelog.sh
itself, right after pushing the tag, and commits CHANGELOG.md to master with
[skip ci]. The changelog work is failure-isolated so it can never fail an
already-successful release. Delete the dead changelog.yml.

This Forgejo instance does not fire workflows for tags pushed by a CI job (Actions-originated events are suppressed to prevent loops), so the tag-triggered changelog.yml never ran when publish pushed v0.4.1. Make the step explicit and imperative instead of relying on that implicit, instance-specific trigger behavior: publish now runs hack/update-changelog.sh itself, right after pushing the tag, and commits CHANGELOG.md to master with [skip ci]. The changelog work is failure-isolated so it can never fail an already-successful release. Delete the dead changelog.yml. 
This Forgejo instance does not fire workflows for tags pushed by a CI job
(Actions-originated events are suppressed to prevent loops), so the
tag-triggered changelog.yml never ran when publish pushed v0.4.1.

Make the step explicit and imperative instead of relying on that implicit,
instance-specific trigger behavior: publish now runs hack/update-changelog.sh
itself, right after pushing the tag, and commits CHANGELOG.md to master with
[skip ci]. The changelog work is failure-isolated so it can never fail an
already-successful release. Delete the dead changelog.yml.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
docs(changelog): backfill v0.4.1 entry missed by the dead workflow
Some checks failed
CI (next Go) / next-go (tip) (pull_request) Successful in 4m24s
Details
CI / ci (pull_request) Failing after 2s
Details
8eef132c77 
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
pr-reviewer-bot commented 2026-06-26 00:28:24 +00:00
Collaborator
Copy link

Automated review by pr-reviewer v0.29.1 | Safety Check | Mistral Small | tracking id r-3dc7a7-78d161
This is an AI-generated review and may contain mistakes.

Status: ❌ Failed

Review failed. Tracking id r-3dc7a7-78d161 — see logs for details.

Comment @pr-reviewer-bot retry to try again.

*Automated review by [pr-reviewer](https://git.brooktrails.org/brooktrails/pr-reviewer) v0.29.1 | Safety Check | Mistral Small | tracking id `r-3dc7a7-78d161`* *This is an AI-generated review and may contain mistakes.* **Status:** ❌ Failed --- Review failed. Tracking id `r-3dc7a7-78d161` — see logs for details. Comment `@pr-reviewer-bot retry` to try again.
rcsheets merged commit 5dbfbf723a into master 2026-06-26 00:28:43 +00:00
rcsheets deleted branch fix/changelog-in-publish 2026-06-26 00:28:43 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
brooktrails/forgejo-runner-operator!34
No description provided.