create-bcp-app 0.2.18 → 0.2.19

package/README.md

@@ -64,17 +64,17 @@ Select storage provider:
 
 New projects include `bcp.project.json`.
 
-Example for the `0.2.18` target:
+Example for the `0.2.19` target:
 
 ```json
 {
   "schemaVersion": 1,
   "framework": "bcp",
   "projectName": "my-app",
-  "frameworkPackage": "npm:@chidchanun/bcp@0.2.18",
+  "frameworkPackage": "npm:@chidchanun/bcp@0.2.19",
   "createdWith": {
     "package": "create-bcp-app",
-    "version": "0.2.18"
+    "version": "0.2.19"
   },
   "packageManager": "npm",
   "presets": {
@@ -251,6 +251,19 @@ const removeSignals =
 
 Default signals are `SIGTERM` and `SIGINT`.
 
+## Stability & API Freeze — 0.2.19
+
+`0.2.19` keeps the `0.2.x` public package surface stable before the next platform baseline.
+
+Framework maintainers can validate the frozen contract with:
+
+```bash
+npm run api:check
+npm run release:readiness
+```
+
+Generated applications do not need to run these framework-repository release commands. Application code should continue importing documented `bcp/*` entrypoints rather than private framework source paths.
+
 ## Application packaging
 
 ```bash
@@ -260,7 +273,7 @@ npm run package
 
 The deployment package excludes application `devDependencies` and project `.env` values. Supply secrets through the deployment environment.
 
-BCP `0.2.18` prepared framework packages use compiled ESM runtime files for the main server entrypoints including config, auth, observability, deployment, server and middleware.
+BCP `0.2.19` prepared framework packages preserve the compiled ESM runtime map introduced by Deployment Platform v2 for the main server entrypoints including config, auth, observability, deployment, server and middleware.
 
 ## Project generators
 
@@ -288,5 +301,5 @@ npm run generate -- migration create_users
 For prerelease/local package verification:
 
 ```bash
-npx create-bcp-app my-app --bcp file:../chidchanun-bcp-0.2.18.tgz
+npx create-bcp-app my-app --bcp file:../chidchanun-bcp-0.2.19.tgz
 ```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-bcp-app",
-  "version": "0.2.18",
+  "version": "0.2.19",
   "description": "Create a new BCP Framework application.",
   "type": "module",
   "license": "MIT",

package/template/README.md

@@ -178,6 +178,12 @@ NODE_ENV
 BCP_SHUTDOWN_TIMEOUT_MS
 ```
 
+## Stability baseline — BCP 0.2.19
+
+BCP `0.2.19` freezes the documented `0.2.x` public `bcp/*` entrypoints and prepared package-resolution contract before the next `0.3.0` baseline.
+
+Application code should import documented public entrypoints and avoid private framework `packages/*` paths. This keeps applications compatible with the frozen `0.2.19` surface.
+
 ## Production build
 
 ```bash
@@ -193,7 +199,7 @@ npm run package
 
 BCP excludes project `.env` files and application `devDependencies` from the deployment package. Supply secrets through the deployment environment.
 
-BCP 0.2.18 prepared framework packages use compiled `.mjs` runtimes for the main server entrypoints, including config, auth, observability, deployment, server and middleware.
+BCP 0.2.19 preserves compiled `.mjs` runtimes for the main server entrypoints, including config, auth, observability, deployment, server and middleware.
 
 ## Direct CLI usage