Add GitHub Actions pipeline for npm releases

[Wombosvideo]

Quick Glance

• Add GitHub Actions pipeline for npm releases

Description

I saw that the npm packages were out of date and not reflecting the same state as the documentation website. I suggest adding a GitHub Actions pipeline to automate npm releases.

Why this is important

Keeping track of changes and manually updating npm releases can be a hassle and easily repeat situations of out-of-date packages. Additionally, the release version should always match the feature set and code samples in the documentation.

Original Issue Content

You mentioned certain fixes and new features but the NPM package version hasn't changed since before that. Do you need help integrating NPM releases to GitHub Actions?

[kampsy]

Hello @Wombosvideo,

Yes, I could definitely use some help setting up the NPM release with GitHub Actions!

I really appreciate any help you can provide.

[Wombosvideo]

I will look into this as soon as I can. I have some experience with GitHub Actions but I'd need to experiment a little first. I'll open a PR as soon as I am either confident that it works, or if it needs review (that would be a draft PR then).

[Wombosvideo]

In terms of Releases, semantic-release is probably the easiest solution. And it seems like they've made it easy to use it for npm package releases as well.

Since you're already using the right commit message format it should be a lot easier to implement.

[kampsy]

Awesome, looking forward to it! My experience with GitHub Actions has mostly been around deployments, running linting, Vite tests, and Playwright, but not NPM package releases. Excited to see your PR!

i have also put the npm token

in the repo environment

[github-actions[bot]]

:tada: This issue has been resolved in version 1.0.0 :tada:

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot :package::rocket: