Repository navigation
Release client v1.0.0 with verified Packagist installation - #2
Merged
Merged
Conversation
Llewellynvdm
marked this pull request as ready for review
September 24, 2026 10:40
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.
Why
The client is registered on Packagist, but users need a stable version, clear installation instructions, and verification of the actual public distribution.
Changes
^1.0, AI stdio setup, and a complete PHP SDK example.release.json. A reviewed manifest version change merged to main starts the tested release workflow automatically.Release behavior
Merging this PR declares and starts publication of v1.0.0. Publication remains gated on testing the merged commit. Existing tags are never moved. API/authentication errors fail closed, and interrupted publication can recover on the same tested commit. Optional manual dispatch remains available.
Pinned server revisions:
14c715c50c2cc29fd3c8cc3c4780442efb507398993522852770e2f8968ab066deedef00f174d8c7Validation
aa960899aa6de8e197ad8c8531538bb356df252d:25fa5150e8287710573a0670070752f27a88d6f4.Published release evidence
legacyProtocolHeaderRequests: 0.Install the stable package:
composer require 'joomengine/mcp-client:^1.0'Consumer reports, package provenance and logs are retained as workflow artifacts.