docs: installability sweep — vcs install step, accurate ePHPm version, doc-drift fixes - #4
Merged
Merged
Conversation
- The ephpm_db_* SAPI functions shipped in the v0.6.3 release (current: v0.8.6) — drop the three 'requires unreleased ePHPm / build from main' claims. - The bare 'composer require' fails for anyone who hasn't added this repo as a Composer vcs repository (ePHPm packages are not on Packagist by design) — document the repositories step.
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.
Part of the org-wide installability sweep: corrects stale 'requires unreleased ePHPm' claims (natives shipped in v0.6.3; current v0.8.6), adds the Composer vcs-repositories install step (packages are not on Packagist), and fixes doc drift verified against source. A cold containerized install via the documented commands was verified end-to-end. Tags (v0.1.0/v0.1.1) were pushed at pre-branch main; cut a follow-up tag after merge if the fixed docs should live inside a tag.