Make release pipeline manual instead of auto-running on push to main #61

New issue

Open

opened 2026-07-26 16:35:58 +02:00 by cloudbot · 0 comments

cloudbot commented

2026-07-26 16:35:58 +02:00

Collaborator

Summary

release.yml currently runs automatically on every push to main
(on: push: branches: [main]), triggering semantic-release and a
Forgejo release on every merge. Change this to a manual trigger instead.

Current behavior

on:
  push:
    branches: [main]

Desired behavior

Replace with workflow_dispatch so releases only happen when explicitly
triggered from the Forgejo Actions UI (or API), rather than on every
merge to main.

Notes

android-build.yml reacts to the Forgejo release event itself, not to
the push — no change expected there, but worth a quick sanity check
once release.yml is updated.
See the semantic-release-pipeline skill for background on how these
two workflows are wired together.

## Summary `release.yml` currently runs automatically on every push to `main` (`on: push: branches: [main]`), triggering semantic-release and a Forgejo release on every merge. Change this to a manual trigger instead. ## Current behavior ```yaml on: push: branches: [main] ``` ## Desired behavior Replace with `workflow_dispatch` so releases only happen when explicitly triggered from the Forgejo Actions UI (or API), rather than on every merge to main. ## Notes - `android-build.yml` reacts to the Forgejo release event itself, not to the push — no change expected there, but worth a quick sanity check once release.yml is updated. - See the `semantic-release-pipeline` skill for background on how these two workflows are wired together.

cloudbot added the

chore

label

2026-07-26 16:35:58 +02:00

No milestone

No project

No assignees

1 participant

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

utilities/Logbook#61

No description provided.

Rows
Columns