@getmicdrop/venue-calendar 4.3.127 → 4.3.128

package/dist/{widget-key-context-DaVnGw3w.js → widget-key-context-B-rITlo1.js}

@@ -1,5 +1,5 @@
 import { g as e, v as t } from "./sizing-B7ixYndz.js";
-import { E as n, N as r } from "./defaultLabels-Bs-Aev13.js";
+import { E as n, N as r } from "./defaultLabels-B0ug1Vhr.js";
 import { n as i } from "./Button-VUB2WJ88.js";
 import { n as a, t as o } from "./normalizers-CqGXhPZo.js";
 import { E as s, S as c, T as l, n as u, o as d, r as f, s as p, x as ee } from "./client-BxgiVv8K.js";

package/dist/{zh-BlnjAnmE.js → zh-pihqmu9w.js}

@@ -120,6 +120,7 @@ var e = {
 	loadingYourOrder: "正在加载您的订单...",
 	loadingSecurePaymentForm: "正在加载安全支付页面...",
 	errorPrefix: "错误：",
+	back: "返回",
 	goBack: "返回",
 	goBackToCalendar: "返回日历",
 	goBackToEventDetails: "返回活动详情",

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.127",
+  "version": "4.3.128",
   "description": "A customizable Svelte calendar component for displaying comedy events",
   "type": "module",
   "types": "./dist/types/index.d.ts",