[Snyk] Upgrade mariadb from 3.0.2 to 3.3.1 #96
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Snyk has created this PR to upgrade mariadb from 3.0.2 to 3.3.1.
ℹ️ 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 9 versions ahead of your current version.
The recommended version was released on 4 months ago.
Release notes
Package name: mariadb
3.3.1 (May 2024)
Full Changelog
Issues Fixed
3.3.0 (Mar 2024)
Full Changelog
Notable changes
Issues Fixed
3.2.3 (Dec 2023)
Full Changelog
3.2.2 (Oct 2023)
Full Changelog
Issues Fixed
3.2.1 (Sep 2023)
Full Changelog
Notable changes
infileStreamFactory
addition for compatibilityIssues Fixed
3.2.0 (Jun 2023)
Full Changelog
Notable changes
new APIs:
importFile(options) → Promise
connection.importFile({file:'...', 'database': '...'}) → Promise
pool.importFile({file:'...', 'database': '...'}) → Promise
example:
Issues Fixed
3.1.2 (May 2023)
Full Changelog
Notable changes
Issues Fixed
3.1.1 (Mar 2023)
Full Changelog
Issues Fixed
3.1.0 (Feb 2023)
Full Changelog
Notable changes
Timezone handling (CONJS-237)
Connector now set session timezone, solving issue with time function,
removing needs of client side conversion.
This requires that when using timezone options, to having server TZ data filled in case client timezone differ from server.
Performance
Other changes
Issues Fixed
initSql
) might not always be executed firstImportant
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: