No longer including the release automation in the initial release process, will instead revise documentation once this issue is completed.

Moving to review as I will be opening a PR but marking it as do not merge. @michael-valdron will be working on a fix for the previous release to registry-operator where a squash merge occurred whereas we need the entire git history. Once that is done this issue should be good to mark as complete and merge.

This issue is currently blocked as it requires changes to the git history of the release branches for registry operator. Currently there is squash commits in the release branches which conflict with the automation as the bot cannot handle merge conflicts without human intervention, which defeats the purpose of the automation. This is occurring because the releases are based off of main but in the release branches it has diverged from main in the git history with these squash commits. In order to prevent this from happening and to allow this issue to become unblocked the git history needs to be altered in the release branches so that it does not diverge from main.

release-v0: https://github.com/devfile/registry-operator/commits/release-v0/
main: https://github.com/devfile/registry-operator/commits/main/

This issue is currently blocked as it requires changes to the git history of the release branches for registry operator. Currently there is squash commits in the release branches which conflict with the automation as the bot cannot handle merge conflicts without human intervention, which defeats the purpose of the automation. This is occurring because the releases are based off of main but in the release branches it has diverged from main in the git history with these squash commits. In order to prevent this from happening and to allow this issue to become unblocked the git history needs to be altered in the release branches so that it does not diverge from main.

@Jdubrick I have talked with @thepetk while discussing the #1605 approach that I think this process should be altered to align with other devfile repos by only using the release branches to backport patches to target major and minor releases which I believe mirrors #1516 you created back in April. The epic #1518 should be completed before this issue can be unblocked.

This issue is stale because it has been open for 90 days with no activity. Remove stale label or comment or this will be closed in 60 days.

This should be kept open to complete automation for a quicker release process for our team to perform, suggest devtools-week tag be added to this one.