mariadb 10.6 config not compatible with latest Nextcloud #7
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The latest tag has a new version of mariadb which makes this error fail installation on a new deployment:
Looks like we need to configure something.
Rolling back to 10.5 works for now 🤦
FYI @3wordchant the bot is now automatically doing merges for upgrades and releases without question (haven't had time to refine it yet) so this happened
89eb579618
. There are ways of tweaking this process which we can discuss soon.Yeah I've been meaning to ask about the workflow. It seems if I run
abra recipe .. release
locally then the bot will make dupe commits? Anyway, is there a way to stop auto-updating MariaDB temporarily on this repo til we have chance to see what's up with this issue? 🤔The bot won't make a dupe commit, it just runs
recipe ... release
as you would, so the logic is just the same? If it sees that there is a new tag, then it makes that release, but if it sees that we're on latest, nothing is done.It seems like we can use ignoreDeps something like
{"ignoreDeps": ["mariadb"]}
but then I dont know if we want to configure it from Renovate side? Perhaps we could add an additional file whichrecipe ... release
would read and if it finds a match, it will ignore this release?I guess we need to map out the existing automation and see what is working and what isn't. Handiest way to stop this now is comment it out from https://git.autonomic.zone/autonomic-cooperative/renovate-bot/src/branch/main/config.js.tmpl and then redeploy renovate with https://git.autonomic.zone/autonomic-cooperative/renovate-bot#deploy.
Maybe
8dfad23470
fixes it for now? Opened up coop-cloud/abra#205 also.Hmmm we did see #10 (comment) but I think that doesn't confirm that
8dfad23470
really works but for now, this is solved. coop-cloud/abra#205 will address the larger issue in the release logic, will close for now.