소스 정보
- 저장소
- adeze/raindrop-mcp
- 최근 소스 활동
- 2026년 3월 10일 00:55
- 감지된 SKILL.md 언어
- 영어
- 스타
- 188
- 포크
- 29
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- name
- publishing
- description
- Publishing and release workflow with semantic-release and GitHub Actions
# 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.yml` on push to `master`
## Standard Release Flow
1. Merge Conventional Commit-based changes to `master`.
2. CI runs lint, type-check, tests, and build.
3. CI release job runs `semantic-release`.
4. `semantic-release` computes version, updates `CHANGELOG.md`, tags release, publishes npm, and creates a GitHub Release.
5. Release prepare step syncs `manifest.json` and builds `raindrop-mcp.mcpb` so 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
```bash
bun run lint
bun run type-check
bun run test
bun run build
```
## Conventional Commit Examples
- `fix: handle missing collection id in bulk edit`
- `feat: add includeArchived filter to bookmark_search`
- `feat!: 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.json` and CI workflow aligned.
GitHub에서 보기