Skip to content

ci: release-assets - fix retagged zip-release pin; dispatchable at a tag - #838

Merged
ronaldtse merged 1 commit into
mainfrom
fix/assets-workflow-zip-tag
Nov 11, 2026
Merged

ronaldtse merged 1 commit into
mainfrom
fix/assets-workflow-zip-tag

Conversation

@ronaldtse

Copy link
Copy Markdown
Contributor

Summary

  • thedoctor0/zip-release@v0.7.6 no longer resolves — upstream retagged, the tag is now 0.7.6. Both archive steps updated.
  • workflow_dispatch gains a tag input (tag: ${{ inputs.tag || github.ref }}) so the failed v3.4.0 release-assets run can be backfilled from the fixed workflow without retagging (re-pushing v3.4.0 would re-run the gem job against an already-published version).

Verification

  • After merge: dispatch release-assets with tag=v3.4.0; the release gains vis_json.zip and metadata.json.zip.

… tag

thedoctor0/zip-release retagged upstream: v0.7.6 no longer exists
(the tag is now 0.7.6), so the v3.4.0 release-assets job failed at
action resolution and the release is missing its vis_json/metadata
assets. The workflow now dispatches with an explicit tag input so the
v3.4.0 assets can be backfilled from the fixed workflow (tag: ${{
inputs.tag || github.ref }}).
@ronaldtse
ronaldtse merged commit 1038600 into main Nov 11, 2026
13 checks passed
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