tracking reverting breaking changes before new emergency release

[ramonpetgrave64]

tracking revert PRs before the next emergency release

[ramonpetgrave64]

getting some errors when trying to revert some PRs

[ramonpetgrave64]

last release was at v1.9.0 07e64b6

[kpk47]

Can we just create a new release branch from the last release date and apply the sigstore fix to that? We won't have the chore releases since then, but we'll at least have the sigstore fix.

[ramonpetgrave64]

@kpk sounds good, we can bramch from
07e64b6
and then apply the fixes from
#3355

But I think there may be an adversarial test for releasing from a non-main branch.

[laurentsimon]

If we revert:

#3313 (I'll send a PR)
Need to update the CHANGELOG for Hayden's PR
example-package revert the v3->v4 action

I'm more confident doing this in the main branch than in a different branch. The e2e tests don't work on different branch. There's just one PR left to revert #3313

[kpk47]

Okay, sounds good. Let's go with your plan.

I've got a release branch together already, so we've got that in case we need it for some reason.