Release Management FAQs

Question 1

When should I use this skill?

Accepted Answer

You should activate this skill whenever you are ready to publish a new version of your plugin, need to bump version numbers (Major, Minor, or Patch), or want to ensure your local project state matches your GitHub release tags.

Question 2

How does this skill improve the Obsidian development workflow?

Accepted Answer

It eliminates manual errors by ensuring version numbers are identical across all required files. It also streamlines the tedious process of bundling main.js, manifest.json, and styles.css for GitHub releases while maintaining a structured history of changes.

Question 3

Can this skill help with release troubleshooting?

Accepted Answer

Yes. The skill includes built-in workflows for conflict resolution, such as deleting and recreating mismatched tags or releases, and ensuring the working directory is clean before a deployment begins.

Question 4

What does the Release Management skill do?

Accepted Answer

This skill automates the end-to-end release process for Obsidian plugins. It synchronizes versions across package.json, manifest.json, and versions.json, maintains the CHANGELOG.md, and orchestrates the GitHub release process including asset bundling.

Question 5

Why does this skill use manual releases instead of GitHub Actions?

Accepted Answer

This skill is designed for developers who prefer manual control over release notes and asset verification. By using the 'gh' CLI instead of automated CI/CD workflows, it prevents conflicts and allows for highly customized deployment notes.

Release Management

Release Management

Key Features

Use Cases

Key Features

Use Cases