releasing-popkorn

Guide maintainers through publishing @popkorn/* packages to npm via changesets.

19|Updated Jul 8, 2026
One-click install
npx skills add https://github.com/ayarse/popkorn --skill releasing-popkorn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: releasing-popkorn
Source: https://github.com/ayarse/popkorn/tree/main/.claude/skills/releasing-popkorn
Command: npx skills add https://github.com/ayarse/popkorn --skill releasing-popkorn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents incorrect or broken npm releases by explaining the repository's changesets-based publishing workflow and preserving the Bun-specific packaging logic required for valid published tarballs.

Core Features & Use Cases

  • Changesets Release Workflow: Guides maintainers through creating changesets, merging the release pull request, and allowing the GitHub workflow to publish packages.
  • Publish Shim Preservation: Explains why scripts/publish.ts must rewrite workspace dependencies and apply dist-based publish configuration before npm publishing.
  • Use Case: When preparing a new @popkorn/* release, use this Skill to avoid manually running the release command, deleting the publish shim, or producing uninstallable packages.

Quick Start

Use the releasing-popkorn skill to prepare and publish the next @popkorn/* npm release through the approved changesets workflow.

Frequently Asked Questions about releasing-popkorn

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

FAQPage Schema
How do I publish @popkorn packages to npm using changesets without breaking workspace dependencies?

To publish @popkorn packages, create changesets, merge the Version Packages pull request, and let GitHub Actions handle the npm publishing to preserve workspace dependency version rewriting and dist-oriented publish configuration.

Why does the publish shim rewrite workspace dependencies before npm publishing?

The publish shim rewrites workspace dependencies and applies dist-based publish configuration before npm publishing to ensure published tarballs remain installable while development manifests continue targeting source files.

Can I manually run the release command to publish @popkorn packages instead of using the changesets workflow?

Manually running the release command bypasses the changesets release process and risks producing uninstallable packages; the approved workflow requires creating changesets and merging the release pull request to trigger GitHub Actions publishing.

Does the @popkorn npm publishing workflow work with Bun-based package manifests?

The @popkorn npm publishing workflow supports Bun-based package manifests by preserving dist-oriented publish configuration and workspace dependency version rewriting during the changesets release process.

What happens if I delete the publish shim before publishing @popkorn packages to npm?

Deleting the publish shim before publishing @popkorn packages to npm removes the logic that rewrites workspace dependencies and applies dist-based publish configuration, resulting in uninstallable published tarballs.