studio/element-call
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
31e59c1da15451201cf9864dccdc8896fd34f32f
element-call/renovate.json

50 lines
1.3 KiB
JSON
Raw Normal View History

Add renovate.json
2023-08-30 08:52:59 +00:00
{
"$schema": "https://docs.renovatebot.com/renovate-schema.json",
Migrate config renovate.json
2024-11-06 18:46:12 +00:00
"extends": ["config:recommended"],
Prettier
2023-08-30 14:42:58 +01:00
"packageRules": [
{
Fix Renovate warning Apparently Renovate doesn't really like it when you use a group: preset inside packageRules, instead of at the top level of the config. We do want to apply schedule:weekly only to the "all non-major dependencies" group though, so we need to write the group definition out by hand.
2024-08-01 16:41:19 -04:00
"groupName": "all non-major dependencies",
"groupSlug": "all-minor-patch",
"matchUpdateTypes": ["minor", "patch"],
"extends": ["schedule:weekly"]
Reduce noise coming from Renovate updates What I've tried to do here is to group most dependency updates together and put them on a weekly schedule. Some of our more sensitive dependencies such as LiveKit and Compound have been put into separate groups, so we still receive frequent updates for them.
2024-06-20 15:38:48 -04:00
},
Refine Renovate config further By getting it to pin GitHub Actions to specific commits, which hardens our workflows, and fixing a warning about matchPackageNames
2024-06-20 16:00:52 -04:00
{
"groupName": "GitHub Actions",
"matchDepTypes": ["action"],
"pinDigests": true,
"extends": ["schedule:monthly"]
},
Reduce noise coming from Renovate updates What I've tried to do here is to group most dependency updates together and put them on a weekly schedule. Some of our more sensitive dependencies such as LiveKit and Compound have been put into separate groups, so we still receive frequent updates for them.
2024-06-20 15:38:48 -04:00
{
"description": "Disable Renovate for packages we want to monitor ourselves",
"groupName": "manually updated packages",
Refine Renovate config further By getting it to pin GitHub Actions to specific commits, which hardens our workflows, and fixing a warning about matchPackageNames
2024-06-20 16:00:52 -04:00
"matchDepNames": ["matrix-js-sdk"],
Prettier
2023-08-30 14:42:58 +01:00
"enabled": false
Reduce noise coming from Renovate updates What I've tried to do here is to group most dependency updates together and put them on a weekly schedule. Some of our more sensitive dependencies such as LiveKit and Compound have been put into separate groups, so we still receive frequent updates for them.
2024-06-20 15:38:48 -04:00
},
{
"groupName": "matrix-widget-api",
Refine Renovate config further By getting it to pin GitHub Actions to specific commits, which hardens our workflows, and fixing a warning about matchPackageNames
2024-06-20 16:00:52 -04:00
"matchDepNames": ["matrix-widget-api"]
Reduce noise coming from Renovate updates What I've tried to do here is to group most dependency updates together and put them on a weekly schedule. Some of our more sensitive dependencies such as LiveKit and Compound have been put into separate groups, so we still receive frequent updates for them.
2024-06-20 15:38:48 -04:00
},
{
"groupName": "Compound",
Migrate config renovate.json
2024-11-06 18:46:12 +00:00
"schedule": "before 5am on Tuesday and Friday",
"matchPackageNames": ["@vector-im/compound-{/,}**"]
Reduce noise coming from Renovate updates What I've tried to do here is to group most dependency updates together and put them on a weekly schedule. Some of our more sensitive dependencies such as LiveKit and Compound have been put into separate groups, so we still receive frequent updates for them.
2024-06-20 15:38:48 -04:00
},
{
"groupName": "LiveKit client",
Refine Renovate config further By getting it to pin GitHub Actions to specific commits, which hardens our workflows, and fixing a warning about matchPackageNames
2024-06-20 16:00:52 -04:00
"matchDepNames": ["livekit-client"]
Reduce noise coming from Renovate updates What I've tried to do here is to group most dependency updates together and put them on a weekly schedule. Some of our more sensitive dependencies such as LiveKit and Compound have been put into separate groups, so we still receive frequent updates for them.
2024-06-20 15:38:48 -04:00
},
{
"groupName": "LiveKit components",
Migrate config renovate.json
2024-11-06 18:46:12 +00:00
"matchPackageNames": ["@livekit/components-{/,}**"]
Reduce noise coming from Renovate updates What I've tried to do here is to group most dependency updates together and put them on a weekly schedule. Some of our more sensitive dependencies such as LiveKit and Compound have been put into separate groups, so we still receive frequent updates for them.
2024-06-20 15:38:48 -04:00
},
{
"groupName": "Vaul",
Refine Renovate config further By getting it to pin GitHub Actions to specific commits, which hardens our workflows, and fixing a warning about matchPackageNames
2024-06-20 16:00:52 -04:00
"matchDepNames": ["vaul"],
Reduce noise coming from Renovate updates What I've tried to do here is to group most dependency updates together and put them on a weekly schedule. Some of our more sensitive dependencies such as LiveKit and Compound have been put into separate groups, so we still receive frequent updates for them.
2024-06-20 15:38:48 -04:00
"extends": ["schedule:monthly"],
"prHeader": "Please review modals on mobile for visual regressions."
Prettier
2023-08-30 14:42:58 +01:00
}
Ignore React Spectrum updates A couple different people (me and Dave) have tried and failed to find an easy way to upgrade these, and in the future we won't need these dependencies at all once the switch to Compound Web is finished, so let's not generate Renovate PRs for them.
2023-11-29 16:45:59 -05:00
],
Hold back PostHog updates for now https://github.com/PostHog/posthog-js/issues/1437
2024-09-27 16:02:12 -04:00
"semanticCommits": "disabled",
"ignoreDeps": ["posthog-js"]
Add renovate.json
2023-08-30 08:52:59 +00:00
}
Reference in New Issue Copy Permalink