Fails to learn from

When starting work on a new major version (redesign, bigger change), keep the currently published version on the main branch and start a next branch for the upcoming changes. Developing the upcoming changes on main and use the release/vX branch seems like a good idea, but it's not. For one, the sites in netlify have to be rerouted to fit the above workflow (and then reverted once next becomes stable), also the release process automation is not intended to work in this way. Keep main on the currently published version until you're ready to deploy the next major. Until then, implement breaking changes on a next branch.