package[-lock].json: Update swagger-test-templates#3
Conversation
|
I can narrow this PR down to just Sorry for doing these PRs out of the blue. I've just been searching for a way to have up-to-date-dependencies on the |
|
Oh no worries, I am glad you are making PR and keep this project up to date! |
|
@DeeDeeG I have merged this into the master, would you like me to bump the version to |
|
A version 0.8.4 would definitely be appreciated. I ultimately have to see what the rest of the team is okay with, but I didn't even have a non-git-revision option until landing these pull requests here. I was considering using the commit id from my "mocha to devdependencies" PR at upstream, since that commit is technically available in upstream's git repo. But if the team is okay using a fork, instead of upstream, this will definitely be the best option. Thank you for asking! |
|
For the record, upstream This PR was necessary for this fork, as this fork locks This fork's advantage, in terms of audits [when depending on this package from an external |
|
Perfect, thanks for your PRs. I published |
|
Thank you! |
Hi, as mentioned in a comment in the previous PR, I bumped dependencies over at
swagger-test-templates.By using this latest version of
swagger-test-templates(1.6.0), people who add this package (swagger-node) in their projects will only have one remaining audit warning against it.(dependencies I bumped over at
swagger-test-templateswere "lodash" and "json-schema-deref-sync-->mpath")