Skip to content

Revert "Switch GitHub release step to use 'gh release create'"#338

Merged
colindean merged 1 commit into
mainfrom
revert-336-use-gh-for-releases
Mar 29, 2026
Merged

Revert "Switch GitHub release step to use 'gh release create'"#338
colindean merged 1 commit into
mainfrom
revert-336-use-gh-for-releases

Conversation

@colindean
Copy link
Copy Markdown
Collaborator

Reverts #336

I realized that releases would fail in this because it lacks the ability to update, and my current release method involves creating the release, not pushing tags that would then create the release. GH doesn't allow the user to create using the web interface a tag without a release, it seems.

gh release create ${TAG} \
--notes-file generated_changelog.md
dist/**/*
uses: softprops/action-gh-release@153bb8e04406b158c6c84fc1615b65b24149a1fe # v2.6.1

Check notice

Code scanning / zizmor

action functionality is already included by the runner Note

action functionality is already included by the runner
@colindean colindean merged commit 24a5fde into main Mar 29, 2026
39 of 40 checks passed
@colindean colindean deleted the revert-336-use-gh-for-releases branch March 29, 2026 18:34
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.

2 participants