Repository navigation
feat: unified versioning via release-please - #142
Conversation
Normalize all plugin versions to 1.7.0 (the current repo version) and add release-please-config.json with glob-based extra-files to keep all plugin.json and marketplace.json versions in sync automatically. - Set all 15 plugin.json versions to 1.7.0 - Set all 15 marketplace.json plugin versions to 1.7.0 - Add missing pr-lifecycle entry to marketplace.json - Create release-please-config.json with: - Glob pattern for all plugin.json files - JSONPath wildcard for marketplace.json plugin versions Zero per-plugin config: adding a new plugin requires no release-please changes. The glob pattern automatically discovers new plugin.json files. (claude)
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request introduces a unified versioning system using release-please to manage and synchronize versions across all plugin.json and marketplace.json files. It simplifies the version management process and ensures consistency across the repository. Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on Gemini (@gemini-code-assist) comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request introduces a unified versioning strategy using release-please, which is a great improvement for managing versions across multiple plugins in this monorepo. The changes correctly normalize all existing plugin versions to 1.7.0 and add a configuration for release-please to automate future version bumps.
I've found a couple of issues that need to be addressed:
- The new
release-please-config.jsonis missing an entry to update the marketplace's top-levelmetadata.version, which will cause it to go out of sync. - The new
pr-lifecycleplugin entry inmarketplace.jsonis syntactically incorrect, causing the JSON to be invalid.
Once these issues are resolved, this will be a solid enhancement to the repository's release process.
There was a problem hiding this comment.
Pull request overview
This PR aligns all Claude Code plugin manifest versions with the repository release version (1.7.0) and introduces release-please configuration to keep these versions in sync automatically going forward.
Changes:
- Bump all plugin
.claude-plugin/plugin.jsonversions to1.7.0. - Update
.claude-plugin/marketplace.jsonplugin entry versions and add thepr-lifecycleplugin entry. - Add
release-please-config.jsonto automate version propagation into plugin manifests and marketplace entries.
Reviewed changes
Copilot reviewed 17 out of 17 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| session-analytics/.claude-plugin/plugin.json | Bumps plugin version to 1.7.0. |
| project-standards/.claude-plugin/plugin.json | Bumps plugin version to 1.7.0. |
| process-cleanup/.claude-plugin/plugin.json | Bumps plugin version to 1.7.0. |
| pr-lifecycle/.claude-plugin/plugin.json | Bumps plugin version to 1.7.0. |
| infra-standards/.claude-plugin/plugin.json | Bumps plugin version to 1.7.0. |
| infra-orchestration/.claude-plugin/plugin.json | Bumps plugin version to 1.7.0. |
| github-workflows/.claude-plugin/plugin.json | Bumps plugin version to 1.7.0. |
| git-workflows/.claude-plugin/plugin.json | Bumps plugin version to 1.7.0. |
| git-standards/.claude-plugin/plugin.json | Bumps plugin version to 1.7.0. |
| git-guards/.claude-plugin/plugin.json | Bumps plugin version to 1.7.0. |
| content-guards/.claude-plugin/plugin.json | Bumps plugin version to 1.7.0. |
| config-management/.claude-plugin/plugin.json | Bumps plugin version to 1.7.0. |
| codeql-resolver/.claude-plugin/plugin.json | Bumps plugin version to 1.7.0. |
| code-standards/.claude-plugin/plugin.json | Bumps plugin version to 1.7.0. |
| ai-delegation/.claude-plugin/plugin.json | Bumps plugin version to 1.7.0. |
| .claude-plugin/marketplace.json | Syncs marketplace plugin versions to 1.7.0 and adds pr-lifecycle. |
| release-please-config.json | Configures release-please to update plugin manifests and marketplace plugin entry versions. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
You can also share your feedback on Copilot code review. Take the survey.
Summary
1.7.0(current repo version)release-please-config.jsonwith glob-basedextra-filesfor automatic version syncpr-lifecycleentry to marketplace.jsonHow It Works
Zero per-plugin configuration. Release-please's
extra-filesuses:*/.claude-plugin/plugin.json— glob matches ALL plugin.json files$.plugins[*].version— JSONPath wildcard sets ALL marketplace entriesAdding a new plugin requires no release-please config changes. The glob automatically discovers new plugin.json files.
Context
Follows up on PR #138 feedback — replaces custom validation scripts with release-please's built-in version sync. This is the unified versioning approach used by major monorepos (React, Angular, Babel).
Test plan
1.7.0:for d in */; do [ -f "$d.claude-plugin/plugin.json" ] && jq -r '.version' "$d.claude-plugin/plugin.json"; done | sort -ujq -r '.plugins[].version' .claude-plugin/marketplace.json | sort -ujq empty release-please-config.json🤖 Generated with Claude Code