chore(ci): remove validate-plugin workflow#192
Merged
Conversation
The validate-plugin workflow gated PRs on plugin.json/pyproject.toml version parity, but the release process only bumps pyproject.toml, which means every release PR fails this check. Rather than wire the plugin.json bump into the release flow, drop the workflow. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Removes
.github/workflows/validate-plugin.yml.Why
The workflow gated PRs on
plugins/conductor/.claude-plugin/plugin.jsonandpyproject.tomlhaving the sameversionfield. The release process (see #191) only bumpspyproject.toml, so every release PR — and every push to main from a release merge — fails this check.Recent failures:
chore: release 0.1.16 (#191)on mainchore: release 0.1.16PRRather than wire a second version bump into the release flow, drop the workflow. The other JSON validity / SKILL.md path checks in this workflow are low-value (the files are stable and human-edited rarely).