Repository navigation
Prepare LaraFly 26.09.9 publication and verify public installs - #6
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
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.
Publish LaraFly as
fireflyframework/larafly, replacing all 29 legacyfirefly/*names. Packagist'sfireflyvendor namespace is already owned by another publisher. The bundled installer, skeleton, Lumen consumer and installation documentation now use the publishable root identity.Prepare version 26.09.9 and complete release delivery: validate on PHP 8.3–8.5, wait for Packagist to index the exact tagged commit, install it without custom repositories, exercise the installed application and installer, and create the GitHub release only after those checks pass. No split repositories or cross-repository token are needed. Export rules also keep local development dependencies out of copied path installations.
Validation:
composer check(3,807 passed, 6 skipped; Pint/PHPStan pass; Deptrac 0 violations), 75 browser tests, the opt-in create-project test, strict Composer validation, monorepo validation, strict documentation build, and the archive/copied-consumer gate. Independent review completed.First publication still requires one-time Packagist registration and webhook authorization; the release workflow intentionally refuses to publish if the exact tag is not installable there.