Skip to content

ci: add tag-module workflow#136

Open
c-julin wants to merge 1 commit into
mainfrom
ci/tagging-wf
Open

ci: add tag-module workflow#136
c-julin wants to merge 1 commit into
mainfrom
ci/tagging-wf

Conversation

@c-julin
Copy link
Copy Markdown
Contributor

@c-julin c-julin commented Feb 26, 2026

Adds a workflow_dispatch workflow to bump and tag Go modules from the Actions UI.

  • Supports specific modules (comma-separated) or all tagged modules
  • patch / minor bump with dry run option
  • Tested locally with act
  • Written by claude but verified and tested behaviour is correct.

Adds a manual workflow to bump and tag Go modules independently.
Supports specific modules (comma-separated) or all tagged modules,
with patch/minor bump and dry run options.
@secpanda
Copy link
Copy Markdown

secpanda commented Feb 26, 2026

Snyk checks have passed. No issues have been found so far.

Status Scanner Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

fi

# Parse version from tag (e.g. rpadmin/v0.2.2 -> 0 2 2)
version=${latest#"$mod/v"}
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd suggest adding a guard against any version that contains rc/alpha/beta or anything like that to make it future proof:

version=${latest#"$mod/v"}
if ! [[ "$version" =~ ^[0-9]+\.[0-9]+\.[0-9]+$ ]]; then
    echo "::error::Latest tag '$latest' is not a plain X.Y.Z version; refusing to auto-bump."                                                                                
    exit 1                                                                                   
  fi 

required: false
default: false
type: boolean

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd add:

concurrency:                                                                                                                                                               
    group: tag-module                                                                                                                                                        
    cancel-in-progress: false

to guard against running more than 1 of this workflow at the time, given that it pushes the tag(s).

cancel-in-progress is true by default, but I'd set it to false just to ensure this isn't canceled mid-run.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants