release-process

Automate Obsidian Gemini plugin release workflows from notes to GitHub releases.

515|64|Updated Oct 23, 2024

Search Tags:#automation #versioning #npm #github #plugin #release

Ready to run

npx skills add https://github.com/allenhutchison/obsidian-gemini --skill release-process-allenhutchison

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release-process
Source: https://github.com/allenhutchison/obsidian-gemini/tree/main/.agents/skills/release-process
Command: npx skills add https://github.com/allenhutchison/obsidian-gemini --skill release-process-allenhutchison

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Full release workflow automation for Obsidian Gemini: updating release notes, running checks, bumping the version with npm, creating a GitHub release, and verifying the release.

Core Features & Use Cases

Update the release notes at src/release-notes.json to reflect the new version, ensuring the changelog stays in sync with the codebase.
Run tests and build to guarantee production readiness before publishing.
Commit release notes, bump the version with npm, and generate a GitHub release that contains the new build artifacts.
Verify the release in GitHub and ensure the tag, artifacts, and documentation align with the new version.

Quick Start

Run the release-process skill to prepare the next plugin release and publish it to GitHub.

Frequently Asked Questions about release-process

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

FAQPage Schema

How do I automate a plugin release workflow on GitHub from start to finish?▼

A GitHub release workflow automates coordinating release notes, version bumps, tests, and publishing. It updates your changelog, runs build checks, commits notes, bumps the version with npm, creates the GitHub release, and verifies the final tag and artifacts.

How do I keep release notes in sync with npm version bumps during deployment?▼

To keep release notes in sync, update the changelog file before running the npm version bump. The workflow commits the updated notes, executes the version increment, and packages the new build artifacts together in the GitHub release to ensure consistency.

Does the release process run tests before creating a GitHub release?▼

Yes, the release process runs tests and builds the project to guarantee production readiness before publishing. This validation step ensures the GitHub release contains verified artifacts, preventing broken builds from being shipped to users.

Can I use this automated release workflow for any npm plugin?▼

This workflow specifically applies to Obsidian Gemini plugin releases. While it uses npm for versioning and GitHub for publishing, the automated steps target the Obsidian Gemini repository structure, including its specific release notes format and build verification.

What is the best way to verify a GitHub release after publishing a plugin?▼

The best way to verify a GitHub release is to check that the tag, build artifacts, and documentation align with the new version. The workflow implements a verification step to confirm the published release outcome matches the bumped version and committed notes.