File tree Expand file tree Collapse file tree 1 file changed +5
-18
lines changed Expand file tree Collapse file tree 1 file changed +5
-18
lines changed Original file line number Diff line number Diff line change @@ -38,6 +38,11 @@ This means that v2.0 will have API and ABI changes to support SHA256.
38
38
[ further benchmarking] ( https://benchmarks.libgit2.org/ ) and several API
39
39
improvements and git compatibility updates.
40
40
41
+ * ** Warning when configuring without SHA1DC**
42
+ Users are encouraged to use SHA1DC, which is _ git's hash_ ; users
43
+ should not use SHA1 in the general case. Users will now be warned
44
+ if they try to configure cmake with a SHA1 backend (` -DUSE_SHA1=... ` ).
45
+
41
46
## Breaking changes
42
47
43
48
There are several ABI-breaking changes that integrators, particularly
@@ -66,24 +71,6 @@ maintainers of bindings or FFI users, may want to be aware of.
66
71
to provide a mechanism to nicely free the configuration entries that
67
72
they provide.
68
73
69
- ## Future Changes
70
-
71
- We're preparing for libgit2 v2.0, and this is expected to be
72
- the last feature-release for the libgit2 v1.0 release line. We
73
- will introduce a number of breaking changes in v2.0:
74
-
75
- * ** SHA256 support**
76
- Adding SHA256 support will change the API and ABI.
77
-
78
- * ** TLS v1.2 as a minimum**
79
- libgit2 will remove support for HTTPS versions prior to TLS v1.2 and
80
- will update to the "intermediate" settings [ documented by
81
- Mozilla] ( https://wiki.mozilla.org/Security/Server_Side_TLS ) .
82
-
83
- * Removing the chromium zlib built-in
84
-
85
- * Removing the libssh2 embedded build system
86
-
87
74
## What's Changed
88
75
89
76
### New features
You can’t perform that action at this time.
0 commit comments