This repository has been archived by the owner on Nov 30, 2024. It is now read-only.
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.
Create an npm Account:
If you don't already have one, create an npm account at https://www.npmjs.com/signup.
To keep sensitive information like your npm token secure, you'll need to add them as secrets in your GitHub repository:
NPM_TOKEN
: Your npm authentication token.GH_TOKEN
: A GitHub personal access token for deploying GitHub releases.Ensure that your library follows semantic versioning (SemVer) by updating the version number in your
package.json
file with each release. GitHub Actions will only publish a new version when a new tag is pushed with an updated version.Deploy a Release:
To create a new release, use the GitHub Releases feature. You can create a new release through the GitHub web interface or by creating a new tag and pushing it to the repository. Remember to attach a changelog and any release notes for users.
Once your workflow is set up, you can monitor it under the "Actions" tab in your GitHub repository. You will see the workflow running when a new tag is pushed, and it will publish your package to npm automatically.
After publishing, you can verify that your package is available on npm by running: