create-brainerce-store 1.82.0 → 1.83.0
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/dist/index.js +11 -2
- package/package.json +1 -1
package/dist/index.js
CHANGED
|
@@ -31,7 +31,7 @@ var require_package = __commonJS({
|
|
|
31
31
|
"package.json"(exports2, module2) {
|
|
32
32
|
module2.exports = {
|
|
33
33
|
name: "create-brainerce-store",
|
|
34
|
-
version: "1.
|
|
34
|
+
version: "1.83.0",
|
|
35
35
|
description: "Scaffold a production-ready e-commerce storefront connected to Brainerce",
|
|
36
36
|
homepage: "https://brainerce.com",
|
|
37
37
|
repository: {
|
|
@@ -350,7 +350,16 @@ var BRAINERCE_RUNTIME_DEPS = Object.freeze({
|
|
|
350
350
|
// So the ordering is: ship the SDK, wait out the week, THEN adopt its API in
|
|
351
351
|
// `templates/` and raise this floor in the same change. A feature is not
|
|
352
352
|
// late for waiting seven days; a template nobody can publish is worse.
|
|
353
|
-
|
|
353
|
+
//
|
|
354
|
+
// ⛔ EXACT, NOT `^`. A caret admits versions that DO NOT EXIST YET, so every
|
|
355
|
+
// future SDK release re-rolls the dice inside an environment we do not
|
|
356
|
+
// control. Measured 2026-09-10: `^2.7.0` already reached past its own floor
|
|
357
|
+
// to 2.8.0, published the day before — so the range was *younger* than the
|
|
358
|
+
// version it was written to pin, and a cooldown that 2.7.0 was about to
|
|
359
|
+
// clear it could not. An exact pin ages once and then stays eligible.
|
|
360
|
+
// Keep it exact when you raise it: a range here is not a convenience, it is
|
|
361
|
+
// an open invitation for tomorrow's release to break yesterday's template.
|
|
362
|
+
brainerce: "2.7.0",
|
|
354
363
|
"isomorphic-dompurify": "^3.8.0"
|
|
355
364
|
});
|
|
356
365
|
|