skills.rest
cjinhuo
cjinhuoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

release-publisher

Automate version bumping, GitHub release creation, and artifact retrieval for the blazwitcher Chrome extension.

101|14|Updated Jul 13, 2024
Search Tags:#automation#versioning#deployment#release#publish#chrome extension
One-click install
npx skills add https://github.com/cjinhuo/blazwitcher --skill release-publisher
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-publisher
Source: https://github.com/cjinhuo/blazwitcher/tree/main/.trae/skills/release-publisher
Command: npx skills add https://github.com/cjinhuo/blazwitcher --skill release-publisher

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the complex and time-consuming process of version bumping, releasing, and publishing your Chrome extension, ensuring a smooth and efficient deployment pipeline.

Core Features & Use Cases

  • Automated Versioning: Manages version increments using changeset.
  • Release Publishing: Handles pushing releases to GitHub and fetching release information.
  • Production Builds: Creates production-ready packages for deployment.
  • Use Case: When you're ready to release a new version of your Chrome extension, this Skill can automatically update the version number, create a new release tag on GitHub, and prepare the necessary build artifacts for publishing to the Chrome Web Store.

Quick Start

Use the release-publisher skill to perform a full release by running the command to bump the version, push the release, and fetch releases.

Frequently Asked Questions about release-publisher

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

FAQPage Schema
How do I automate version bumping for a Chrome extension release?▼

You can automate Chrome extension version bumping by orchestrating a multi-step deployment process using changeset versioning. This updates the version number and prepares the extension for a new release tag.

Does the Chrome extension release process require pnpm for script execution?▼

Yes, pnpm is required for script execution to automate the release pushing and artifact retrieval. Adherence to specific Git and environment variable configurations is also necessary.

What is the best way to publish a Chrome extension to GitHub and fetch release artifacts?▼

The best way to publish is to run a command that pushes the release to GitHub and fetches release information. This creates production-ready packages for Chrome Web Store deployment.

Can I use changeset to manage GitHub release creation for browser extensions?▼

Yes, you can use changeset to manage version increments which orchestrates the creation of a new release tag on GitHub and fetches the necessary build artifacts for publishing.

What environment variables are needed to push extension releases to GitHub?▼

Specific Git and environment variable configurations are required to push releases to GitHub and fetch release information, ensuring a smooth and efficient deployment pipeline for your extension.

Related Skills

Explore More Software Engineering Skills→
mikemikulamikemikula
2

docker-dev-setup

Configure Docker Compose with Postgres 17, Redis 8, and environment variables.

Community
Intermediate
mohamed-g-shoaibmohamed-g-shoaib

browser-extension-builder

Design, build, and publish Manifest V3 browser extensions for cross-browser stores.

Community
Intermediate
Aktoh-CyberAktoh-Cyber

github-release-management

Automate GitHub release orchestration across multiple repositories with semantic versioning.

Official
Advanced
SjdjdiejdrirhdkjejSjdjdiejdrirhdkjej

production-deployment-phase

Promote validated staging builds to production with semantic versioning and health checks.

Community
Advanced