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: .windsurf/workflows/prepare-update.md
+32-70Lines changed: 32 additions & 70 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ auto_execution_mode: 3
5
5
6
6
# Prepare Update
7
7
8
-
Bumps the MotelyVersion, cleans everything, builds all .NET projects, AOT-publishes both WASM targets, prepares the active npm packages, and walks the user through publishing.
8
+
Bumps the MotelyVersion, cleans everything, builds the solution, publishes **Motely** for `net10.0-browser` (Bootsharp), stages **`motely-wasm`**, and walks the user through npm publish. The old **`Motely.NodeAddon`** / `Motely.npm` flow is gone.
9
9
10
10
**User provides**: the new version number — OR if not specified, read the current `<MotelyVersion>` from `Directory.Packages.props` and auto-increment the patch (e.g. `2.2.1` → `2.2.2`).
This publishes `Motely.BrowserWasm` using the validated browser-wasm AOT path. After publish, run the central staging script to copy the filtered `_framework` output into `Motely.npm/_framework/`.
92
-
93
-
Keep `x:\JammySeedFinder\src\MotelyJAML\Directory.Build.props` in place so browser-wasm projects explicitly reset `PublishAot=false` and `PublishReadyToRun=false` at the local repo level. The actual browser AOT settings live in the project files via `RunAOTCompilation=true` and `WasmBuildNative=true`.
If this fails, capture the full SDK error and stop before changing other steps.
92
+
`Motely` multi-targets `net10.0-browser`. Publish, then run `motely-wasm`'s build script (`Motely/build/stage-wasm.mjs` copies `bootsharp/` into `motely-wasm/dist/`).
**`Motely.NodeAddon` was removed.** There is no second C# package to publish for Node in this workflow. Browser delivery is **Bootsharp / `net10.0-browser` only**.
If you add a new Node `.node` target later, document its `dotnet publish` command and how artifacts land under `motely-node/`. Until then, **skip**`npm pack` for `motely-node` unless you intentionally ship JS-only stubs.
0 commit comments