12 Commits

Author SHA1 Message Date
92f5e1c33a ci: upgrade to Node.js 20 for native globalThis.crypto support 2025-12-16 14:27:11 -05:00
Bill Ballou
b0fc0be629 chore: add Buy Me A Coffee funding link 2025-11-01 11:01:40 -04:00
f4fab2593f fix: allow prerelease tags (alpha/beta/rc) in deployment workflow
Modified version validation to support testing with prerelease tags:
- Prerelease tags (e.g., 1.1.0-alpha.1) now validate base version against package.json/manifest.json
- Production tags still require exact version match
- Supports -alpha.N, -beta.N, and -rc.N tag formats

This enables deployment testing with alpha releases while maintaining
strict version control for production releases.
2025-10-30 11:19:12 -04:00
cc4e71f920 refactor: remove 'obsidian' from plugin ID and update branding
- Change plugin ID from 'obsidian-mcp-server' to 'mcp-server'
- Remove 'Obsidian' from plugin description per guidelines
- Update documentation to use new plugin folder name
- Update installation paths to .obsidian/plugins/mcp-server/
- Update package name to match new plugin ID
- Simplify README title and description
2025-10-26 16:47:36 -04:00
87d04ee834 fix: remove jq dependency from Gitea release step
Use grep and sed instead of jq to parse JSON response, as jq
is not available on all Gitea runners.
2025-10-26 13:52:40 -04:00
9adc81705f fix: use Gitea API directly instead of action reference
Replace the gitea-release-action with direct API calls using curl.
This approach works on both GitHub (which runs this step conditionally)
and Gitea servers, using their compatible REST APIs.
2025-10-26 13:32:52 -04:00
79c4af55d5 feat: add Gitea support to release workflow
Add platform detection to support creating releases on both GitHub
and Gitea servers. The workflow now:
- Detects the platform using github.server_url
- Uses GitHub CLI (gh) for GitHub releases
- Uses gitea-release-action for Gitea releases
- Creates draft releases with the same artifacts on both platforms
2025-10-26 13:08:55 -04:00
dd4976e218 fix: support pre-release version tags in release workflow
Add support for semantic version tags with pre-release identifiers
(e.g., 1.0.0-alpha.1, 1.0.0-beta.2) in the GitHub Actions release
workflow.

The workflow now triggers on both stable versions (X.Y.Z) and
pre-release versions (X.Y.Z-*).

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-26 12:55:59 -04:00
d2a76ee6f4 fix: use heredoc for release notes to avoid YAML parsing issues 2025-10-26 12:07:24 -04:00
ed8729d766 docs: add GitHub Sponsors funding option
- Added GitHub Sponsors configuration file to enable sponsorship button
- Updated README to include GitHub Sponsors link alongside existing donation options
- Configured sponsorship to direct to Xe138's GitHub profile
2025-10-26 12:05:50 -04:00
d0c2731816 fix: add release notes template to draft releases 2025-10-26 11:53:34 -04:00
b7cf858c1c feat: add GitHub Actions release workflow
Implements automated release workflow per design document.

- Triggers on semantic version tags (e.g., 1.2.3)
- Validates version consistency across package.json, manifest.json, and git tag
- Runs test suite (blocks release if tests fail)
- Builds plugin using production build process
- Verifies build artifacts exist (main.js, manifest.json, styles.css)
- Creates draft GitHub release with required files

Workflow uses single-job architecture for simplicity and runs on Node.js 18 with npm caching for performance.
2025-10-26 11:50:37 -04:00