Skip to content

Update renovate/renovate Docker tag to v34 - autoclosed

Stackspin-renovate Bot requested to merge renovate/renovate-renovate-34-x into main

This MR contains the following updates:

Package Type Update Change
renovate/renovate image major 33.2.4 -> 34.8.0

Release Notes

renovatebot/renovate

v34.8.0

Features

v34.7.1

Bug Fixes

v34.7.0

Features

v34.6.2

Bug Fixes
  • manager/gradle: ignore mapScalar() method from Apollo Kotlin plugin (#​18625) (0dfc98c)
Documentation

v34.6.1

Build System

v34.6.0

Features

v34.5.0

Features

v34.4.0

Features

v34.3.0

Features
Miscellaneous Chores
Documentation
Continuous Integration

v34.2.3

Bug Fixes

v34.2.2

Bug Fixes
  • manager/gradle: preserve next token for parsing in case dependency interpolation fails (#​18330) (8279be4)

v34.2.1

Bug Fixes
  • manager/dockerfile: improve RegEx to match ARG values with trailing spaces (#​18592) (4770c00)
Continuous Integration
Miscellaneous Chores
Documentation

v34.2.0

Features
Documentation
Miscellaneous Chores

v34.1.5

Bug Fixes
Build System

v34.1.4

Build System
Miscellaneous Chores

v34.1.3

Bug Fixes
Miscellaneous Chores
Documentation
Code Refactoring

v34.1.2

Bug Fixes

v34.1.1

Bug Fixes
Miscellaneous Chores

v34.1.0

Features
Code Refactoring
Miscellaneous Chores

v34.0.0

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 MRs 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)
Bug Fixes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this MR and you won't be reminded about this update again.


  • If you want to rebase/retry this MR, click this checkbox.

This MR has been generated by Renovate Bot.

Edited by Stackspin-renovate Bot

Merge request reports

Loading