Pun Butrach

> Whats the state of this PR? This PR should be *ready* (aside from fixing conflicts) But I'm waiting on review because this is a really big changes.

@PalmDevs if would like to change some strings, now would be a perfect time to do so.

String updated to matched with edc8ef4f4449b250018632a4322bdcaac8ebe9e7

> Is this still the case? Not sure, I can't reproduce this problem now on 1.19.0-dev.17 version.

Also would it be possible to publish the release as ReVanced Bot?

Also by the way @BenjaminHalko can you please look into the PopScope changes? See * #1645

Fyi, whenever semantic release has created a tag, **force push is discouraged**.

Docs and CI check are done now, will moving on to code check after PR have been merged. * #1663 * #1662

> Yeah, a token can be created for this for the bot Can get started on doing that, is there any organisation secret that I could use here.

> @validcube Here is a secret named REPOSITORY_PUSH_ACCESS Hm, the secret appear to be empty, could you verify that it's correctly set? https://github.com/ReVanced/revanced-manager/actions/runs/8135888633/job/22231203031