@go-labs-sg/rsvp 0.12.0 → 0.13.0

package/dist/index.js

@@ -5595,7 +5595,7 @@ var ensurePrivateCredentialLockDirectory = async () => {
     return directoryStat;
   };
   const directoryStat = await inspectDirectory();
-  if ((directoryStat.mode & 63) !== 0) {
+  if (process.platform !== "win32" && (directoryStat.mode & 63) !== 0) {
     await chmod(directory, 448);
     const securedDirectoryStat = await inspectDirectory();
     if ((securedDirectoryStat.mode & 63) !== 0) {

package/examples/amgen-rsvp-copy/README.md

@@ -0,0 +1,78 @@
+# Amgen public registration page copy
+
+`public-page-patch.json` contains only the intended public-page settings. It is
+not a standalone `event setup update` payload. That command requires a complete
+revision-checked setup payload, including the current event identity and
+configuration version. The API merges supplied `publicPage` keys into the
+saved object, so keeping this patch to the three requested keys preserves the
+event's existing registration description and other public-page settings.
+
+## Refresh each event before preparing an update
+
+Use the authenticated Registration CLI and the Amgen organization ID to find
+the official and test event IDs by their current slugs. Do this independently
+for each event; do not copy an ID or version from an older example or from the
+other event. The slugs are `amgen-dinner-and-dance-2026` (official) and
+`amgen-dinner-and-dance-2026-test` (test).
+
+```sh
+rsvp event list --organization-id <amgen-organization-id>
+rsvp event get --organization-id <amgen-organization-id> --event-id <event-id>
+```
+
+From each fresh `event get` response, record `configurationVersion` and build a
+complete setup input using the current values. The `version` field must equal
+that `configurationVersion`. Supply required fields: `accessMode`,
+`allowedEmailDomains`, `employeeIdMatchingEnabled`, `guestPolicy`, `name`,
+`organizationId`, `eventId`, `personalEmailPolicy`, `retentionMonths`,
+`seatHoldMinutes`, `seatingAssignmentMode`, `seatingMode`, `slug`, `status`,
+`timeZone`, `waitlistEnabled`, `waitlistOfferTtlMinutes`, and `walkInsEnabled`.
+Also include optional values that must be retained. In particular, map
+`capacityLimit` from the event's `capacityState.capacityLimit` (or
+`metadataJson.capacityLimit`) because omitting it clears the configured limit;
+map `guestPolicyJson` to `guestPolicy`; retain nullable date fields and
+`description` because omitted dates become null and omitted `description` is
+cleared. Retain `dietaryClosesAt`, `endsAt`, `rsvpClosesAt`, `rsvpOpensAt`,
+`startsAt`, and `venueName`, including their current null values. Omit
+`checkInQrRelease` from this copy-only setup payload. The API preserves its
+stored policy, including the absence of an explicit policy, when this field is
+omitted. The top-level value returned by `event get` can be an inferred fallback;
+submitting it would persist that fallback as a new explicit policy. For
+`publicTheme`, use the stored `metadataJson.publicTheme` values rather than the
+display-resolved `publicTheme` object, which can contain a non-input image URL.
+Keep existing `publicPage` values from `metadataJson.publicPage`.
+
+Keep each event's current dates, registration windows, status, capacity limit,
+and QR release configuration unchanged. Do not change schedule or
+status fields as part of this copy update. Merge only the three values from
+`public-page-patch.json` into the current `publicPage` object. Omitted
+`publicPage` keys are preserved by the setup API merge. Explicitly retain the
+setup fields that omission clears, as listed above; omit `checkInQrRelease` to
+keep the stored policy unchanged.
+
+The currently published schedule governs whether registration is open. If an
+event is closed under its existing schedule, do not alter the schedule to make
+the page appear open; defer validation of the open-page copy until the existing
+schedule permits it. `showDeadlineNotice: true` retains the deadline notice,
+while the separately implemented `showResponseUpdateNotice: false` hides only
+the update-response sentence.
+
+The official page currently shows “Registration not open”; this patch does not
+override that state. If the setup API refuses an update because the event is
+completed, cancelled, or archived, stop rather than changing its status.
+
+## Apply after the compatible deployment
+
+The `showResponseUpdateNotice` setting must be supported by the deployed API
+and web app before applying this payload. Once the compatible version is
+deployed, inspect the prepared full payload, then apply it separately to each
+event using its freshly read ID and version:
+
+```sh
+rsvp event setup update \
+  --allow-state-change \
+  --target <event-id> \
+  --payload "$(cat event-setup-current.json)"
+```
+
+This command is documented for later use and was not executed for this task.

package/examples/amgen-rsvp-copy/public-page-patch.json

@@ -0,0 +1,7 @@
+{
+	"publicPage": {
+		"registrationActionLabel": "Click here to register",
+		"showDeadlineNotice": true,
+		"showResponseUpdateNotice": false
+	}
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@go-labs-sg/rsvp",
-  "version": "0.12.0",
+  "version": "0.13.0",
   "description": "RSVP CLI for authorized event operations.",
   "type": "module",
   "main": "./dist/index.js",