Automated Publishing
Automated Publishing
Section titled “Automated Publishing”Rhyolite automates npm publishing so you can focus on building, not manual releases.
How It Works
Section titled “How It Works”- Versioning: Bump your package version in
package.json. - Tagging: Push a git tag (e.g.,
v1.2.3). - CI/CD: The publish workflow runs on new tags, builds the package, and publishes to npm using a secure token.
Steps to Publish
Section titled “Steps to Publish”- Update your package version:
Terminal window pnpm version patch # or minor/majorgit push --follow-tags - CI/CD will publish to npm automatically.
Security
Section titled “Security”- The npm token is stored as a GitHub Actions secret (
NPM_TOKEN). - Only trusted maintainers have publish rights.
Troubleshooting
Section titled “Troubleshooting”- Check the Actions tab for publish errors.
- Ensure your package is public and has a valid
nameandversion.
For more, see CI/CD Best Practices.