Security Audit Version Bump#279
Merged
blakeembrey merged 1 commit intopillarjs:masterfrom May 26, 2022
Merged
Conversation
Codecov Report
@@ Coverage Diff @@
## master #279 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 1 1
Lines 248 248
Branches 98 98
=========================================
Hits 248 248 Continue to review full report at Codecov.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hello,
Big fan of the pillarjs organization, btw! Keep on making the world a better place
:DThe following pull request is relating to that pesky
minimistsecurity concern; changes are only to thepackage-lock.json.All tests passed successfully.
Edit* -- oh yes, I also updated, implicitly
@typescript-eslint/eslint-pluginto5.25.0.As a recommendation, I do suggest setting that explicitly as a
devDependency. I was previously working in alernamonorepo, which is why it got caught in the package-lock.If this is of any concern, which it's still passing tests, let me know and I'll close + submit a new PR.