Tag a patch release when license data updates on main - #30
Merged
Merged
Conversation
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
force-pushed
the
tag-release-workflow
branch
from
September 20, 2026 14:17
4c75df2 to
ee16c45
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.2still 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 defaultGITHUB_TOKEN, so no credentials are persisted in the checkout. It skips if HEAD is already tagged, andworkflow_dispatchallows cutting a patch release manually (useful for tagging the current untagged data update asv0.3.3once this merges).Code changes are unaffected and still released by hand.