chore: Merge branch dev to main
#1
Draft
Conversation
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
Removed unnecessary files, including files that appear to have been accidentally copied from official ReVanced. * dummy/: It was a remnant from v19 patches. In patcher v21, dummy is called "stub". * extensions/shared/: Removed classes for non-existent patches. e.g. SpoofVideoStreams * extensions/twitter/stub/: Removed unused stubs. * extensions/twitter/library/: library dir only exists in "shared" on official ReVanced. * patches/stub/: At this time, there are no patches in piko that require stubs. It is unlikely that stubs will be needed in the future. * patches.json: This was removed from the official ReVanced at some point. It won't be updated unless you bring back the Json generator, so removed. I removed "EmojiCompat" from Twitter stub, but I'm not sure if it is needed. If it is needed, please tell me.
Fix minSdk to 26 (Android 8.0) as the X app is minSdk 26 Remove unused dependencies from ReVanced Match to official ReVanced Fix "About" information of patches (There is no contact for piko, so I replaced it with the sample one from the revenanced-patches-template.)
Without this fix, CI will break. Changed the semantic release configurations to find new .rvp files. Reflected the changes in the official ReVanced repo.
My understanding is that piko doesn't use these patches because piko adds resources and settings in piko's own way. So I judged these were accidentally copied from the official ReVanced. Am I doing the right thing?
My understanding is that piko doesn't use these patches. If you copied this for future use, please let me know so I can revert it. However, in my opinion, it's better to copy these when they are actually needed for piko. Copying them now will make it burdensome to reflect changes in the official ReVanced.
…Removed extendWith extendWith is done in sharedExtensionPatch
The default value of `use` is true. Both ReVanced and RVX omit `use` if it is `true`.
All fingerprints are now internal or private. In the official ReVanced, all fingerprints are internal, but in piko, many patches and fingerprint are in the same file, so I made it private as much as possible
Patches that other patches depend on (patches without names) do not need compatibleWith.
In ReVanced Manager, these patches were treated as universal patches and were not applied.
Also, removed it from unnecessary files.
* Fix the patch structure. (Make it a single resource patch.) * Fix the issue that Japanese arrays.xml is not modified. * Introduce region comments. This is often used in the official ReVanced project. TODO: Logs are printed (not fixed in this commit)
The old information was remained in README.md. Added temporary information that the latest ReVanced Manager is supported now. TODO: Screenshot of Manager is not updated yet!
Do not change this version manually. By use the breaking change format in commit message, CI will change the major version automatically. Also, use the commit types that triggers CI, such as "feat:".
Other improvements include: * Reduced subdomains by using wildcards (For each domain specified in the patch option, one wildcard version will also be added to the intent filter.) * Fixed pathPrefix from `/.*` to `/..*` in order to prevent the app from opening the custom domain's homepage such as `https://vxtwitter.com/` * Fixed missing period in patch description * Fixed redundant wording in patch description
Some fixes for v21
## [2.0.0-dev.2](crimera/piko@v2.0.0-dev.1...v2.0.0-dev.2) (2025-09-27) ### Bug Fixes * **Twitter:** Fix remove ads on replies ([8fda05e](crimera@8fda05e)) * **Universal:** Set version code as int ([ee83df7](crimera@ee83df7)) ### Refactors * **Twitter:** potential fix for resource compilation failing in manager ([fa0dfac](crimera@fa0dfac))
Migration v21: Added back `Custom sharing domains`
Some more fixes for v21
## [2.0.0-dev.3](crimera/piko@v2.0.0-dev.2...v2.0.0-dev.3) (2025-10-04) ### Refactors * **Twitter:** Correct ja strings replacement in BBT patch ([ee200a5](crimera@ee200a5)) * **Twitter:** fix `Remove promoted trends` ([0e1d4ed](crimera@0e1d4ed)) * **Twitter:** handle piko resources programmatically ([3cc0f07](crimera@3cc0f07)) * **Twitter:** refactor `Bring back twitter` patch ([f24cb72](crimera@f24cb72)) * **Twitter:** remove old comments ([1655283](crimera@1655283))
Removed pull_request trigger for main and dev branches.
Turkish loc update
Turkish loc update
## [2.0.0-dev.4](crimera/piko@v2.0.0-dev.3...v2.0.0-dev.4) (2025-10-08) ### Updates * **Translations:** Update `Polish` ([43da4b5](crimera@43da4b5))
Add Traditional Chinese (zh-rHK)
Update Traditional Chinese (zh-rHK)
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 pull request will
devtomain.