Enable Updates via Magisk #37
Merged
Conversation
This file contains 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
creates updater.json File in Release
|
Very nice! This is exactly what I was thinking about implementing. Thanks. |
This was referenced Aug 11, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR enables the Magisk Update Property to allow updating of the Module directly from Magisk. See Magisk Documentation for module.prop.
The build CI will generate an updater.json file to be released alonside the zip File. The module.prop points to the latest released updater.json. The updater.json points to the specific current release to allow downloading the updated Module.zip from there.
This is similar to #31, but it doesnt need to commit to the repo from the build pipeline, instead uses the release for the updater.json
Cheers, JM-Lemmi