Closed 304NotModified closed 1 year ago
polite bump @mburumaxwell
@304NotModified
We have not added full support for security updates only but PRs are always welcome. 🙂
However, changing the lines you referenced may not produce the results you desire. I suggest looking at the following:
Do you mean we have to port these lines or use that script instead of this plugin?
Porting the lines and any other related ones should do because our script borrows heavily from the test one in the parent repository.
According to update-script.rb#L314 it allows security updates even if dependency is outside of allow
list, so you can do a bit of hack with:
DEPENDABOT_ALLOW_CONDITIONS: '[{"dependency-name":"a1","dependency-type":"all"}]' # specify any non-existing package name, so it will ignore everything but still allow security updates
Hello @mburumaxwell, why did you close it as 'not planned'? I think that this enhancement would be very useful. Even if you don't have time, maybe there will be someone brave enough to try to submit PR ;)
I think this feature is a must have.
We tried changing the ruby script in the past, but unfortunately you really need some Ruby skills.
Hi,
We like to use this great extension for our security updates on Azure Devops Services. Is it possible to only create pull requests for security updates?
We tried with
dependency-type":"security"
- found on https://github.com/tinglesoftware/dependabot-azure-devops/blob/main/src/script/update-script.rb#L173But it gives always: not allowed, e.g:
Tested with gulp-scss-lint 0.7.2 (link to GitHub security database) and log4net 2.0.9 (link to GitHub security database)
full yaml:
full package.json: