Repository navigation
Require nativephp/mobile-ui ^0.6 and list it in boost.json - #12
Merged
Merged
Conversation
New apps are created from main, so the ^0.3 constraint was installing mobile-ui 0.3.x even though 0.6 is out. Also fix the Theme class name in the published config comment. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
boost.json still named the old nativephp/native-ui package, so boost:install (which laravel new runs non-interactively) skipped mobile-ui's guidelines and skills. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
simonhamp
changed the title
simonhamp
marked this pull request as ready for review
September 30, 2026 12:01
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.
Bumps the mobile-ui constraint from ^0.3 to ^0.6.
laravel new app --using=nativephp/mobile-starterrunscomposer create-projectwith--stability=dev, so new apps are built from main rather than a tag. On 0.x a caret pins the minor, so every new app was getting mobile-ui 0.3.x even though 0.6.0 is out.With ^0.6 a fresh install resolves nativephp/mobile-ui 0.6.0 (with nativephp/mobile 4.5.2). The repo doesn't track a composer.lock, so there's no lock change.
The welcome screen only uses basic elements (column, row, text, image, icon, divider), none of which changed between 0.3 and 0.6, so the view needed nothing. The published config/native-ui.php still matches 0.6's keys. Its differences from the package default are the starter's own colors and fonts, which I left alone. I did fix one comment that pointed at the old
Nativephp\NativeUi\Themeclass name; it'sNative\Mobile\UI\Themenow.The test suite passes (8 tests, 81 assertions) and
php artisan native:validatepasses. It gives one warning, "Could not determine view name from render()" on Home.php, but that comes from nativephp/mobile's analyzer and isn't related to this change. I didn't run it on a device.It also fixes
boost.json, which still listed the oldnativephp/native-uipackage name.boost:install(whichlaravel newruns without prompting) only installs guidelines and skills for packages listed there, so mobile-ui's never reached new apps.🤖 Generated with Claude Code