Update dependency PyMySQL to v1 [SECURITY] #113
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR contains the following updates:
==0.10.1->==1.1.10.9.3->1.1.1GitHub Vulnerability Alerts
CVE-2024-36039
PyMySQL through 1.1.0 allows SQL injection if used with untrusted JSON input because keys are not escaped by
escape_dict.Release Notes
PyMySQL/PyMySQL (PyMySQL)
v1.1.1Compare Source
Release date: 2024-05-21
Cursor.execute(). It didn't produce valid SQLand might cause SQL injection. (CVE-2024-36039)
v1.1.0Compare Source
Release date: 2023-06-26
Cursor.warning_countto check for warnings without additional query (#1056)Cursor.fetchall()returns empty list instead of tuple (#1115). Note thatCursor.fetchmany()still return empty tuple after reading all rows for compatibility with Django.Connection.set_character_set(charset, collation=None). This method is compatible with mysqlclient. (#1119)Connection.set_charset(charset)(#1119)Since collation table is vary on MySQL server versions, collation in handshake is fragile.
charset="utf8mb3"option (#1127)v1.0.3Compare Source
Release date: 2023-03-28
_last_executedbecause of duplication with_executedby @rajat315315 in https://github.com/PyMySQL/PyMySQL/pull/948v1.0.2Compare Source
Release date: 2021-01-09
user,password,host,databaseare still positional arguments.All arguments of
connect()are now keyword-only. (#941)v1.0.1Compare Source
Release date: 2021-01-08
dbandpasswd.Note that they are still deprecated. (#939)
python_requires=">=3.6"to setup.py. (#936)v1.0.0Compare Source
Release date: 2021-01-07
Backward incompatible changes:
connect()uses keyword-only arguments. User must use keyword argument.connect()kwargsdbandpasswdare now deprecated; Usedatabaseandpasswordinstead.escape_dict,escape_sequence, andescape_stringfrompymysqlmodule. They are still in
pymysql.converters.Other changes:
__exit__closes the connection. (#886)Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.