Files
obsidian-mcp-server/.windsurf/rules/versioning-releases.md
Bill 08cc6e9ea6 Release v1.0.0 - Initial Release
🎉 Initial release of Obsidian MCP Server plugin

Core Features:
- MCP server implementation with HTTP transport
- JSON-RPC 2.0 message handling
- Protocol version 2024-11-05 support

MCP Tools:
- read_note, create_note, update_note, delete_note
- search_notes, list_notes, get_vault_info

Server Features:
- Configurable HTTP server (default port: 3000)
- Health check and MCP endpoints
- Auto-start option

Security:
- Origin header validation (DNS rebinding protection)
- Optional Bearer token authentication
- CORS configuration

UI:
- Settings panel with full configuration
- Status bar indicator and ribbon icon
- Start/Stop/Restart commands

Documentation:
- Comprehensive README with examples
- Quick Start Guide and Implementation Summary
- Test client script
2025-10-16 20:52:52 -04:00

938 B

trigger, description
trigger description
always_on Versioning and release process

Versioning & Releases

Version Management

  • Bump version in manifest.json using Semantic Versioning (SemVer)
  • Update versions.json to map plugin version → minimum app version
  • Keep version numbers consistent across all release artifacts

Release Process

  1. Create GitHub release with tag that exactly matches manifest.json's version
    • Do not use a leading v in the tag
  2. Attach required assets to the release:
    • manifest.json
    • main.js
    • styles.css (if present)
  3. After initial release, follow the process to add/update your plugin in the community catalog

Testing Before Release

Manual install for testing:

  1. Copy main.js, manifest.json, styles.css (if any) to:
    <Vault>/.obsidian/plugins/<plugin-id>/
    
  2. Reload Obsidian
  3. Enable the plugin in Settings → Community plugins