manual-versioning - Workflow Failing preventing new releases #297
Description
About a month ago I tried to run the manual-versioning workflow to release the various bumps to depdendcies used by this plugin so that adopters could take advantage of them and also setup some sort of monthly cadence for this process. Sadly the workflow failed with the following error: "GitPushError: Failed to push branch (main) to remote". Details in this run: https://github.com/backstage/mkdocs-techdocs-core/actions/runs/17110783786/job/48531428656
I reached out to @nickhudkins for some help and he kindly shared the following on Discord:
Ah ha! It's trying to push directly to main and main has branch protection. Since I don't have repo admin permissions, I'll write up what needs to happen
There's a variety of ways to handle this with varying degrees of security posture. The most "correct" way to handle this is to create a GitHub app that has appropriate permissions, and generate a short lived token while we do the release.
The "quick fix" here is to take your personal access tokens and give them the ability to override branch protections.
https://gonzalohirsch.com/blog/semantic-release-and-branch-protection-rules/ is a good article about all the steps required. Happy to do this for y'all, though I suspect I'll need to go through the whole CNCF membership etc...
Since then @theobch has submitted a PR to do a manual release in #289.
I'd very much like to get the automated process working and would like to use this issue as a way for us to settle on a fix and track the work to implement it.