First off, pretty cool component! Pretty much just what I was looking for and a bit more!
However I'm hesitant to bring in into my project because I'll be unable to review upgrades, since versions aren't tagged in GitHub & there's no changelog.
I strongly suggest getting set up with something like semantic-release to automate the release process (including updating version number according to semver, generating changelog, publishing to npm, creating release on GitHub) and deliver valuable info to package consumers.
It's pretty easy to set up with GitHub Actions.. you can see my recent commit for an example, though the GitHub Actions yml is a bit complex due to having multiple jobs, which you might just combine into one. The GITHUB_TOKEN is set automatically by GitHub. The NPM_TOKEN you need to generate with the npm cli and save it to your "Secrets" for this repo on GitHub.
First off, pretty cool component! Pretty much just what I was looking for and a bit more!
However I'm hesitant to bring in into my project because I'll be unable to review upgrades, since versions aren't tagged in GitHub & there's no changelog.
I strongly suggest getting set up with something like semantic-release to automate the release process (including updating version number according to semver, generating changelog, publishing to npm, creating release on GitHub) and deliver valuable info to package consumers.
It's pretty easy to set up with GitHub Actions.. you can see my recent commit for an example, though the GitHub Actions yml is a bit complex due to having multiple jobs, which you might just combine into one. The GITHUB_TOKEN is set automatically by GitHub. The NPM_TOKEN you need to generate with the npm cli and save it to your "Secrets" for this repo on GitHub.