Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
@harald-somnes-hanssen_2204 thanks for the Feature Request, definitely makes sense to me!
Just a couple things to consider / think about, on our end, from an implementation point.
How do you remove internalized chocolatey packages? Is this using the Package Retention Rules feature? Maybe it would make sense to add a deletion as part of this process.
How many excess/outdated vulnerabilities do you have now? Handful? Dozens? Hundreds?
I'm not super-familiar with ADO's npm feeds, but I don't think you're the only one who's had this issue, based on this old post.
Since that post was made, we added the "Authentication" drop down, and you should select Bearer for that. Then, keep Username empty.
If you do that, the Password field will be used as the Bearer token.
Can you try taht, and let us know if it works?
@philippe-camelio_3885 this seems to be a regression, but an easy fix. It'll be fixed in the next BuildMaster (6.2.28), but you can grab the patch from here: https://inedo.myjetbrains.com/youtrack/issue/BM-3672
Just download that SQL file, run it in your environment, and they'll start showing again.
Thanks @bvandehey_9055 !
Just a couple questions to help us understand...
The recommended private server (https://pub.dev/packages/pub_server) seems to be discontinued and no longer maintained. Are there any other private package server on the market?
This will help us come up with how to evaluate this!