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: README.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -198,7 +198,7 @@ By default the project will find all wit files and execute wit-bindgen against e
198
198
</ItemGroup>
199
199
```
200
200
201
-
### Configuring location of generaged wit files
201
+
### Configuring location of generated wit files
202
202
203
203
By default the wit files are generated under the itermediate path `$(IntermediateOutputPath)wit_bindgen` which is by default at a location like `\obj\Debug\net10.0\wit_bindgen`. This means you can't really see the files and they will be ignored and not checked in to source by default (assuming you have a standard .net `.gitignore`) but intillisense will work.
Copy file name to clipboardexpand all lines: RELEASE.md
+9-2
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,9 @@
1
1
# Releasing the package
2
2
3
3
1. Update all the tool versions in [Directory.Build.Props](./Directory.Build.props)
4
-
1. Open a PR to update the `<VersionPrefix>` tag in [Directory.Build.Props](./Directory.Build.props)
4
+
1. Open a PR to update:
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.
5
7
1. Maintainers approve and merge PR
6
8
1. After the PR merges a maintainer triggers the Release workflow on the main branch via the github Actions UI or runs:
7
9
@@ -13,9 +15,14 @@ gh workflow run build -f test-run=false
13
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