@civitai/blocks-react 0.56.0 → 0.56.1

package/README.md

@@ -1586,8 +1586,8 @@ Runnable, minimal blocks — one per feature, each with its own README:
 
 | `@civitai/blocks-react` | pairs with `@civitai/app-sdk` | adds |
 |---|---|---|
-| `0.50.x` | `^0.40.0` | `useCreatePostFromApp()` (`CREATE_POST_FROM_APP`) + the `posts:write:self` scope. 🔴 Same wide `peerDependencies` floor as the row below, so **npm will not warn you**: pairing this with an SDK below `0.40.0` fails at `tsc` with `Cannot find name 'BlockCreatePostHostError'`, not at install. |
-| `0.48.x` | `^0.38.0` | `useCollectionFollow()` + `<FollowButton>` / `<TipButton>` (`SET_COLLECTION_FOLLOW`). 🔴 The `peerDependencies` floor stays the deliberately-wide `>=0.29.0 <1.0.0` (#206 — a per-minor floor forced a major on consumers), so **npm will not warn you**: pairing this with an SDK below `0.38.0` fails at `tsc` with `Cannot find name 'BlockCollectionFollowErrorCode'`, not at install. |
+| `0.50.x` | `^0.40.0` | `useCreatePostFromApp()` (`CREATE_POST_FROM_APP`) + the `posts:write:self` scope. Pairing `0.50.x` with an SDK below `0.40.0` fails at `tsc` with `Cannot find name 'BlockCreatePostHostError'`, not at install. |
+| `0.48.x` | `^0.38.0` | `useCollectionFollow()` + `<FollowButton>` / `<TipButton>` (`SET_COLLECTION_FOLLOW`). Pairing `0.48.x` with an SDK below `0.38.0` fails at `tsc` with `Cannot find name 'BlockCollectionFollowErrorCode'`, not at install — the floor those releases declared was deliberately wide (#206 — a per-minor floor forced a major on consumers). |
 | `0.36.x` | `^0.27.0` | auto-installs the SDK's opaque-origin web-storage shim (`@civitai/app-sdk/safe-storage`) on import |
 | `0.29.x` | `^0.24.0` | `useAppWorkflows()` — app generator subqueue read + cancel (`QUERY_APP_WORKFLOWS` / `CANCEL_APP_WORKFLOW`) |
 | `0.27.x`–`0.28.x` | `^0.23.0` | async-scan image upload; transport validators for all `SHARED_*` / `APP_STORAGE_*` / picker replies |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@civitai/blocks-react",
-  "version": "0.56.0",
+  "version": "0.56.1",
   "description": "React hooks and iframe transport for Civitai Apps. Pairs with @civitai/app-sdk/blocks.",
   "license": "MIT",
   "type": "module",
@@ -35,153 +35,10 @@
     "node": ">=20"
   },
   "dependencies": {
-    "@civitai/components": "0.4.2",
-    "@civitai/theme": "0.3.1"
+    "@civitai/theme": "0.3.1",
+    "@civitai/components": "0.4.2"
   },
-  "comment-peerDependencies": [
-    "The @civitai/app-sdk floor is DERIVED, not chosen: it is the lowest published",
-    "version that exports every symbol this package imports from the peer.",
-    "",
-    "🔴 RAISED 0.47.0 -> 0.49.0 (THE FOURTH TIME: #309, #317, #344, then this) when",
-    "`internal/mockHost.ts` began importing four NEW peer VALUE symbols --",
-    "`APP_STORAGE_ERROR_VALUE_TOO_LARGE`, `APP_STORAGE_ERROR_USER_QUOTA_EXCEEDED`,",
-    "`APP_STORAGE_ERROR_USER_ROW_LIMIT` and `APP_STORAGE_ERROR_REQUEST_FAILED`, the",
-    "host's own storage-rejection messages, which it now emits instead of the invented",
-    "`PAYLOAD_TOO_LARGE` / `STORAGE_UNAVAILABLE` (#343). All four ship for the first",
-    "time in the app-sdk minor released alongside this change.",
-    "",
-    "HOW 0.49.0 WAS DERIVED (computed, not predicted from release ordering) -- the same",
-    "three steps as 0.47.0 below, RE-RUN after this branch was rebased onto 8971ba3",
-    "(`chore(release): version packages (#365)`), because a rebase invalidates the base:",
-    "  - in-tree `packages/civitai-app-sdk/package.json` is 0.48.0, and 0.48.0 is also",
-    "    `npm view @civitai/app-sdk version` -- nothing is mid-flight. #365 bumped only",
-    "    @civitai/blocks-react (0.55.0 -> 0.55.1) and @civitai/components; app-sdk did",
-    "    not move.",
-    "  - `git ls-tree -r origin/main .changeset/` shows main carries NO pending",
-    "    changesets at all -- #365 consumed every one -- so this branch's changeset is",
-    "    the only input to the next release plan.",
-    "  - `pnpm exec changeset status --verbose` on this branch prints",
-    "    `@civitai/app-sdk 0.49.0` (and `@civitai/blocks-react 0.56.0`).",
-    "There is no published tarball to probe for these four: they do not exist on npm",
-    "yet. That is the same position #344 was in, and the same derivation is used.",
-    "",
-    "🔴 SO 0.49.0 IS A PREDICTION, AND IT IS PINNED AS ONE. The four symbols are",
-    "declared in `PEER_SYMBOLS_PREDICTED_BY_THIS_BRANCH` in",
-    "`tests/guards/blocks-react-peer-floor.test.mjs`; its `PREDICTED ENTRY` test",
-    "re-derives the version from the tree on every run and requires BOTH that the",
-    "ledger entries name it and that this floor equals it exactly. If another app-sdk",
-    "minor publishes first, the computed version becomes 0.50.0 and that test goes RED",
-    "-- where every other assertion in the file stays green on the stale number, which",
-    "is #344's shape for a fourth time. Delete the four from that list and re-measure",
-    "against the real tarball once this release has actually published.",
-    "",
-    "⚠️ `changeset status` now logs `Package \"@civitai/blocks-react\" must depend on the",
-    "current version of \"@civitai/app-sdk\": \"0.48.0\" vs \">=0.49.0 <1.0.0\"`. That is",
-    "EXPECTED and not a failure (rc=0, and the release plan still prints): the floor",
-    "names the version this PR's own changeset publishes, which by construction does not",
-    "exist yet. #344 raised the floor to 0.47.0 from an in-tree 0.46.0 in exactly the",
-    "same way, logged the same line, and published. No CI job runs `changeset status`",
-    "-- tracked as #367, and the guard above is the tree-local mitigation, not a fix.",
-    "",
-    "🔴 RAISED 0.45.0 -> 0.47.0 (THE THIRD TIME THIS CLASS HAS BITTEN: #309, then",
-    "#317 caught it in review, then this) when `internal/mockHost.ts` began importing",
-    "three NEW peer VALUE symbols -- `APP_STORAGE_MAX_BYTES`, `APP_STORAGE_MAX_ROWS`",
-    "and `APP_STORAGE_MAX_VALUE_BYTES`, the App Storage ceilings, which it assigns to",
-    "its mock storage defaults. All three ship for the first time in the app-sdk minor",
-    "released alongside this change.",
-    "",
-    "HOW 0.47.0 WAS DERIVED (computed, not predicted from release ordering):",
-    "  - in-tree `packages/civitai-app-sdk/package.json` is 0.46.0, and 0.46.0 is also",
-    "    `npm view @civitai/app-sdk version` -- the tree is at the last published",
-    "    version, so nothing is mid-flight.",
-    "  - the pending changeset set is exactly ONE file, `.changeset/",
-    "    app-storage-real-ceilings-2026-09-19.md`, declaring `@civitai/app-sdk: minor`;",
-    "    `git ls-tree -r origin/main .changeset/` shows main carries no others.",
-    "  - `pnpm exec changeset status --verbose` on this branch prints",
-    "    `@civitai/app-sdk 0.47.0` (and `@civitai/blocks-react 0.54.0`). That is the",
-    "    tool that will actually run, answering with the number it will actually write.",
-    "",
-    "MEASURED, both directions, against the REAL tarballs (not the workspace copy):",
-    "  - published 0.46.0 -- which the OLD `>=0.45.0` range SATISFIED, installing with",
-    "    no peer warning at all -- does not export any of the three. `node -e` on a",
-    "    scratch `npm i @civitai/app-sdk@0.46.0`:",
-    "      SyntaxError: The requested module '@civitai/app-sdk/blocks'",
-    "        does not provide an export named 'APP_STORAGE_MAX_BYTES'",
-    "    Controls were run BOTH ways before believing that zero: an impossible symbol",
-    "    reported absent (the probe can go red) and `BrowsingLevel`/`SFW_LEVELS`",
-    "    resolved (the probe can see a symbol that IS there).",
-    "  - blast radius is the `./testing` subpath ONLY, and that is measured too, by",
-    "    `pnpm pack`ing this package and importing both entries against 0.46.0:",
-    "    `@civitai/blocks-react` resolved 61 exports fine; `@civitai/blocks-react/",
-    "    testing` threw the SyntaxError above out of `dist/internal/mockHost.js`.",
-    "    `src/testing.tsx` reaches `mockHost`, `src/index.ts` does not -- so the block",
-    "    boots and every dev harness and downstream test suite dies instead.",
-    "  - with the floor at 0.47.0, that same install is refused: npm reports",
-    "    ERESOLVE against `@civitai/app-sdk@0.46.0`.",
-    "",
-    "⚠️ THE RESIDUAL RISK IS RELEASE ORDERING, AND IT IS NOT REMOVABLE FROM HERE.",
-    "0.47.0 is the version THIS changeset publishes from THIS base. If another app-sdk",
-    "minor merges and publishes before this PR does, 0.47.0 ships WITHOUT the",
-    "constants, this changeset publishes 0.48.0, and this range admits a broken",
-    "version -- #309's shape exactly. So: RE-RUN `changeset status --verbose` after any",
-    "rebase onto a moved main, and re-read this range. The number here is a",
-    "measurement of a base, and a rebase invalidates the base.",
-    "",
-    "🔴 `changeset version` WILL NOT FIX A STALE FLOOR -- IT IS NOT A BACKSTOP.",
-    "`.changeset/config.json` sets `onlyUpdatePeerDependentsWhenOutOfRange: true`, so a",
-    "peer range is rewritten ONLY when the computed version falls OUT of it. A floor",
-    "that is too LOW is, by construction, still satisfied -- so it is left exactly as",
-    "it is and ships stale. (The flag does bite in the other direction, which an",
-    "earlier note recorded: run before a rebase, when the computed version is BELOW the",
-    "declared floor, it rewrites the range DOWNWARD and drops the upper bound. Both",
-    "readings say the same thing -- never let this number be the flag's problem.)",
-    "",
-    "🔴 A PEER RANGE IS METADATA AND NOTHING CHECKS IT AGAINST THE CODE. 0.49.0-0.51.0",
-    "declared >=0.29.0 while importing `effectiveBrowsingCeiling` (app-sdk 0.39.0) and",
-    "the create-post types (0.40.0). The range was SATISFIED, so no install warned;",
-    "the failure landed at module evaluation in a consumer's tests, where 27 of 43",
-    "test files collected ZERO tests -- 292 tests stopped running and the summary line",
-    "reported no failures. See #309. NO BUILD OR TYPECHECK CAN CATCH THIS:",
-    "`pnpm.overrides` maps the peer to the workspace copy, so every in-repo typecheck,",
-    "test and build resolves the symbol from `packages/civitai-app-sdk` and is",
-    "structurally blind to whatever this range says.",
-    "",
-    "🔴 SINCE #344 ONE GATE DOES SEE PART OF IT: `tests/guards/",
-    "blocks-react-peer-floor.test.mjs` fails when this range admits an app-sdk version",
-    "measured NOT to export the App Storage constants, and when the derivation below",
-    "stops being recorded here. Read its KNOWN LIMITS before relying on it -- CI checks",
-    "out at `fetch-depth: 1` and the guard job has no registry access, so it is",
-    "offline and tree-local: it re-asserts a measurement taken by hand, it does not",
-    "take one. The steps below are still the only way to MAKE the measurement.",
-    "",
-    "🔴 AND #309'S OWN SUGGESTED FLOOR (>=0.39.0) WAS WRONG. `effectiveBrowsingCeiling`",
-    "arrives in 0.39.0, but `BlockCreatePostRequest`, `BlockCreatePostResult`,",
-    "`BlockCreatePostHostError` and `BlockPostSource` arrive in 0.40.0, and there is no",
-    "0.39.x patch between them. Landing the issue's number would have closed it and",
-    "stayed broken. Do not take a floor from a ticket.",
-    "",
-    "TO RE-DERIVE IT (do this when this package starts importing a new peer symbol):",
-    "  1. collect the symbols -- every named `import`/`export … from '@civitai/app-sdk*'`",
-    "     clause in src/, plus bare and star forms, which name a SUBPATH and no symbols",
-    "     but still have to resolve. Measured at #344: 64 distinct symbols over 2",
-    "     subpaths ('/blocks' and '/safe-storage'), counting unique names across every",
-    "     named import clause in src/**/*.ts{,x}. An earlier derivation recorded 62;",
-    "     re-count rather than trusting either figure.",
-    "  2. in a scratch dir OUTSIDE this workspace (pnpm would resolve the peer to the",
-    "     workspace copy and measure nothing), `npm i @civitai/app-sdk@<version>` and",
-    "     typecheck a file importing all of them -- each in the POSITION it is imported",
-    "     in here, since a type-only export satisfies a plain value import and that is",
-    "     the #309 failure mode itself.",
-    "  3. the floor is the lowest version with zero missing. Confirm the version BELOW",
-    "     it is missing something, or the floor is higher than it needs to be.",
-    "  4. include a symbol you know does not exist, and check it reports. A run that",
-    "     finds nothing is indistinguishable from one wired to nothing.",
-    "",
-    "A 584-line script that automated this was written and then cut: three audit rounds",
-    "found defects in the SCRIPT while the floor value it derived never changed, and",
-    "nothing in the repo ran it. The derivation is rare and the number is recorded here;",
-    "the tool was the expensive half."
-  ],
+  "comment-peerDependencies": "This floor is DERIVED, not chosen — the lowest published app-sdk that exports every symbol this package imports. Do not edit it without reading ./PEER_FLOOR.md (in-repo, unpublished) and tests/guards/blocks-react-peer-floor.test.mjs.",
   "peerDependencies": {
     "@civitai/app-sdk": ">=0.49.0 <1.0.0",
     "react": "^18.0.0 || ^19.0.0"