ScheduleMigration is not applied to automergeSchedule config #33823
Unanswered
mpihelgas
asked this question in
Request Help
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
How are you running Renovate?
Self-hosted Renovate
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
Renovate version 39.106.0 with Bitbucket
Please tell us more about your question or problem
I have Renovate running once every hour for my projects. After configuring similar schedules for both branch & PR creation (
schedule
) and automerge (automergeSchedule
), I observed that even though automerges were enabled they were never in schedule according to debug logs.Following the documentation and examples from
schedule
page and the claim thatautomergeSchedule
supports the same syntax asschedule
, I created the following config.After having a closer look into Debug logs I discovered that during startup Renovate logs
Config migration necessary
. When observing the differences in the new config we see that theschedule
field is migrated to a more logically correct format["after 8pm", "before 4am"]
while theautomergeSchedule
stays at the logically impossible["after 8pm and before 4am"]
.I was able to work around the issue by adding the migrated syntax for
automergeSchedule
already into the config. However, I reckon thatScheduleMigration
should also apply for theautomergeSchedule
field values since the documentation claims that the syntax is handled identically.Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions