Skip to content

Commit ec7b2d5

Browse files
yepzdkclaude
andcommitted
docs: add auto-release documentation and changelog
- Update README with auto-release workflow section - Update project structure to include new files - Create CHANGELOG.md with Keep a Changelog format Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
1 parent 2fec418 commit ec7b2d5

2 files changed

Lines changed: 69 additions & 1 deletion

File tree

CHANGELOG.md

Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
# Changelog
2+
3+
All notable changes to this project will be documented in this file.
4+
5+
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
6+
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
7+
8+
## [Unreleased]
9+
10+
### Added
11+
12+
- Auto-release workflow for MCP dependency updates
13+
- Weekly scheduled check for new MCP releases (Mondays 8:30 UTC)
14+
- Automated version bump and release creation when updates detected
15+
- Version tracking in `.claude-plugin/mcp-versions.json`
16+
17+
## [0.2.0] - 2025-01-24
18+
19+
### Added
20+
21+
- User-invocable skills for common workflows
22+
- `/itkdev-commit` - Create commits following ITK Dev guidelines
23+
- `/itkdev-pr` - Create pull requests with proper formatting
24+
- `/itkdev-changelog` - Update changelog entries
25+
26+
### Changed
27+
28+
- Renamed skills to use `itkdev` prefix for consistency
29+
30+
## [0.1.0] - 2025-01-23
31+
32+
### Added
33+
34+
- Initial plugin release
35+
- Browser feedback MCP server integration
36+
- GitHub guidelines skill for ITK Dev team workflows
37+
- Plugin marketplace structure
38+
39+
[Unreleased]: https://github.com/itk-dev/itkdev-claude-plugins/compare/v0.2.0...HEAD
40+
[0.2.0]: https://github.com/itk-dev/itkdev-claude-plugins/compare/v0.1.0...v0.2.0
41+
[0.1.0]: https://github.com/itk-dev/itkdev-claude-plugins/releases/tag/v0.1.0

README.md

Lines changed: 28 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,11 @@ A Claude Code plugin marketplace for ITK Dev team tools and MCP servers.
88
itkdev-claude-plugins/
99
├── .claude-plugin/
1010
│ ├── plugin.json # Plugin manifest
11-
│ └── marketplace.json # Marketplace catalog
11+
│ ├── marketplace.json # Marketplace catalog
12+
│ └── mcp-versions.json # Tracked MCP dependency versions
13+
├── .github/workflows/ # GitHub Actions workflows
14+
│ ├── check-mcp-updates.yml # Weekly MCP update checker
15+
│ └── release.yml # Automated release workflow
1216
├── .mcp.json # MCP server configurations
1317
├── commands/ # Slash commands (Markdown files)
1418
│ └── example.md
@@ -45,6 +49,29 @@ GitHub workflow guidelines for the ITK Dev team. Automatically activates when wo
4549
- Changelog updates (Keep a Changelog format)
4650
- PR requirements and templates
4751

52+
## Auto-Release Workflow
53+
54+
This plugin automatically releases new versions when MCP server dependencies publish updates.
55+
56+
### How it works
57+
58+
1. **Weekly Check**: A GitHub Actions workflow runs every Monday at 8:30 UTC
59+
2. **Version Comparison**: Compares latest MCP releases with tracked versions in `.claude-plugin/mcp-versions.json`
60+
3. **Automated Release**: If updates are detected, a new patch version is released automatically
61+
62+
### Tracked Dependencies
63+
64+
| MCP Server | Repository |
65+
|------------|------------|
66+
| browser-feedback | [mcp-claude-code-browser-feedback](https://github.com/itk-dev/mcp-claude-code-browser-feedback) |
67+
| docker | [mcp-itkdev-docker](https://github.com/itk-dev/mcp-itkdev-docker) |
68+
69+
### Manual Trigger
70+
71+
You can manually trigger a dependency check via the GitHub Actions UI:
72+
1. Go to **Actions** > **Check MCP Updates**
73+
2. Click **Run workflow**
74+
4875
## Adding New Tools
4976

5077
### Adding MCP Servers

0 commit comments

Comments
 (0)