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

Open
opened 2026-04-02 18:18:28 +00:00 by mprihoda · 0 comments
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.
Sign in to join this conversation.
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
iterative-works/scalatags-webawesome#9
No description provided.