Open svc-secops opened 1 year ago
@svc-secops why are we pinning these dependencies?
This will cause much more maintenance burden on this repo, and noise for new releases.
The Types packages in particular don’t make sense to pin.
If you want to set up CI so releases happen automatically, then I would withdraw my objection, but since this currently would make more manual work for me, I’m not convinced.
This PR contains the following updates:
7.x
->7.26.0
14.x
->14.5.0
23.x
->23.3.14
10.x
->10.17.60
6.5.x
->6.5.3
16.2.x
->16.2.3
0.17.x
->0.17.2
5.0.x
->5.0.0
3.x
->3.8.3
6.x
->6.1.13
7.x
->7.7.3
14.x
->14.7.0
2.2.x
->2.2.1
23.x
->23.6.0
2.x
->2.1.2
3.6.x
->3.6.0
8.1.x
->8.1.7
4.17.x
->4.17.21
1.2.x
->1.2.2
1.15.x
->1.15.3
6.6.x
->6.6.1
2.6.x
->2.6.3
1.0.x
->1.0.7
0.4.x
->0.4.2
2.1.x
->2.1.0
23.10.x
->23.10.5
3.x
->3.9.10
3.4.x
->3.4.10
Add the preset
:preserveSemverRanges
to your config if you don't want to pin your dependencies.Configuration
📅 Schedule: Branch creation - "after 10pm every weekday,before 5am every weekday" in timezone America/Los_Angeles, Automerge - "after 8am and before 4pm on tuesday" in timezone America/Los_Angeles.
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.