Skip to content
New issue

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

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

Already on GitHub? # to your account

[Snyk] Upgrade cspell from 5.2.4 to 5.5.2 #222

Closed

Conversation

snyk-bot
Copy link

Snyk has created this PR to upgrade cspell from 5.2.4 to 5.5.2.

ℹ️ 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 27 versions ahead of your current version.
  • The recommended version was released 22 days ago, on 2021-05-30.
Release notes
Package name: cspell
  • 5.5.2 - 2021-05-30

    v5.5.2

  • 5.5.1 - 2021-05-29

    v5.5.1

  • 5.5.0 - 2021-05-29

    v5.5.0

  • 5.4.1 - 2021-05-11

    v5.4.1

  • 5.4.0 - 2021-05-05

    v5.4.0

  • 5.3.12 - 2021-04-06

    v5.3.12

  • 5.3.11 - 2021-04-03

    v5.3.11

  • 5.3.10 - 2021-04-02

    v5.3.10

  • 5.3.9 - 2021-03-19

    v5.3.9

  • 5.3.8 - 2021-03-17

    v5.3.8

  • 5.3.7 - 2021-03-05
  • 5.3.7-alpha.3 - 2021-03-05
  • 5.3.7-alpha.2 - 2021-03-05
  • 5.3.7-alpha.1 - 2021-03-05
  • 5.3.7-alpha.0 - 2021-03-05
  • 5.3.6 - 2021-03-05
  • 5.3.5 - 2021-03-05
  • 5.3.4 - 2021-03-01
  • 5.3.3 - 2021-02-26
  • 5.3.2 - 2021-02-26
  • 5.3.1 - 2021-02-25
  • 5.3.0 - 2021-02-25
  • 5.3.0-alpha.4 - 2021-02-25
  • 5.3.0-alpha.3 - 2021-02-23
  • 5.3.0-alpha.2 - 2021-02-22
  • 5.3.0-alpha.1 - 2021-02-19
  • 5.3.0-alpha.0 - 2021-02-18
  • 5.2.4 - 2021-01-28
from cspell GitHub release notes
Commit messages
Package name: cspell

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

@mistaken-pull-closer
Copy link

Thanks for your submission.

It appears that you've created a pull request using one of our repository's branches. Since this is
almost always a mistake, we're going to go ahead and close this. If it was intentional, please
let us know what you were intending and we can see about reopening it.

Thanks again!

@mistaken-pull-closer mistaken-pull-closer bot added the invalid This doesn't seem right label Jun 21, 2021
@pull-dog
Copy link

pull-dog bot commented Jun 21, 2021

*Ruff* 🐶 I wasn't able to find any Docker Compose files in your repository at any of the given paths in the pull-dog.json configuration file, or the default docker-compose.yml file 😩 Make sure the given paths are correct.

Files checked:

  • docker-compose.yml
What is this?

Pull Dog is a GitHub app that makes test environments for your pull requests using Docker, from a docker-compose.yml file you specify. It takes 19 seconds to set up (we counted!) and there's a free plan available.

Visit our website to learn more.

Commands
  • @pull-dog up to reprovision or provision the server.
  • @pull-dog down to delete the provisioned server.
Troubleshooting

Need help? Don't hesitate to file an issue in our repository

Configuration

{
  "isLazy": false,
  "dockerComposeYmlFilePaths": [
    "docker-compose.yml"
  ],
  "expiry": "00:00:00",
  "conversationMode": "singleComment"
}

Trace ID
458476d0-d239-11eb-90cb-40791eac379a

@guardrails
Copy link

guardrails bot commented Jun 21, 2021

⚠️ We detected 5 security issues in this pull request:

Mode: paranoid | Total findings: 5 | Considered vulnerability: 5

Vulnerable Libraries (5)
Severity Details
Medium browserslist@4.16.1 upgrade to >4.16.4
Medium glob-parent@5.1.1 upgrade to >=5.1.2
Medium hosted-git-info@2.8.8 upgrade to `>=2.8.9
High lodash@4.17.20 upgrade to >=4.17.21
High y18n@4.0.0 upgrade to >=5.0.5

More info on how to fix Vulnerable Libraries in JavaScript.


👉 Go to the dashboard for detailed results.

📥 Happy? Share your feedback with us.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
invalid This doesn't seem right
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant