Skip to content

The shared tagging workflow has no manual path, so a dropped push event strands a release #57

Description

@bdbarnett

On 2026-09-28 GitHub ran no workflow for the merge of an audiodsp release PR (PyDevices/audiodsp#167): the push event never arrived, and its status page showed no incident. The release was never tagged. Every repository's tag-release.yml has only a push trigger filtered on VERSION, and reusable-tag-on-release-merge.yml decides by git diff HEAD^ HEAD -- VERSION, so nothing can run it by hand: a manual run at the branch head sees no change.

audiodsp got a local fix (PyDevices/audiodsp#171): workflow_dispatch on its caller, with a job that tags the commit on main that last changed VERSION (first-parent) and refuses when the tag exists.

Wanted here: the same path inside the shared workflow, so every caller gets it by adding one trigger line.

  • an input or an event check that skips the HEAD^..HEAD diff on a manual run;
  • the target is git log -1 --first-parent --format=%H -- VERSION, not GITHUB_SHA;
  • the existing refusals stay (tag exists; VERSION not a release version);
  • a new publishing-vN tag, and the callers moved to it.

Until then, a dropped event on any other repository needs the same local change audiodsp took.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions