revanced-manager
revanced-manager copied to clipboard
chore: Merge `dev` to `main`
Fixes #1325, closes #1629, fixes #530
Also would it be possible to publish the release as ReVanced Bot?
Yeah, a token can be created for this for the 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.
Force pushing should be avoided regardless. It is not a huge problem, though, even with semantic release. Once you force push, semantic-release will not attempt to regenerate a new commit/tag, as long as the commits and tags are preserved. The issue that occurred here is caused by the force push deleting a commit generated by semantic release, without deleting the tag, so semantic release attempts to regenerate the commit and the tag and fails because it exists already
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
@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
@validcube Try now
This release, will completely obliterate the changelog.
OH WE'RE PUSHING NOW, REAL MEN TEST IN PRODUCTION
If you merge, you're going to find your pet hidden in a funny hole at a random north korea graveyard
If you merge, you're going to find your pet hidden in a funny hole at a random north korea graveyard
Not the cat :(
I don't have enough experience with flutter UI to solve the ongoing UI issues caused by longer strings, I'll merge this for now to get the important fixes in and assign someone else to it