Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
chore(release): 1.5.0-dev.9 [skip ci]
# [1.5.0-dev.9](v1.5.0-dev.8...v1.5.0-dev.9) (2024-03-27) ### Bug Fixes * Check index of pattern in string instead of the other way around ([e3ba343](e3ba343)) * **YouTube - Hide layout components:** Correctly hide Join button ([b945e2f](b945e2f)) * **YouTube - Hide Shorts components:** Correctly hide join button ([b7a8995](b7a8995)) * **YouTube:** Fix video playback by switching to ReVanced GmsCore vendor ([#589](#589)) ([3a34a23](3a34a23)) ### Features * **YouTube - Hide layout components:** Filter home/search results by keywords ([#584](#584)) ([0222a4a](0222a4a)) * **YouTube - Hide Shorts components:** Hide like and dislike buttons ([2a08e5a](2a08e5a)) * **YouTube - Hide Shorts components:** Hide sound metadata label ([46d8ef6](46d8ef6)) * **YouTube - Hide Shorts components:** Hide title and full video link label ([59165de](59165de))
- Loading branch information
bc52fad
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@oSumAtrIX
It refuses to create a new release.
Build log shows:
[9:48:28 AM] [semantic-release] › ℹ The local branch dev is behind the remote one, therefore a new version won't be published.
How to fix this?
bc52fad
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As per explanation on the semantic-release website, such an issue can occur if we wrongly force push or if a release fails for any reason. In such an event, both the failed release tag and the commit have to be deleted via a force push in order to fix the issue. Force pushing to delete the old commit is not necessary but it would get rid of duplicate c(invalid) commits.