@getmicdrop/venue-calendar 4.3.2 → 4.3.4

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@getmicdrop/venue-calendar",
   "_version_comment": "4.1.55 was the last PUBLISHED version, and the tree carried 36 commits npm's 4.1.55 does not have — including the gate-password security fix and four money fixes. A filename must never reuse a version npm has taken (jsDelivr/unpkg cache the FIRST bytes they see under `@4.1.55` forever, so republishing that number ships the old widget to every venue that pinned it). Bumped to 4.2.0 here, BEFORE anything is built for publish. `npm run release:preflight` refuses to proceed when this number already exists in the registry.",
-  "version": "4.3.2",
+  "version": "4.3.4",
   "description": "A customizable Svelte calendar component for displaying comedy events",
   "type": "module",
   "types": "./dist/types/index.d.ts",
@@ -154,7 +154,7 @@
   "_devDependencies_pin_comment": "Three EXACT pins in here are load-bearing and must not be re-caretted by a dependency bot. (1) `@getmicdrop/svelte-components` — the ES/UMD/IIFE builds do NOT externalize SC, so it is COMPILED INTO every shipped artifact. RESTORED TO AN EXACT PIN 2026-08-23, having drifted back to a caret at some point between 6.24.311 and 6.24.316 — exactly the re-caretting this note warns about, which is worth knowing recurs. Under a caretted range like `^6.24.311` the SC version a venue's browser executes is whatever the range floats to on the publish machine at publish time, which is not recorded anywhere and is not reproducible after the fact; the `overrides` block below cannot help (it only ever covered esbuild, and consumers ignore a dependency's overrides entirely). Pinned exact so the artifact and the manifest agree, and vite.config.lib.js stamps the resolved version into the bundle as __VC_SC_VERSION__ so a venue's devtools can answer 'which SC is this?'. (2) `svelte` — the compiler whose private internal/client calls the pre-compiled dist binds to. `^5.56.9` let the compiler move under a peer range that stayed still; see _peerDependencies_comment. (3) `@stripe/stripe-js` in dependencies — see its own note there.",
   "devDependencies": {
     "@eslint/js": "^10.0.1",
-    "@getmicdrop/svelte-components": "6.24.333",
+    "@getmicdrop/svelte-components": "^6.24.334",
     "@playwright/test": "^1.60.0",
     "@size-limit/file": "^13.0.3",
     "@sveltejs/adapter-auto": "^7.0.1",