Publishing Skill for @adeze/raindrop-mcp
Use this workflow for all standard releases in this repository.
Source of Truth
- Release command:
bun run release - Release config:
.releaserc.json - CI trigger:
.github/workflows/ci.ymlon push tomaster
Standard Release Flow
- Merge Conventional Commit-based changes to
master. - CI runs lint, type-check, tests, and build.
- CI release job runs
semantic-release. semantic-releasecomputes version, updatesCHANGELOG.md, tags release, publishes npm, and creates a GitHub Release.- Release prepare step syncs
manifest.jsonand buildsraindrop-mcp.mcpbso the bundle is attached to the GitHub Release.
Required Secrets
GITHUB_TOKEN: provided by GitHub Actions.
Publishing Authentication
- npm publish uses GitHub Actions OIDC trusted publishing.
- No long-lived npm token is required for the standard CI release path.
Local Verification Before Merge
bun run lint
bun run type-check
bun run test
bun run build
Conventional Commit Examples
fix: handle missing collection id in bulk editfeat: add includeArchived filter to bookmark_searchfeat!: remove deprecated query parameter
Rules
- Do not manually bump package versions for standard releases.
- Do not manually create release tags for standard releases.
- Do not run manual npm publish commands for standard releases.
- Keep release behavior in
.releaserc.jsonand CI workflow aligned.
Converted and distributed by TomeVault — claim your Tome and manage your conversions.