Skip to content

chore: wire up force_publish input in release workflow#39

Closed
Rodriguespn wants to merge 1 commit into
mainfrom
fix/force-publish-workflow
Closed

chore: wire up force_publish input in release workflow#39
Rodriguespn wants to merge 1 commit into
mainfrom
fix/force-publish-workflow

Conversation

@Rodriguespn

@Rodriguespn Rodriguespn commented Jun 9, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Adds workflow_dispatch trigger with a force_publish boolean input so the release artifact can be re-published manually without a new release-please run
  • Derives the release tag from the latest git tag when release-please did not create one (e.g. when re-running after a failed upload)
  • Adds --clobber to gh release upload to overwrite existing assets instead of erroring

@Rodriguespn Rodriguespn force-pushed the fix/force-publish-workflow branch from 05061ed to e6362d0 Compare June 9, 2026 10:59
@Rodriguespn Rodriguespn changed the title fix: wire up force_publish input in release workflow chore: wire up force_publish input in release workflow Jun 9, 2026
@Rodriguespn Rodriguespn marked this pull request as ready for review June 9, 2026 10:59
Add workflow_dispatch trigger with force_publish flag so the release
artifact can be re-published manually without a new release-please run.
Derives the tag from the latest git tag when release-please did not
create one, and uses --clobber to overwrite existing release assets.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@Rodriguespn

Copy link
Copy Markdown
Collaborator Author

Closing this. Check supabase/agent-skills#104 (comment) for more details

@Rodriguespn Rodriguespn closed this Jun 9, 2026
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