skills.rest
TingRuDeng
TingRuDengCOMMUNITY
Explore all skills by this author →
GitHub

package-release

Automates versioning and release preparation for ForgeFlow npm packages.

2|1|Updated Apr 3, 2026
Search Tags:#automation#versioning#npm#release#ci-cd#forgeflow
One-click install
npx skills add https://github.com/TingRuDeng/forgeflow-platform --skill package-release-tingrudeng
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: package-release
Source: https://github.com/TingRuDeng/forgeflow-platform/tree/main/skills/package-release
Command: npx skills add https://github.com/TingRuDeng/forgeflow-platform --skill package-release-tingrudeng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill eliminates the risk of manual errors and accidental registry writes during the npm package release process by providing a standardized, dry-run-first workflow for version bumping and release preparation.

Core Features & Use Cases

  • Safe Previewing: Perform dry-run simulations to verify version changes and command execution before applying any modifications.
  • Automated Preparation: Update package manifests for pull requests while maintaining strict adherence to branch protection and CI/CD release triggers.
  • Use Case: When a developer needs to release a new beta version of a runtime package, they use this skill to preview the bump, prepare the version PR, and ensure the subsequent GitHub workflow handles the formal publication and provenance recording.

Quick Start

Use the package-release skill to preview a prerelease version bump for the trae-beta-runtime package.

Frequently Asked Questions about package-release

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

FAQPage Schema
How do I safely preview an npm package version bump before publishing?▼

To safely preview an npm package version bump, you can perform a dry-run simulation that verifies version changes and command execution without applying modifications or writing to the registry.

How do I automate npm release preparation for protected branches?▼

Automate npm release preparation by updating package manifests for pull requests while maintaining strict adherence to branch protection rules and CI/CD release triggers.

Does this npm release workflow support secure artifact publishing via OIDC provenance?▼

Yes, the npm release workflow supports secure artifact publishing by integrating with automated GitHub release workflows that handle formal publication and OIDC provenance recording.

What is the best way to prepare a beta runtime package release without manual registry errors?▼

The best way to prepare a beta runtime package release without manual errors is using a standardized, dry-run-first workflow to preview the bump and prepare the version pull request.

Can I use this to bump prerelease versions for specific runtime packages?▼

Yes, you can use this to bump prerelease versions for specific runtime packages by targeting the package and previewing the version bump before opening the pull request.

Why does my automated version bump require a pull request instead of direct publishing?▼

Automated version bumps require a pull request to ensure protected branch compliance, allowing the subsequent GitHub workflow to handle the formal publication securely.

Related Skills

Explore More Software Engineering Skills→
Trystan-SATrystan-SA
4

postkit-release

Bump the version, create a GitHub Release, and publish postkit to npm.

Community
Advanced
pr-pmpr-pm
121

npm-trusted-publishing

Configure GitHub Actions OIDC trusted publishing for npm packages.

Community
Intermediate
AnveioAnveio
1

task-pull-request

Automate GitHub pull request creation, reviews, feedback, and merges via gh CLI.

Community
Intermediate
spartDevspartDev
6

Release Automation

Automate SEMVER version bumps, changelog generation, and release pull requests.

Community
Advanced