Fix release ZIP build (composer require --update-no-dev) + manual trigger - #24
Merged
Conversation
…ual trigger The MCP-adapter bundling step (added in #23) used `composer require … --no-dev`, but `composer require` has no `--no-dev` flag (that is `composer install`'s) — the correct flag is `--update-no-dev`. The v1.3.3 release build failed at that step before creating the tag/release. Also add a `workflow_dispatch` trigger so a release can be re-run manually without a version bump.
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
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.
The MCP-adapter bundling step added in #23 used
composer require … --no-dev, butcomposer requirehas no--no-devoption — that belongs tocomposer install. The correct flag is--update-no-dev. The v1.3.3 release build failed at that step, before the tag/release was created (so no v1.3.3 tag or release exists).--no-dev→--update-no-dev.workflow_dispatchtrigger so a release can be re-run manually (used here to release v1.3.3 without a redundant version bump).CI-only change; no plugin code or version change.