Dependency Dashboard #17127
Comments
|
Thank you for submitting your first issue, awesome! 🚀 We're thrilled to receive your input. If you haven't completed the template yet, please take a moment to do so. This ensures that we fully understand your feature request or bug report. On what happens next, see the docs. If you like Orchard Core, please star our repo and join our community channels. |
|
Hmm, interesting that we have this, I thought it would just update the dependencies. I guess this can be useful. Since my understanding is that with the current config this merely presents an overview with an option to issue updates right away (instead of waiting for the schedule), but otherwise it doesn't require us to approve each update separately here too, I wouldn't disable it. So, looks good. I'll try some low-risk updates that I can check now too, without having access to my desktop PC and running OC. |
|
So far so good. For GitHub Actions actions it can also update releases by pinning them to commit SHAs, which is the recommendation since tags can be moved: #17147. |
|
I've triggered all updates. Reviewed and tested those that I could, also merged them with manual fixed if necessary. A couple of them are up-to-date where I need input/review from others, see the comments. |
|
Should we close these? Is there something that will close them automatically? |
|
No and no. It's not an ideal solution, but I guess the only thing the Revolut developers could come up with to allow everyone with read access to the repo to be able to see an overview of what Revolut does, and for maintainers to trigger updates. But you can see and do the same thing under https://developer.mend.io/github/OrchardCMS/OrchardCore if you have the rights for it (I think at least everyone with org admins should see that, perhaps also with repo admin, and perhaps also with repo write permissions; @MikeAlhayek can you?). So, we can also disable this issue. |
|
No access to the link you shared |
|
I guess only admins can use that, then, so that's why we have this issue. |
|
We triaged this issue and set the milestone according to the priority we think is appropriate (see the docs on how we triage and prioritize issues). This indicates when the core team may start working on it. However, if you'd like to contribute, we'd warmly welcome you to do that anytime. See our guide on contributions here. |
This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.
Awaiting Schedule
These updates are awaiting their schedule. Click on a checkbox to get an update now.
Ignored or Blocked
These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.
Microsoft.AspNetCore.Authentication.Facebook,Microsoft.AspNetCore.Authentication.Google,Microsoft.AspNetCore.Authentication.MicrosoftAccount,Microsoft.AspNetCore.Authentication.Twitter,Microsoft.AspNetCore.DataProtection.StackExchangeRedis,Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation,Microsoft.AspNetCore.Mvc.Testing,Microsoft.AspNetCore.Owin,Microsoft.Extensions.Caching.Memory,Microsoft.Extensions.Caching.StackExchangeRedis,Microsoft.Extensions.Http.Resilience,System.IO.Hashing,System.Runtime.Caching,System.Text.Json,mcr.microsoft.com/dotnet/aspnet)Detected dependencies
docker-compose
dockerfile
github-actions
npm
nuget
pip_requirements
The text was updated successfully, but these errors were encountered: