Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit085181b

Browse files
committed
Drop obsolete info on yanking from security policy
Versions may still be yanked for security reasons under specificcircumstances, but this is not the usual or most common practice inGitPython, at least currently. Recent security updates have notbeen accompanied by yanking older versions, and allowing theseversions to be selected automatically even when not called forspecifically can be good, such as to prevent an older version witheven more vulnerabilities from being installed in situations wherefor some reason the latest version is not yet being used.In general, users shouldn't (and don't) assume all non-yankedversions to be free of security fixes that later versions havereceived. This change updates SECURITY.md to avoid giving thatimpression, but of course some versions of GitPython may still beyanked in the future if circumstances warrant it.
1 parent1e7d885 commit085181b

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

‎SECURITY.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,7 @@
22

33
##Supported Versions
44

5-
Only the latest version of GitPython can receive security updates. If a vulnerability is discovered, a fix can be issued in a new release, while older releases
6-
are likely to be yanked.
5+
Only the latest version of GitPython can receive security updates. If a vulnerability is discovered, a fix can be issued in a new release.
76

87
| Version| Supported|
98
| -------| ------------------|

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp