@uniweb/runtime 0.21.0 → 0.22.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.
Files changed (2) hide show
  1. package/package.json +2 -2
  2. package/src/isolate-api.js +12 -8
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@uniweb/runtime",
3
- "version": "0.21.0",
3
+ "version": "0.22.0",
4
4
  "description": "Minimal runtime for loading Uniweb foundations",
5
5
  "type": "module",
6
6
  "exports": {
@@ -44,7 +44,7 @@
44
44
  "esbuild": "^0.21.0 || ^0.23.0 || ^0.24.0 || ^0.25.0 || ^0.27.0",
45
45
  "vite": "^7.3.1",
46
46
  "vitest": "^4.1.7",
47
- "@uniweb/build": "0.47.0"
47
+ "@uniweb/build": "0.47.1"
48
48
  },
49
49
  "peerDependencies": {
50
50
  "react": "^19.0.0",
@@ -164,7 +164,7 @@ export const ISOLATE_API = Object.freeze({
164
164
  * ⚖️ Revisit at 1.0: once sites are pinned in the field, *"it does not break
165
165
  * sites"* stops being free, and this paragraph is the thing to re-argue.
166
166
  */
167
- export const WIRE_FLOOR = '0.20.3'
167
+ export const WIRE_FLOOR = '0.21.0'
168
168
 
169
169
  /**
170
170
  * ⭐ **THE MINIMUM RUNTIME VERSION A SITE MAY BE PUBLISHED AT.** At or above it,
@@ -172,13 +172,17 @@ export const WIRE_FLOOR = '0.20.3'
172
172
  * current records service; below it, a runtime **does not work** — not "is
173
173
  * unsupported".
174
174
  *
175
- * ⛔ **Named `ISOLATE_API_FLOOR` until 2026-09-06, and the name was wrong twice
176
- * over**: the API map is only one of its inputs, and "floor" said nothing about
177
- * what falls below it. *[Diego: "I wasn't convinced by `isolateApiFloor` when it
178
- * was introduced."]* ⭐ **`usable` is a claim of FACT, and it is chosen to resist
179
- * a drift** — raise this for an incompatibility, never for a feature, a fix or a
180
- * preference, and a name that says *usable* makes the wrong reason read wrong.
181
- * On the wire it is `minUsable`.
175
+ * ⛔ **The earlier name was wrong twice over, and was replaced 2026-09-06**: the
176
+ * API map is only one of its inputs, and "floor" said nothing about what falls
177
+ * below it. **[Diego, 2026-09-06]** was not convinced by it and said changing it
178
+ * was easy — which removed the only cost the argument for keeping it rested on.
179
+ * ⭐ **`usable` is a claim of FACT** — below it a runtime does not work, rather
180
+ * than merely being unsupported.
181
+ *
182
+ * ⚠️ **The drift that name was chosen to resist was RELAXED 2026-09-12** — see
183
+ * `WIRE_FLOOR` above: while pre-1.0 the floor may be raised simply so nobody has
184
+ * to check what a version supports, so a raise no longer implies a break at the
185
+ * new number. **On the wire it is `minUsable`, and that is the only spelling.**
182
186
  */
183
187
  export const MIN_USABLE_RUNTIME = [WIRE_FLOOR, ...Object.values(ISOLATE_API)]
184
188
  .filter((v) => v !== UNRELEASED)