Skip to content

github release created by this workflow no longer goes to draft and gets automatically published#1231

Open
ethankonk wants to merge 1 commit intomainfrom
ethan/auto-publish-gh-release
Open

github release created by this workflow no longer goes to draft and gets automatically published#1231
ethankonk wants to merge 1 commit intomainfrom
ethan/auto-publish-gh-release

Conversation

@ethankonk
Copy link
Contributor

Summary & Motivation

  • This section of the workflow is now gated by our production environment approvals guard so its safe to auto publish the Github release instead of drafting it and having to manually publish it.
    • Main reason to change this is we often forget to publish the Github release after doing the NPM release which leaves us in a weird de-synchronized state on Github. This is just overall cleaner and we can always edit release descriptions if we spot something after the fact.

How I Tested These Changes

  • Will test with the next release 😊

@ethankonk ethankonk force-pushed the ethan/auto-publish-gh-release branch from 2867ae1 to 8fe1297 Compare March 2, 2026 21:36
@codesandbox-ci
Copy link

codesandbox-ci bot commented Mar 2, 2026

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 8fe1297:

Sandbox Source
@turnkey/example-react-components Configuration

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