Switch publish workflow to tag-based triggers instead of main branch push #9

New issue

Closed

opened 2026-04-02 18:18:28 +00:00 by mprihoda · 1 comment

mprihoda commented

2026-04-02 18:18:28 +00:00

(Migrated from github.com)

The current publish workflow triggers on every push to main, which publishes a new version on every merge. This should be changed to tag-based triggers (v*) so that releases are intentional.

Current behavior

on:
  push:
    branches: [main]
    tags: ['v*']

Proposed change

on:
  push:
    tags:
      - 'v*'

This way publishing only happens when a version tag is pushed (e.g. git tag v0.2.0 && git push origin v0.2.0), giving explicit control over releases.

The current publish workflow triggers on every push to `main`, which publishes a new version on every merge. This should be changed to tag-based triggers (`v*`) so that releases are intentional. ### Current behavior ```yaml on: push: branches: [main] tags: ['v*'] ``` ### Proposed change ```yaml on: push: tags: - 'v*' ``` This way publishing only happens when a version tag is pushed (e.g. `git tag v0.2.0 && git push origin v0.2.0`), giving explicit control over releases.

mph commented

2026-09-11 19:07:57 +00:00

Owner

Resolved by #11 (5a2dec4). The publish workflow now publishes to Maven Central only on v* tags (if: github.ref_type == 'tag'). A push to main publishes only the -SNAPSHOT to the Forgejo Maven registry, and that is intended. A tag-only trigger would stop those snapshot publishes, so we do not change the trigger.

Resolved by #11 (5a2dec4). The publish workflow now publishes to Maven Central only on `v*` tags (`if: github.ref_type == 'tag'`). A push to `main` publishes only the -SNAPSHOT to the Forgejo Maven registry, and that is intended. A tag-only trigger would stop those snapshot publishes, so we do not change the trigger.

mph closed this issue

2026-09-11 19:07:57 +00:00