You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently our standard setup for dependabot automerge is configure as following:
update change - merge into devDependencies and (prod-) dependencies
minor change - merge into devDependencies but NOT into (prod-) dependencies
major change - do NOT merge at all
As discussion at telegramm (near https://t.me/ioBroker_development/31787) shows that almost all dependencies are configured using '^m.b.u' syntax. This way any minor update is installed at user systems whenever a new minor version exists and is used by at least one npm package. So ist does not realy seem to provide any benefit to require the devs to manually trigger such merges at adapetr directory.
SUGGESTION:
merge update and minor changes for devDependencies and (prod-)dependencies automatically (if tests succeed)
do nor merge major changes automatically (= no change)
Please review / discuss.I can provide a PR ich change is accepted. Feel free to assign to me.
The text was updated successfully, but these errors were encountered:
While I agree, I really want to avoid ~a.b.c versions getting auto-updated to a different minor version without the dev being involved, as preventing this is the sole reason for the ~ specifier. If we can avoid this, go for it.
Absoliutly my oppinion too.
If ~cannot be expluded from automatic merge, we should leave it as it is.
I'll check as soon as I have time :-(
mcm1957
changed the title
Dependabot automerge - autmatically merge minor changes too
Dependabot automerge - aut0matically merge minor changes too
Oct 10, 2023
mcm1957
changed the title
Dependabot automerge - aut0matically merge minor changes too
Dependabot automerge - automatically merge minor changes too
Oct 10, 2023
Currently our standard setup for dependabot automerge is configure as following:
update change - merge into devDependencies and (prod-) dependencies
minor change - merge into devDependencies but NOT into (prod-) dependencies
major change - do NOT merge at all
As discussion at telegramm (near https://t.me/ioBroker_development/31787) shows that almost all dependencies are configured using '^m.b.u' syntax. This way any minor update is installed at user systems whenever a new minor version exists and is used by at least one npm package. So ist does not realy seem to provide any benefit to require the devs to manually trigger such merges at adapetr directory.
SUGGESTION:
merge update and minor changes for devDependencies and (prod-)dependencies automatically (if tests succeed)
do nor merge major changes automatically (= no change)
Please review / discuss.I can provide a PR ich change is accepted. Feel free to assign to me.
The text was updated successfully, but these errors were encountered: