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 eslint-plugin-react from 7.19.0 to 7.20.0 #61

Merged
merged 1 commit into from
Jun 9, 2020

Conversation

snyk-bot
Copy link
Contributor

@snyk-bot snyk-bot commented Jun 8, 2020

Snyk has created this PR to upgrade eslint-plugin-react from 7.19.0 to 7.20.0.

merge advice

✨What is Merge Advice? We check thousands of dependency upgrade pull requests and CI tests every day to see which upgrades were successfully merged. After crunching this data, we give a recommendation on how safe we think the change is for you to merge without causing issues. Learn more, and share your feedback to help improve this feature. 🙏
ℹ️ 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 a month ago, on 2020-05-13.

The recommended version fixes:

Severity Issue Exploit Maturity
Arbitrary Code Injection
SNYK-JS-SERIALIZEJAVASCRIPT-570062
Proof of Concept
Release notes
Package name: eslint-plugin-react from eslint-plugin-react GitHub release notes
Commit messages
Package name: eslint-plugin-react
  • 25bf6cc Update CHANGELOG and bump version
  • 2598b1e [Dev Deps] update `@types/eslint`, `@types/estree`, `@types/node`, `@typescript-eslint/parser`, `coveralls`, `eslint-config-airbnb-base`, `eslint-plugin-import`, `typescript`
  • f94d851 [Fix] `jsx-sort-props`: only use localeCompare when case is ignored
  • c481a26 [Docs] Clean up examples in rule docs
  • 88d404d [eslint] remove `operator-linebreak` override
  • 304590a Merge pull request #2635 from ljharb/eslint7
  • 35030a0 [Tests] fix mistaken error property and add output property
  • 906b474 [New] support eslint v7
  • d66f467 [Fix] `jsx-key`: add a failing test case for optional chaining
  • da7a045 [Fix] `no-unused-state`: handle optional chaining
  • 9861469 [New] `forbid-component-props`/`forbid-dom-props`: Allow a custom message with forbid props
  • ab28224 [Fix] `jsx-pascal-case`: Do not consider namespaces when checking for DOM
  • 25b1936 [Fix] `jsx-curly-spacing`, `jsx-no-bind`, `usedPropTypes` util: avoid node.start and node.end
  • db4e471 [readme] Add Rules of Hooks to Other useful plugins section
  • b9d2eb5 [Fix] `jsx-no-target-blank`: allow `no-referrer` without `noopener` by default
  • 3385caa [Tests] `button-has-type`: ensure no mistakenly allowed identifiers named `button`/`submit`/`reset`
  • aecff62 [Fix] `button-has-type`: improve message when non-static value is used
  • bea3b30 [Docs] `no-this-in-sfc`: backtick `this`
  • 78ddd46 [Fix] `no-adjacent-inline-elements`: prevent crash on nullish children
  • 80f3826 [Docs] `function-component-definition`: Fix unnamedComponents option examples
  • e19287d [tests] `displayName`: add a test case
  • a93ef20 [Fix] `prop-types`: avoid crash when spreading any type
  • ad18d35 [Fix] `require-render-return`: add missing "a"
  • 6aa7874 [Fix] `jsx-no-comment-textnodes`: fix for `@typescript-eslint/parser`

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

@DavidKindler DavidKindler merged commit f57f43d into master Jun 9, 2020
@DavidKindler DavidKindler deleted the snyk-upgrade-b07cb3e2e25b3727c14f4048d24d636c branch June 9, 2020 16:08
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