Repository navigation
Use the separately versioned shared core dependency - #2
Merged
Merged
Conversation
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.
Use the public tagged
mybbresources/mybb-toolingComposer dependency and remove tracked shared-library snapshots. The installed CLI checks the separate core package, while the installer bootstraps core, CLI, and repository as separate signed owners. Portable PHARs remain self-contained.Validation: Composer resolves v0.1.0 from public GitHub and records its immutable source commit; both CLI entrypoints run from their standalone checkouts. The core's 78-test suite and nine supported-host CI jobs passed. CI also verifies the installed Composer core and absence of tracked snapshots.