obsidian-deploy-integration

name	obsidian-deploy-integration
description	Publish Obsidian plugins to the community plugin directory. Use when releasing your first plugin, updating existing plugins, or managing the community plugin submission process. Trigger with phrases like "publish obsidian plugin", "obsidian community plugins", "submit obsidian plugin", "obsidian plugin directory".
allowed-tools	Read, Write, Edit, Bash(git:*), Bash(gh:*)
version	1.13.0
license	MIT
author	Jeremy Longshore <[e-mail]>
tags	["saas","obsidian","obsidian-deploy"]
compatibility	Designed for Claude Code, also compatible with Codex and OpenClaw

Obsidian Plugin Deploy Integration

Overview

Release and distribute Obsidian plugins through multiple channels: the official community plugin directory, GitHub releases, BRAT beta testing, and manual installation. Covers the full lifecycle from building release assets to submitting your PR to the obsidian-releases repo.

Prerequisites

• Obsidian plugin with main.ts, manifest.json, and styles.css (if applicable)
• GitHub repository for your plugin (public)
• gh CLI authenticated (gh auth status)
• Plugin passes obsidian-prod-checklist validation

Instructions

Step 1: Build Release Assets

set -euo pipefail
# Clean build for production
rm -f main.js
npm ci
npm run build

# Verify the three release files exist
for f in main.js manifest.json; do
  test -f "$f" || { echo "MISSING: $f"; exit 1; }
done
test -f styles.css && echo "styles.css included" || echo "No styles.css (OK if no custom styles)"

echo "Release assets ready"

Step 2: Version Bump with version-bump.mjs

// version-bump.mjs
import { readFileSync, writeFileSync } from 'fs';

const targetVersion = process.env.npm_package_version;

// Sync manifest.json
const manifest = .((, ));
 { minAppVersion } = manifest;
manifest. = targetVersion;
(, .(manifest, , ));


 versions = .((, ));
versions[targetVersion] = minAppVersion;
(, .(versions, , ));

.();