Skip to content

Conversation

@dawsontoth
Copy link

No description provided.


Remember to hit save!

## 5. Using Semantic Release (Optional)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm a little confused; is semantic-release really optional? This process seems specific to it hence the very first section:

These are required for semantic-release to create GitHub releases and publish to NPM.

If it is, what is the other option? What if I wanted to manage the version and then push the updated package.json to the repo; can the repo then publish on that commit?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. If you manually update the package.json version and invoke your release workflow, it will work without semantic release.

dawsontoth and others added 2 commits February 10, 2026 12:42
Co-authored-by: Ethan Arrowood <ethan@arrowood.dev>
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