Skip to content

Commit 809b0ca

Browse files
authored
Merge pull request libgit2#4533 from pks-t/pks/v0.27.0-rc1
v0.27.0-rc1: version bump
2 parents 894ccf4 + 23d4a91 commit 809b0ca

File tree

3 files changed

+28
-4
lines changed

3 files changed

+28
-4
lines changed

CHANGELOG.md

Lines changed: 18 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,15 @@
1-
v0.26 + 1
1+
v0.27 + 1
2+
---------
3+
4+
### Changes or improvements
5+
6+
### API additions
7+
8+
### API removals
9+
10+
### Breaking API changes
11+
12+
v0.27
213
---------
314

415
### Changes or improvements
@@ -54,6 +65,12 @@ v0.26 + 1
5465

5566
* Fix files not being treated as modified when only the file mode has changed.
5667

68+
* We now explicitly reject adding submodules to the index via
69+
`git_index_add_frombuffer`.
70+
71+
* Fix handling of `GIT_DIFF_FIND_RENAMES_FROM_REWRITES` raising `SIGABRT` when
72+
one file has been deleted and another file has been rewritten.
73+
5774
* Fix for WinHTTP not properly handling NTLM and Negotiate challenges.
5875

5976
* When using SSH-based transports, we now repeatedly ask for the passphrase to

docs/release.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,13 @@ We aim to release once every six months. We start the process by opening an issu
2323

2424
We tag at least one release candidate. This RC must carry the new version in the headers, including the SOVERSION. If there are no significant issues found, we can go straight to the release after a single RC. This is up to the discretion of the release manager. There is no set time to have the candidate out, but we should we should give downstream projects at least a week to give feedback.
2525

26+
Preparing the first release candidate includes updating the version number of libgit2 to the new version number. To do so, a pull request shall be submitted that adjusts the version number in the following places:
27+
28+
- CHANGELOG.md
29+
- include/git2/version.h
30+
31+
As soon as the pull request is merged, the merge commit shall be tagged with a lightweight tag.
32+
2633
The tagging happens via GitHub's "releases" tab which lets us attach release notes to a particular tag. In the description we include the changes in `CHANGELOG.md` between the last full release. Use the following as a base for the release notes
2734

2835
This is the first release of the v0.X series, <codename>. The changelog follows.

include/git2/version.h

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,12 +7,12 @@
77
#ifndef INCLUDE_git_version_h__
88
#define INCLUDE_git_version_h__
99

10-
#define LIBGIT2_VERSION "0.26.0"
10+
#define LIBGIT2_VERSION "0.27.0"
1111
#define LIBGIT2_VER_MAJOR 0
12-
#define LIBGIT2_VER_MINOR 26
12+
#define LIBGIT2_VER_MINOR 27
1313
#define LIBGIT2_VER_REVISION 0
1414
#define LIBGIT2_VER_PATCH 0
1515

16-
#define LIBGIT2_SOVERSION 26
16+
#define LIBGIT2_SOVERSION 27
1717

1818
#endif

0 commit comments

Comments
 (0)