npm-publish skill

Overview

This skill publishes @autumnsgrove/groveengine to the public npm registry while preserving GitHub Packages as the default registry for the repository. It implements a safe registry-swap workflow: switch to npm for publishing, build and publish, then switch the publishConfig back to GitHub Packages. Use it when releasing a new engine version to ensure correct registry, access, and commits.

How this skill works

The skill updates packages/engine/package.json to bump the version and temporarily replace publishConfig with the npm registry and public access. It runs the package build, executes npm publish --access public, then restores the publishConfig back to the GitHub Packages registry. Finally it commits the version bump and pushes the change to the remote to keep the repository consistent.

When to use it

• Releasing a new version of @autumnsgrove/groveengine to npm
• When a user requests: "publish to npm", "release to npm", or "bump and publish"
• After merging feature or bugfix changes that require a new package version
• When preparing a public package release while keeping GitHub Packages as default

Best practices

• Decide and verify the new semantic version (MAJOR.MINOR.PATCH) before editing package.json
• Always swap publishConfig to npm only for the publish step and then swap back immediately
• Build the package locally (pnpm run package) before running npm publish
• Verify npm auth token and 2FA bypass settings in npm config to avoid OTP errors
• Commit only the version and publishConfig change, and push to the main branch after publishing

Example use cases

• Minor feature release: bump MINOR, swap to npm, build, publish, swap back, commit and push
• Patch hotfix: bump PATCH, run build and publish to npm to make the fix available
• Major release with breaking changes: bump MAJOR and follow the same publish workflow
• Automated release script that edits packages/engine/package.json, publishes, and reverts publishConfig

FAQ