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 copy-to-clipboard from 3.2.0 to 3.3.1 #2296

Merged
merged 1 commit into from
Oct 12, 2020

Conversation

snyk-bot
Copy link
Contributor

Snyk has created this PR to upgrade copy-to-clipboard from 3.2.0 to 3.3.1.

✨ Snyk has automatically assigned this pull request, set who gets assigned.
ℹ️ 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 3 versions ahead of your current version.
  • The recommended version was released 8 months ago, on 2020-02-22.
Release notes
Package name: copy-to-clipboard from copy-to-clipboard GitHub release notes
Commit messages
Package name: copy-to-clipboard

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

👩‍💻 Set who automatically gets assigned

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@snyk-bot snyk-bot requested a review from bsekachev as a code owner October 10, 2020 06:09
@coveralls
Copy link

Coverage Status

Coverage remained the same at 65.32% when pulling 1966a18 on snyk-upgrade-d398e073a268549bba2f39cfd38404c2 into 2b221d2 on develop.

@bsekachev bsekachev merged commit b6506b6 into develop Oct 12, 2020
@bsekachev bsekachev deleted the snyk-upgrade-d398e073a268549bba2f39cfd38404c2 branch October 12, 2020 09:40
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.

3 participants