Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Upgrade @deepcode/tsc from 2.1.0 to 2.1.1 #77

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

deepcodeg
Copy link
Contributor

Snyk has created this PR to upgrade @deepcode/tsc from 2.1.0 to 2.1.1.

merge advice
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 1 version ahead of your current version.
  • The recommended version was released 21 days ago, on 2021-01-26.
Release notes
Package name: @deepcode/tsc
  • 2.1.1 - 2021-01-26

    2.1.1 (2021-01-29)

    Bug Fixes

    • build from typescript before publish (8e6bcf5)
  • 2.1.0 - 2021-01-05

    2.1.0 (2021-01-28)

    Bug Fixes

    • add categories to tags in sarif converter (6f72065)
    • package.json & package-lock.json to reduce vulnerabilities (8449799)
    • stabilise rule id in sarif (552389f)
    • upgrade @ types/lodash from 4.14.166 to 4.14.167 (a9d791f)

    Features

    • add highlighting to sarif converter (d33ea84)
    • changed logic for shortDescription.text to have rule instead of a message (6af2568)
    • fixed typo in sarif converter (1879530)
    • meta-coverage added to sarif run (c70e14e)
    • new arg: limitToFiles in getAnalysis API call (d72bfbc)
from @deepcode/tsc GitHub release notes
Commit messages
Package name: @deepcode/tsc

Compare


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants