Skip to content

chore: Merge branch dev to main#178

Draft
github-actions[bot] wants to merge 31 commits into
mainfrom
dev
Draft

chore: Merge branch dev to main#178
github-actions[bot] wants to merge 31 commits into
mainfrom
dev

Conversation

@github-actions

Copy link
Copy Markdown

This pull request will Merge branch dev to main.

prateek-who and others added 12 commits June 15, 2026 13:30
Moved our temp apk from tmp folder in our morphe-data folder to the temp
folder used when patching. `--purge` should now properly clean up this
file.
## [1.9.2-dev.1](v1.9.1...v1.9.2-dev.1) (2026-06-15)

### Bug Fixes

* CLI --purge command does not cleanup temp APK ([#169](#169)) ([6163e9c](6163e9c))
…atch sources + block play store updates for patched apps (#176)

- Settings is now split into Settings and Tools for better UX.
- New "Your Apps" section: every GUI patch is recorded (app, version,
patches + sources/versions, date, integrity) in the shared engine store.
This allows for easy updating of apps and also getting notified about
app updates on startup.
- Copied over the keystore converter from the manager. Now users can
drop any keystore and we should be able to convert it to BKS and use it
properly.
- Patch sources can now be reordered either by dragging them or using 
the arrow keys. (Order only affects display order + the app-label tiebreak. 
It does not change which patches load first).
- ADB installs now set a non-play installer source so the play store won't 
try to auto-update the patched apps. Auto-picks a popular store that isn't 
installed on the device. Always on (no toggle).

!Important: "Your apps" section update requires the user to reinstall
the app since we need to collect a bunch of info when an app gets
installed.

---------

Co-authored-by: LisoUseInAIKyrios <118716522+LisoUseInAIKyrios@users.noreply.github.com>
# [1.10.0-dev.1](v1.9.2-dev.1...v1.10.0-dev.1) (2026-06-15)

### Features

* "your apps" section + settings and tools split + re-orderable patch sources + block play store updates for patched apps ([#176](#176)) ([d865abd](d865abd))
…ction's cards (#179)

- Route a patched app's web links to it instead of the browser or the
stock/default app.
- Added an "Uninstall" button to the Your Apps section's cards. Allows
for better tracking of an app. (The GUI still tracks and says "Not on
this device" if an app was uninstalled outside.)
- Added `--route-links` and `--disable-stock <packageName>` flag to 
utility install for the cli. This will route links through our patched app and 
also stop stock app from opening those links respectively.
# [1.10.0-dev.2](v1.10.0-dev.1...v1.10.0-dev.2) (2026-06-23)

### Features

* route links through patched app + uninstall from "Your Apps" section's cards ([#179](#179)) ([1626ce5](1626ce5))
…el colors, improve patch loading errors (#180)

- The engine only merged `.apkm` bundles; `.xapk`/`.apks` were handed to
the patcher unmerged and crashed with a null-manifest NPE. Fixed now.

- Older-stable, older-dev, and latest-dev all rendered as yellow/amber.
That impossible to tell apart. Now four distinct colors (
  green = stable latest,
  amber = stable older,
  blue = dev latest,
  red = dev older
)

- Better patch load errors thrown.
# [1.10.0-dev.3](v1.10.0-dev.2...v1.10.0-dev.3) (2026-06-23)

### Bug Fixes

* Handle GUI patching xapk / apks, add distinct patch-source channel colors, improve patch loading errors ([#180](#180)) ([d8245f0](d8245f0))
…parate class loader for multiple patch bundles (#187)
# [1.10.0-dev.4](v1.10.0-dev.3...v1.10.0-dev.4) (2026-06-27)

### Features

* Array GUI patches alphabetically, improve error logging, use separate class loader for multiple patch bundles ([#187](#187)) ([755909c](755909c))
…ed version (#185)

On startup, the gui automatically gets the latest version of dev/stable
if available based on user's previous choice and shifts to it. An older
version is pinned only if the user had previously pinned an older
version.

!Important: Existing sources are moved onto the latest of their channel.
Anyone who had deliberately pinned an older version will be bumped to
latest. Users will need to re-pin for now.
@prateek-who prateek-who linked an issue Jun 28, 2026 that may be closed by this pull request
2 tasks
semantic-release-bot and others added 4 commits June 28, 2026 10:45
# [1.10.0-dev.5](v1.10.0-dev.4...v1.10.0-dev.5) (2026-06-28)

### Features

* Patch sources follows latest (stable/dev) instead of to last used version ([#185](#185)) ([5d34993](5d34993))
# [1.10.0-dev.6](v1.10.0-dev.5...v1.10.0-dev.6) (2026-06-29)

### Bug Fixes

* Update to latest patcher ([2c89128](2c89128))
krvstek and others added 2 commits June 29, 2026 17:17
…ersions` (#189)

Closes #171.

Adds `-x` / `--include-experimental` to both `list-patches` and
`list-versions`. Without it, the output is identical to before.

The old `compatiblePackages` API has no concept of experimental
versions, everything gets flattened. The new `compatibility` API has an
`isExperimental` flag per version target, so we now use that as the
source of truth, with a fallback to the legacy field for older patch
bundles. The filtering/rendering logic lives in a new
`PatchExtensions.kt` in `app.morphe.engine` to keep it out of the
command classes.

**`list-patches -p -v -x`** now shows experimental versions under
"Compatible versions" and labels universal patches as `(universal)`
instead of silently dropping them. **`list-versions -x`** now counts
experimental versions in the frequency table:

```
$ java -jar cli.jar list-versions --patches=patches.mpp -x
Package name: com.google.android.youtube
Most common compatible versions:
        21.25.523 (70 patches)
        21.24.360 (70 patches)
        ...
```
# [1.10.0-dev.7](v1.10.0-dev.6...v1.10.0-dev.7) (2026-06-29)

### Features

* Add `--include-experimental` flag to `list-patches` and `list-versions` ([#189](#189)) ([8ef916c](8ef916c))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment