Teach release logic to ignore certain upgrades #205

Open
opened 2021-07-12 09:30:56 +00:00 by decentral1se · 0 comments
Owner

Following coop-cloud/nextcloud#7 and 8dfad23470, this maybe stops the renovate bot running the config upgrade but when we run abra nextcloud release it will not read the renovate.json file. We probably want to add some sort of ignore pattern to abra.sh so it can skip upgrades that are known to be sketchy? This is a pretty half baked plan right now...

Following https://git.autonomic.zone/coop-cloud/nextcloud/issues/7 and https://git.autonomic.zone/coop-cloud/nextcloud/commit/8dfad23470694e04b5e97f36257992cfec1fc434, this maybe stops the renovate bot running the config upgrade but when we run `abra nextcloud release` it will not read the `renovate.json` file. We probably want to add some sort of ignore pattern to `abra.sh` so it can skip upgrades that are known to be sketchy? This is a pretty half baked plan right now...
decentral1se added this to the Beta release milestone 2021-07-12 09:30:56 +00:00
decentral1se added the
enhancement
label 2021-07-12 09:30:56 +00:00
This repo is archived. You cannot comment on issues.
No Milestone
No Assignees
1 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/abra#205
No description provided.