well, inotia tags those builds as beta himself in CLI. even though patches get successful.youarefinished wrote:Rockmods wrote:Patch 4.7.1: feat(YouTube): add support versions 19.03.36 ~ 19.16.39
Any Higher Version than 19.16.39 Patched with this Patch will turn As Beta (even if the used Base YT APK is stable release from google) because the Patches are not compatible for that Version. So stable Tag is Correct ?
Stable tag is correct as patches are always stable, you can`t build with an incompatible patch, as well as the YouTube build is also stable and not beta so nothing is wrong in this.
Mods made from a different branch other then main branch would be called experimental or something similar.
Also, the extended branch is not the main. Main is revanced. Rvx is fork. Rex is fork of rvx. Patches are stable for a particular version and will be called stable. Dev patches are out to build experimental Builds. Also Higher versions patched by current patches also comes under experimental build.
RVX Manager itself states the same that it can lead to unexpected issues. (Versions are found showing bugs even though all patches were successful), because all patches are made by the developer with the fingerprint of specific version or versions. higher version have different fingerprints.