Skip to content

Conversation

@snyk-bot
Copy link

Snyk has created this PR to upgrade sqlite3 from 4.0.6 to 4.1.1.

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 5 versions ahead of your current version.
  • The recommended version was released 5 months ago, on 2019-12-05.
Release notes
Package name: sqlite3
  • 4.1.1 - 2019-12-05
    • Electron v6.1 and v7 support #1237
    • Electron v7.1 support #1254
    • SQLite3 update to 3.30.1 #1238
    • Overwrite 'msbuild_toolset' only if 'toolset' is defined #1242
    • Upgrade CI to node-gyp 6.x for Windows Electron v5 & v6 builds #1245
    • Node v13 support #1247
    • Use minimum supported node version for Electron 7 #1255
  • 4.1.0 - 2019-08-16
    No content.
  • 4.0.9 - 2019-06-13
    • ci: use trusty for ubuntu to create prebuilt binaries for node v12 to create lower requirements for libc
  • 4.0.8 - 2019-05-11

    Re-release of 4.0.7 but without the excess .vscode files.

  • 4.0.7 - 2019-05-08
  • 4.0.6 - 2019-01-11

    A re-release of the retracted v4.0.5 because of node-pre-gyp being unavailable.

from sqlite3 GitHub release notes

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