Add Github Action workflow to publish releases automatically to NPM registry. Fixes #537 #538
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This adds Github Action to automatically release new git tags into npm registry.
I noticed that the Notion search has been broken for a while from this issue: transitive-bullshit/nextjs-notion-starter-kit#546
@danni-cool wrote a nice blog post about this problem here: https://danni.cool/fixed-the-broken-search-in-nextjs-notion-starter-kit
If we would automatically deploy the new git tags into npm we wouldn't need to create patches like he is proposing.
Fixes #537.
Steps to do before merging ❗