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 cspell from 5.13.2 to 5.13.3 #400

Closed

Conversation

snyk-bot
Copy link

@snyk-bot snyk-bot commented Jan 1, 2022

Snyk has created this PR to upgrade cspell from 5.13.2 to 5.13.3.

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 22 days ago, on 2021-12-11.
Release notes
Package name: cspell
  • 5.13.3 - 2021-12-11

    Changes

    Fixes

    dev: Add awareness of Monkey C (#2089)

    dev: Add awareness of Monkey C (#2089)


    fix: Hunspell make sure COMPOUNDFLAG is supported (#2088)

    fix: Hunspell make sure COMPOUNDFLAG is supported (#2088)


    fix: cspell-tools - limit memory usage when build dictionaries (#2087)

    fix: cspell-tools - limit memory usage when build dictionaries (#2087)

    When compiling Estonian, it would cause node to run out of keys due to caching highly repetitive suffixes.


  • 5.13.2 - 2021-12-07

    Changes

    fix: jest/expect-expect warning (#2062)

    fix: jest/expect-expect warning (#2062)

    Inlined the code since it couldn't understand the double redirection


    chore: add setup-node caching to remaining jobs (#2043)

    chore: add setup-node caching to remaining jobs (#2043)

    It was already setup for some of the jobs, this extends it to the rest


    fix: Update TypeScript extensions (#2051)

    fix: Update TypeScript extensions (#2051)


    Fixes

    fix: make cspell aware of PureScript and Dhall (#2067)

    fix: make cspell aware of PureScript and Dhall (#2067)


    Maintenance

    ci: Remove eslint-plugin-promise (#2076)

    ci: Remove eslint-plugin-promise (#2076)

    Add it back when Support ESLint 8.x · Issue #218 · xjamundx/eslint-plugin-promise is resolved.


    ci: Update eslint (#2075)

    ci: Update eslint (#2075)


    ci: always use the same version of npm. (#2068)

    ci: always use the same version of npm. (#2068)


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!

@pull-dog
Copy link

pull-dog bot commented Jan 1, 2022

*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
46d00ce0-6b48-11ec-9015-9ee4ddcc9009

@mistaken-pull-closer mistaken-pull-closer bot added the invalid This doesn't seem right label Jan 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid This doesn't seem right
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant