npm-publish

Swaps registry to npm for publishing, then reverts to avoid conflicts.

Updated Nov 30, 2025

Search Tags:#npm #publish #version-bump #github-packages #registry-swaps #build-and-publish

Ready to run

npx skills add https://github.com/AutumnsGrove/GroveScout --skill npm-publish-autumnsgrove

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: npm-publish
Source: https://github.com/AutumnsGrove/GroveScout/tree/main/.claude/skills/npm-publish
Command: npx skills add https://github.com/AutumnsGrove/GroveScout --skill npm-publish-autumnsgrove

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Publish GroveEngine to npm with a safe registry swap workflow, preventing accidental publishes to the wrong registry and ensuring the correct version is released.

Core Features & Use Cases

Regulated registry swaps: switch from GitHub Packages to npm, publish, then revert to GitHub Packages automatically, avoiding misconfigurations.
Version bump and publish automation: update package.json version, run build, publish to npm, verify success, and push changes.
Use Case: releasing GroveEngine updates to npm for users while keeping internal registry integrity intact.

Quick Start

Run the npm publish workflow to bump the version, swap registries, build, publish, swap back, and push changes.

Frequently Asked Questions about npm-publish

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I publish a package to npm without breaking my default GitHub Packages registry?▼

This registry swap workflow updates package.json, modifies publishConfig to target npm, builds the package, publishes, and reverts the registry back to GitHub Packages automatically.

What is the safest way to automate a version bump and npm publish in CI?▼

Automating version bumps and npm publishing ensures the correct version is released while preserving your default registry configuration, avoiding manual errors during CI or local release workflows.

Can I use this npm publish workflow for local releases or is it only for CI environments?▼

The workflow enforces updating package.json, modifying publishConfig, building, publishing to npm, and pushing changes, ensuring a safe release process in any environment.

Why does my npm publish keep failing when switching from GitHub Packages?▼

By enforcing a strict sequence of updating package.json, swapping registries, building, and publishing, this approach prevents accidental publishes to the wrong registry and ensures the correct version is released.

How to swap npm registries during a release and restore the original config?▼

This automated swap process prevents accidental publishes to the wrong registry by ensuring the original configuration is preserved after the version bump and publish tasks complete successfully.