Replies: 1 comment
-
|
Let's wait and see if there's more demand for such feature. To me it looks a bit unusual. I think most of the people would just set 2 weeks for everything. If you want to avoid frequent updates to your dependencies, you can use exact versions for the direct dependencies. You can also use company-wide version catalogs. These can even be shared via config dependencies |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
My organization would like to set the
minimumReleaseAgeto 6 months for most packages. For key packages likereactornxwe would like to bypass theminimumReleaseAgesetting of 6 months. Instead, we would like to set a second level of protection 1 hour or 2 weeks for all packages.Implementation details don't really matter to us, but the effect would be something like this:
I did find #9985 but this requires much more maintenance for this scenario than my proposal.
Beta Was this translation helpful? Give feedback.
All reactions