Skip to content

Commit 5b3d8e2

Browse files
authored
Use GitReleaseManager dotnet tool (#3091)
1 parent 47ff4bf commit 5b3d8e2

File tree

3 files changed

+11
-7
lines changed

3 files changed

+11
-7
lines changed

.config/dotnet-tools.json

+7-1
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,12 @@
77
"commands": [
88
"async-generator"
99
]
10+
},
11+
"gitreleasemanager.tool": {
12+
"version": "0.11.0",
13+
"commands": [
14+
"dotnet-gitreleasemanager"
15+
]
1016
}
1117
}
12-
}
18+
}

ReleaseProcedure.txt

+4-5
Original file line numberDiff line numberDiff line change
@@ -3,12 +3,11 @@ These are the tasks typically needed to create an official NHibernate release.
33
* In GitHub, make sure no open issues have milestone set to the release
44
that is about to happen (as these will show in the milestone).
55

6-
* Create a draft release in Github with GitReleaseManager. If you have used
7-
the NHibernate build menu, it should be available in Tools\gitreleasemanager\x.x.x\
8-
(change x.x.x by its current version in tools).
9-
By example:
6+
* Restore local dotnet tools: `dotnet tool restore`
107

11-
Tools\gitreleasemanager\0.11.0\tools\GitReleaseManager.exe create -o nhibernate -r nhibernate-core -m 5.3 --token yourGitHubTokenWithRepoScope
8+
* Create a draft release in Github with GitReleaseManager. For example:
9+
10+
dotnet gitreleasemanager create -o nhibernate -r nhibernate-core -m 5.3 --token yourGitHubTokenWithRepoScope
1211

1312
(Adjust the -m milestone parameter above, and add "-c branchname" if
1413
releasing another branch than master)

Tools/packages.csproj

-1
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,6 @@
1313
<ItemGroup>
1414
<PackageReference Include="vswhere" Version="2.1.4" />
1515
<PackageReference Include="NUnit.Console" Version="3.10.0" />
16-
<PackageReference Include="GitReleaseManager" Version="0.11.0" />
1716
</ItemGroup>
1817

1918
</Project>

0 commit comments

Comments
 (0)