Skip to content

Tag a patch release when license data updates on main - #30

Merged
andrew merged 1 commit into
mainfrom
tag-release-workflow
Sep 20, 2026
Merged

andrew merged 1 commit into
mainfrom
tag-release-workflow

Conversation

@andrew

@andrew andrew commented Sep 20, 2026

Copy link
Copy Markdown
Contributor

The weekly license update workflow merges new scancode data to main, but dependents only see it once a version tag exists, and tagging was manual. v0.3.2 still predates the latest data update (#29).

This adds a workflow that bumps the patch version and tags whenever a push to main touches licenses.json. The tag is created through the API with the default GITHUB_TOKEN, so no credentials are persisted in the checkout. It skips if HEAD is already tagged, and workflow_dispatch allows cutting a patch release manually (useful for tagging the current untagged data update as v0.3.3 once this merges).

Code changes are unaffected and still released by hand.

License data merged to main was not reaching dependents until a tag
was cut by hand. Tag automatically on licenses.json changes, with
workflow_dispatch for manual releases.
@andrew
andrew force-pushed the tag-release-workflow branch from 4c75df2 to ee16c45 Compare September 20, 2026 14:17
@andrew
andrew merged commit 73d1bdf into main Sep 20, 2026
5 checks passed
@andrew
andrew deleted the tag-release-workflow branch September 20, 2026 14:23
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.

1 participant