Skip to content

Commit b40baa3

Browse files
authored
Merge pull request #63 from jsturtevant/release-0.5.0
Bump to version 0.5.0
2 parents 8ac59f2 + c59f0d7 commit b40baa3

File tree

2 files changed

+5
-4
lines changed

2 files changed

+5
-4
lines changed

Directory.Build.props

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
<Project>
22
<PropertyGroup>
3-
<VersionPrefix>0.4.0</VersionPrefix>
3+
<VersionPrefix>0.5.0</VersionPrefix>
44
<VersionSuffix Condition="'$(BuildNumber)' == ''">dev</VersionSuffix>
55
<VersionSuffix Condition="'$(BuildNumber)' != ''">preview$([System.String]::Format('{0:00000}', $([MSBuild]::Add($(BuildNumber), 0))))</VersionSuffix>
66
<PackageVersion>$(VersionPrefix)-$(VersionSuffix)</PackageVersion>

RELEASE.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,15 @@
11
# Releasing the package
22

3+
1. Update all the tool versions in [Directory.Build.Props](./Directory.Build.props)
34
1. Open a PR to update the `<VersionPrefix>` tag in [Directory.Build.Props](./Directory.Build.props)
4-
2. Maintainers approve and merge PR
5-
3. After the PR merges a maintainer triggers the Release workflow on the main branch via the github Actions UI or runs:
5+
1. Maintainers approve and merge PR
6+
1. After the PR merges a maintainer triggers the Release workflow on the main branch via the github Actions UI or runs:
67

78
```
89
gh workflow run build -f test-run=false
910
```
1011

11-
4. The release flow will build and publish the packages to nuget, tag the repository with version of the release, and create a GH release
12+
>The release flow will build and publish the packages to nuget, tag the repository with version of the release, and create a GH release
1213
5. Maintainer updates release notes with package info:
1314

1415
```

0 commit comments

Comments
 (0)