Skip to content

chore: docs npm high vuln.#256

Merged
heitorlessa merged 1 commit into
aws-powertools:developfrom
heitorlessa:chore/npm-sec-vuln
Jan 11, 2021
Merged

chore: docs npm high vuln.#256
heitorlessa merged 1 commit into
aws-powertools:developfrom
heitorlessa:chore/npm-sec-vuln

Conversation

@heitorlessa

Copy link
Copy Markdown
Contributor

Issue #, if available:

Description of changes:

Checklist

Breaking change checklist

RFC issue #:

  • Migration process documented
  • Implement warnings (if it can live side by side)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@heitorlessa heitorlessa added the internal Maintenance changes label Jan 11, 2021
@codecov-io

codecov-io commented Jan 11, 2021

Copy link
Copy Markdown

Codecov Report

Merging #256 (4cf8623) into develop (893068f) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff            @@
##           develop     #256   +/-   ##
========================================
  Coverage    99.81%   99.81%           
========================================
  Files           76       76           
  Lines         2772     2772           
  Branches       112      112           
========================================
  Hits          2767     2767           
  Misses           4        4           
  Partials         1        1           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 893068f...4cf8623. Read the comment docs.

@heitorlessa heitorlessa merged commit b5e3593 into aws-powertools:develop Jan 11, 2021
@heitorlessa heitorlessa deleted the chore/npm-sec-vuln branch January 11, 2021 12:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

internal Maintenance changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants