@flare-desktop/cli 0.1.7 → 0.1.9
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +5 -1
- package/package.json +1 -1
- package/src/release-versions.js +2 -2
package/README.md
CHANGED
|
@@ -40,7 +40,7 @@ environment and local layers. The executable does not read JSON from disk. Rebui
|
|
|
40
40
|
build system tracks them. `flare dev` embeds the development layer and `flare build` embeds production. The `--config`
|
|
41
41
|
and `--environment` CLI flags select the input at build time. On Windows the generated CMake project enables
|
|
42
42
|
`FLARE_NATIVE_WEBVIEW` before fetching the C++ core; the CLI verifies that the native backend was enabled.
|
|
43
|
-
Generated projects require CLI 0.1.
|
|
43
|
+
Generated projects require CLI 0.1.9 or newer. They target C++ core v0.1.5; prebuilt mode requires the matching GitHub SDK Release. Only TypeScript templates install the types-only npm core v0.1.0; JavaScript runtime is injected by C++.
|
|
44
44
|
|
|
45
45
|
`flare build` passes `build.frontendDist` to CMake as `FLARE_FRONTEND_DIR`. The scaffolded `CMakeLists.txt` uses
|
|
46
46
|
that variable for `FlareEmbedFrontend` and for the development directory. Change the config key, not the CMake
|
|
@@ -103,3 +103,7 @@ created by the core SDK workflow after successful platform builds.
|
|
|
103
103
|
|
|
104
104
|
The former C++ `codegen` executable is replaced by `npx flare codegen --language=header|cpp|json` with
|
|
105
105
|
`--config`, `--out`, `--namespace`, `--embed-assets` and `--frontend`.
|
|
106
|
+
|
|
107
|
+
## Publishing
|
|
108
|
+
|
|
109
|
+
CI publishes the exact `version` checked into `package.json` only when it is newer than the versions already published to npm. A push with an existing version runs the tests but does not publish. For a new release, choose a version explicitly and update both `package.json` and `package-lock.json`, for example with `npm version 0.1.9 --no-git-tag-version --ignore-scripts`, then commit and push. CI does not increment the patch number or rewrite the manifests. npm trusted publishing uses OIDC.
|
package/package.json
CHANGED
package/src/release-versions.js
CHANGED
|
@@ -1,3 +1,3 @@
|
|
|
1
|
-
export const CORE_VERSION = "0.1.
|
|
1
|
+
export const CORE_VERSION = "0.1.5";
|
|
2
2
|
export const CORE_NPM_VERSION = "0.1.0";
|
|
3
|
-
export const MIN_CLI_VERSION = "0.1.
|
|
3
|
+
export const MIN_CLI_VERSION = "0.1.9";
|