Commit the pinned skeleton: Flarum v2.0.0-rc.5 (#2, step 2) - #4
Merged
Conversation
Resolved by the resolve-lock workflow on PHP 8.3 with the image's own extension set, and audited clean. Flarum core and its bundled extensions land on v2.0.0-rc.5; fof/horizon and fof/redis on v2.0.0-beta.9; fof/upload on 2.0.0-beta.6. The lock is the pin. composer.json keeps loose constraints because that is what flarum/flarum ships, but composer install from a committed lock installs the recorded versions and ignores them. Filed under skeleton/ rather than the repository root so it cannot be mistaken for this repo's own manifest — nothing here is a PHP project. Worth recording: there is no stable Flarum 2.0. minimum-stability: beta is currently required to install 2.0 at all, so the pin targets an explicit release candidate and tightens when 2.0 ships. Nothing consumes these yet. The Dockerfile still builds an image that resolves at first boot; baking the skeleton in is the next 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.
Second step of #2. Resolved by the
Resolve skeleton lockworkflow on PHP 8.3 with the image's own extension set, and audited clean.v2.0.0-rc.5fof/horizon,fof/redisv2.0.0-beta.9fof/upload2.0.0-beta.6The lock is the pin.
composer.jsonkeeps loose constraints because that is whatflarum/flarumships, butcomposer installfrom a committed lock installs the recorded versions and ignores them.Filed under
skeleton/rather than the repo root so it cannot be mistaken for this repository's own manifest — nothing here is a PHP project.Worth recording for #2: there is no stable Flarum 2.0.
minimum-stability: betais currently required to install 2.0 at all, so the pin targets an explicit RC and can tighten when 2.0 ships. The issue's "pin stable if it's out" doesn't apply yet.Nothing consumes these yet — the Dockerfile still builds an image that resolves at first boot. Baking the skeleton in and seeding the volume from it is the next step, and that's the one that changes runtime behaviour.