You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: RELEASE.md
+8-3Lines changed: 8 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,8 +2,8 @@
2
2
3
3
1. Update all the tool versions in [Directory.Build.Props](./Directory.Build.props)
4
4
1. Open a PR to update:
5
-
- the `<VersionPrefix>` tag in [Directory.Build.Props](./Directory.Build.props)
6
-
- the version `BytecodeAlliance.Componentize.DotNet.Wasm.SDK` package `version` to match the `<VersionPrefix>`i.e. `Version="0.6.0-preview*"`in the [template](./templates/content/wasi-cli/wasi-cli.csproj). This ensures the templates use the latest package.
5
+
- the `<VersionPrefix>` tag in [Directory.Build.Props](./Directory.Build.props)
6
+
- the `BytecodeAlliance.Componentize.DotNet.Wasm.SDK` package `version` to match the `<VersionPrefix>` in the [template](./templates/content/wasi-cli/wasi-cli.csproj). For example the template version might look like `Version="0.6.0-preview*"`. This ensures the templates use the latest package.
7
7
1. Maintainers approve and merge PR
8
8
1. After the PR merges a maintainer triggers the Release workflow on the main branch via the github Actions UI or runs:
9
9
@@ -15,9 +15,14 @@ gh workflow run build -f test-run=false
15
15
5. Maintainer updates release notes with package info:
6. Post message about release [c# collaboration Zulip channel](https://bytecodealliance.zulipchat.com/#narrow/channel/407028-C.23.2F.2Enet-collaboration)
0 commit comments