Mobile v3 docs: simplify NATIVEPHP_APP_VERSION guidance#378
Merged
Conversation
…SION - Remove NATIVEPHP_APP_VERSION/_CODE from the pre-install .env block; they default to DEBUG and aren't required up front. - Reframe the configuration page section: lead with what these vars actually are (public version string vs. internal build number, with iOS/Android mappings), note DEBUG is the default, and point at `native:release`. Move the bundled-Laravel extraction mechanics into an aside. - Update the deployment Releasing section to drive readers to `native:release` instead of editing .env by hand, recommend semver for version numbers, and clarify that the build number is auto-incremented and persisted by the command. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Summary
Reworks the mobile v3 docs to better explain
NATIVEPHP_APP_VERSION/NATIVEPHP_APP_VERSION_CODEand to lean on thenative:releasecommand rather than hand-editing.env.NATIVEPHP_APP_VERSION/_CODEfrom the pre-install.envblock. They default toDEBUGand won't be required in the next release.NATIVEPHP_APP_VERSIONsection to lead with what the vars actually are: public version string (CFBundleShortVersionString/versionName) vs. internal build number (CFBundleVersion/versionCode). HighlightDEBUGas the default and point atnative:releasefor release builds. The "how NativePHP unpacks the bundled Laravel app on boot" mechanics move into an aside..envsnippet under Releasing with thenative:releasecommand, recommend semver for version numbers, and clarify that the build number is auto-incremented and persisted back to.envby the command.Test plan
#nativereleaseanchor on/docs/mobile/3/getting-started/commandsresolves (slug for### native:release).commands#nativereleasefrom configuration.md and deployment.md.