netscript-release

Automate NetScript release cuts and GitHub publishing with Deno and GitHub Actions.

Updated Jun 4, 2026
One-click install
npx skills add https://github.com/rickylabs/netscript --skill netscript-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: netscript-release
Source: https://github.com/rickylabs/netscript/tree/main/.agents/skills/netscript-release
Command: npx skills add https://github.com/rickylabs/netscript --skill netscript-release

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of cutting releases, interpreting release gates, publishing through GitHub, and verifying the release flow for NetScript services.

Core Features & Use Cases

  • Release Cutting: Execute the release:cut command to automate the release-cut process.
  • GitHub Publishing: Publishes through GitHub Release/OIDC, ensuring all steps are automated.
  • End-to-End Verification: Verifies a race-free e2e-cli-prod, ensuring the release is stable.
  • Rollback & Retry: Provides rollback and retry mechanisms for failed cuts.

Quick Start

Run the release cut command with the desired version: deno task release:cut -- <version>

Frequently Asked Questions about netscript-release

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

FAQPage Schema
How do I automate release cuts and GitHub publishing for NetScript services?

Automating release cuts and GitHub publishing for NetScript services involves executing the `release:cut` command via Deno, which manages version bumps, preflight validations, and OIDC publishing to GitHub Releases automatically.

Do I need Deno and GitHub Actions to run the NetScript release automation workflow?

Yes, you need Deno and GitHub Actions configured in your environment to execute the NetScript release automation workflow, as it relies on these platforms to manage version bumps and publish through GitHub Release/OIDC.

What preflight validations are checked during a NetScript release cut?

During a NetScript release cut, preflight validations manage version bumps and perform residue checks to ensure codebase stability before publishing through GitHub Release/OIDC.

Does the NetScript release workflow verify production readiness after publishing?

Yes, the NetScript release workflow verifies production readiness by executing a race-free end-to-end CLI production check to ensure the published release remains stable and functional.

Can I rollback or retry a failed NetScript release cut?

Yes, you can rollback or retry a failed NetScript release cut using the built-in rollback and retry mechanisms provided by the release automation workflow to recover from publishing errors.

What is the best way to handle GitHub OIDC publishing for NetScript CI/CD pipelines?

Handling GitHub OIDC publishing for NetScript CI/CD pipelines is best managed by running the `deno task release:cut` command, which automates version bumps, residue checks, and secure OIDC authentication for GitHub Releases.