Merge pull request #63 from jsturtevant/release-0.5.0

Bump to version 0.5.0
bytecodealliance · Dec 2, 2024 · b40baa3 · b40baa3
2 parents 8ac59f2 + c59f0d7
commit b40baa3
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 4 deletions.
diff --git a/Directory.Build.props b/Directory.Build.props
@@ -1,6 +1,6 @@
 <Project>
     <PropertyGroup>
-        <VersionPrefix>0.4.0</VersionPrefix>
+        <VersionPrefix>0.5.0</VersionPrefix>
         <VersionSuffix Condition="'$(BuildNumber)' == ''">dev</VersionSuffix>
         <VersionSuffix Condition="'$(BuildNumber)' != ''">preview$([System.String]::Format('{0:00000}', $([MSBuild]::Add($(BuildNumber), 0))))</VersionSuffix>
         <PackageVersion>$(VersionPrefix)-$(VersionSuffix)</PackageVersion>

diff --git a/RELEASE.md b/RELEASE.md
@@ -1,14 +1,15 @@
 # Releasing the package
 
+1. Update all the tool versions in [Directory.Build.Props](./Directory.Build.props)
 1. Open a PR to update the `<VersionPrefix>` tag in [Directory.Build.Props](./Directory.Build.props)
-2. Maintainers approve and merge PR
-3. After the PR merges a maintainer triggers the Release workflow on the main branch via the github Actions UI or runs:
+1. Maintainers approve and merge PR
+1. After the PR merges a maintainer triggers the Release workflow on the main branch via the github Actions UI or runs:
 
 ```
 gh workflow run build -f test-run=false
 ```
 
-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
+>The release flow will build and publish the packages to nuget, tag the repository with version of the release, and create a GH release
 5. Maintainer updates release notes with package info:
 
 ```