34.0.0 (2022-10-25)
Here comes v34 hot on the heels of v33. We decided to issue another breaking change to revert one of the breaking changes in v33.
If you are upgrading from v32 to v34 then it means that the setting for branchNameStrict remains as false and you don't need to worry about that.
If you already upgraded from v32 to v33 then you have a decision to make first: should you set branchNameStrict to true (like in v33), or let it set back to false (like in v32).
Strict branch naming meant that all special characters other than letters, numbers and hyphens were converted to hyphens and then deduplicated, e.g. a branch which in v32 was like renovate/abc.def-2.x would become renovate/abc-def-2-x in v33. If you prefer to revert back to the old way then that will happen automatically in v34. If you prefer to keep the way in v33 because you already had a bunch of PRs closed and reopened due to branch names, and don't want to do that again, then add branchNameStrict: false to your bot config or your shared config before updating to v34.
Apologies to anyone negatively affected by this v33 change.
⚠ BREAKING CHANGES
- revert branchNameStrict to false (#18536)