b884c83980
This commit refactors the entire release process to be simpler, more robust, and less error-prone. The previous complex system of manual version calculation, artifact passing, and dry-run flags has been replaced with a more streamlined, two-stage process driven by distinct GitHub Actions workflows. The new process separates tag creation from the release engine. A new `create-internal-release.yml` workflow is introduced to handle the creation and iteration of internal build tags (e.g., `v1.2.3-internal.1`, `v1.2.3-internal.2`). The main `release.yml` workflow is now triggered solely by the presence of a new version tag. Key changes include: - The `release.yml` workflow no longer takes `dry_run` or `pr_number` inputs, as tag creation is now handled separately. - Version code is now consistently calculated once per build based on Git history and an offset, removing the complex logic for handling hotfixes and reusing version codes via artifacts. - Builds only occur if a release for the given `BASE_TAG` doesn't already exist on the same commit. This makes the process idempotent for promotions. - A new `prepare-release-environment` job intelligently handles superseded releases by deleting old releases and tags if a new tag for the same base version points to a different commit. - The build process is split into separate jobs for Google Play (`release-google`) and F-Droid (`release-fdroid`), allowing them to run in parallel. - Build attestations are now generated for all artifacts to improve supply chain security. - The `create-internal-release.yml` workflow is simplified to only require a `base_version`, automatically calculating the next internal iteration number. It no longer handles complex version bumping logic (`major`, `minor`, `patch`, `hotfix`). - Fastlane scripts have been cleaned up to remove now-unused lanes (`get_internal_track_version_code`). - The `RELEASE_PROCESS.md` documentation has been completely rewritten to reflect the new, simpler workflow. BREAKING CHANGE: The release workflow has been fundamentally changed. - The `release.yml` workflow is no longer triggered with `workflow_dispatch` inputs like `dry_run`. Releases are now initiated by pushing a correctly formatted tag. - The `create-internal-release.yml` workflow has been changed. It no longer supports `release_type` (`auto`, `patch`, etc.) and instead requires a specific `base_version` to create an internal build tag for. - Hotfix handling via special tags like `-hotfix` is removed. Superseding a release is now handled by creating a new internal iteration for the same base version from a newer commit. Signed-off-by: James Rich <2199651+jamesarich@users.noreply.github.com> |
||
|---|---|---|
| .github | ||
| .idea | ||
| app | ||
| build-logic | ||
| config | ||
| core | ||
| fastlane | ||
| feature | ||
| gradle | ||
| mesh_service_example | ||
| .gitignore | ||
| .gitmodules | ||
| .ruby-version | ||
| AGENT.md | ||
| CONTRIBUTING.md | ||
| Gemfile | ||
| Gemfile.lock | ||
| LICENSE | ||
| README.md | ||
| RELEASE_PROCESS.md | ||
| build.gradle.kts | ||
| codecov.yml | ||
| compose_compiler_config.conf | ||
| config.properties | ||
| crowdin.yml | ||
| debugging-android.md | ||
| gradle.properties | ||
| gradlew | ||
| gradlew.bat | ||
| secrets.defaults.properties | ||
| settings.gradle.kts | ||
README.md
Meshtastic-Android
This is a tool for using Android with open-source mesh radios. For more information see our webpage: meshtastic.org. If you are looking for the the device side code, see here.
This project is currently beta testing across various providers. If you have questions or feedback please Join our discussion forum or the Discord Group . We would love to hear from you!
Get Meshtastic
The easiest, and fastest way to get the latest beta releases is to use our github releases. It is recommend to use these with Obtainum to get the latest updates.
Alternatively, these other providers are also available, but may be slower to update.
![Download at https://play.google.com/store/apps/details?id=com.geeksville.mesh]](https://play.google.com/intl/en_us/badges/static/images/badges/en_badge_web_generic.png){kind=icon}
The play store is the last to update of these options, but if you want to join the Play Store testing program go to this URL and opt-in to become a tester. If you encounter any problems or have questions, ask us on the discord, create an issue, or post in the forum and we'll help as we can.
Documentation
The project's documentation is generated with Dokka and hosted on GitHub Pages. It is automatically updated on every push to the main branch.
Generating Locally
You can generate the documentation locally to preview your changes.
- Run the Dokka task:
./gradlew :app:dokkaHtml - View the output:
The generated HTML files will be located in the
app/build/dokka/htmldirectory. You can open theindex.htmlfile in your browser to view the documentation.
Translations
You can help translate the app into your native language using Crowdin.
Building the Android App
https://meshtastic.org/docs/development/android/
Note: when building the google flavor locally you will need to supply your own Google Maps Android SDK api key MAPS_API_KEY in local.properties in order to use Google Maps.
e.g.
MAPS_API_KEY=your_google_maps_api_key_here
Contributing guidelines
For detailed instructions on how to contribute, please see our CONTRIBUTING.md file. For details on our release process, see the RELEASE_PROCESS.md file.
Repository Statistics
Copyright 2025, Meshtastic LLC. GPL-3.0 license