Platform Updates

Repositories: Partners, Partners API. Status: Released; signed-in hosted checks remain to verify.

What’s Changed: Asset Register links with malformed or excessively large page numbers now open safely while normal saved page and cursor links keep working. Settlement, finance, inventory, and registration payment QR images now load through the platform image proxy instead of exposing the media provider’s direct address.

Impact: Partner teams can continue using saved asset views and payment QR images. Invalid page numbers return to page one; no action is needed for ordinary links or uploaded images.

Upgrade Notes: The crafted asset link crashed the register before the fix. Direct-entry and register workflow checks, typecheck, and build pass afterward. Both dashboard hostnames serve the matching Asset Register asset from the linked release. API checks cover QR conversion, finance settlement behavior, inventory authorization, typecheck, and a dry Worker build. The matching Worker version is active for all traffic; unauthenticated settlement reads return 401. Signed-in hosted asset and payment workflows remain to verify.

Repositories: Partners API, Rego. Status: API released; signed-in hosted checkout remains to verify.

What’s Changed: A payment reference can now be reused only within the same attendee, event, provider, and purchase context. Shop usage also stays with the buyer who made it.

Impact: Attendees can retry their own checkout without losing a valid reference. Another account cannot claim or reuse that reference for a separate purchase.

Upgrade Notes: Before/after checks covered cross-account rejection, same-account retry, separate checkouts, race recovery, and registration and shop attribution. API typecheck and Worker dry build passed; Rego intent-key, typecheck, build, and route checks passed. The linked API production build passed, public Rego loaded, and unauthenticated API access returned 401. Authenticated hosted checkout and provider processing remain to verify.

Repository: Partners. Status: Released; signed-in hosted preview remains to verify.

What’s Changed: Registration previews now evaluate organizer-defined answer patterns with bounded, linear-time matching. Add-on images use the same managed-image rules as other form images, so unapproved external addresses are not loaded.

Impact: Organizers can keep previewing ordinary answer rules and managed images. A pattern that uses unsupported advanced regular-expression features must be rewritten using a supported pattern before it can be previewed.

Upgrade Notes: Before the change, a short crafted answer delayed validation for about a second, and an unapproved image address reached the add-on preview. Afterward, focused checks covered ordinary and crafted patterns, supported and blocked image addresses, form parity, typecheck, and build. The production dependency audit reported no advisories. The linked Cloudflare build succeeded; the custom and Pages hostnames serve the matching registration-runtime asset. A signed-in hosted preview remains to verify.

Repository: Partners. Status: Released; signed-in hosted exports remain to verify.

What’s Changed: Planning artifact, archive, audit, and calendar downloads now stop if the operator changes account, partner, or project while a file is being prepared. Current-workspace downloads still work.

Impact: Planning teams can continue using the same download controls. After changing workspace scope, start the download again for the new scope.

Upgrade Notes: Held-response browser checks reproduced old-workspace artifact, archive, and audit downloads before the fix. Afterward, focused checks covered those files and calendar exports for current and switched scopes. Existing Files, archive, and Settings browser workflows, typecheck, and build passed. A separate calendar UI fixture still times out on the unmodified baseline; the focused calendar export check passed. The linked production build succeeded, and both dashboard hostnames serve the matching planning assets. Signed-in hosted downloads remain to verify.

Repository: Partners. Status: Released; signed-in hosted downloads remain to verify.

What’s Changed: A registration attachment download now stops if the organizer changes account or partner while its file is still loading. Downloads for the current account continue normally.

Impact: EMS organizers can use the same attachment control. After switching accounts or partners, start the download again from the new context.

Upgrade Notes: A held-response browser check reproduced an old-account download before the fix. Afterward, current-account, aborted, account-switch, and partner-switch checks passed, along with the roster prefetch workflow, typecheck, and build. A separate source-ownership fixture times out on the same assertion on the unchanged baseline. Both dashboard hostnames serve matching production roster assets; signed-in hosted download remains to verify.

Repositories: Partners, Partners API. Status: Protected upload and link conversion released; retirement of older media copies remains in progress.

What’s Changed: Images pasted into a saved incident report now go through encrypted storage. Report previews and details load them through the dashboard session and current report access rules. Older dashboard tabs are also prevented from sending saved-report images through the former public uploader. This keeps the familiar paste and preview workflow for authorized reviewers.

Impact: Report authors and reviewers can keep using the same controls. Previously attached report images now use protected links in the report and its saved history; no operator action is needed.

Upgrade Notes: Local tests covered image paste, preview, detail, logout cleanup, FPH-admin upload, shared-viewer upload denial, and guest or revoked image reads. API and dashboard typechecks and builds passed. The linked Worker and dashboard production builds succeeded; both dashboard hostnames serve the new client asset. The earlier report’s five images load for an authorized dashboard session, and the same route rejects unauthenticated access. All stored report and revision links were converted; old media-copy removal and signed-in hosted paste remain to verify.

Repository: Partners. Status: Released; signed-in hosted downloads remain to verify.

What’s Changed: Feedback CSV and ZEP access bundle downloads now stop if the operator changes account or event while the file is being prepared. Downloads for the current account and event still work.

Impact: Event teams can keep using the same export controls. After switching accounts or events, start a fresh download for the new scope.

Upgrade Notes: A local browser check reproduced an old event’s feedback CSV downloading after an event switch before the fix. Afterward, browser checks confirmed current, event-switched, and account-switched behavior for both files. Existing feedback and registration-configuration workflows passed on desktop and mobile, along with typecheck and build. The linked production build succeeded and the live dashboard and deployment serve matching JavaScript. A signed-in hosted download remains to verify.

Repository: Partners. Status: Released; signed-in hosted downloads remain to verify.

What’s Changed: Ledger CSV and disbursement evidence downloads now stop if the signed-in person, partner, or selected record changes while the file is being prepared. An authorized download for the current partner still works.

Impact: Finance operators can use the same export and evidence controls. If they switch scope during a download, they can start a new download in the new scope.

Upgrade Notes: A local browser check reproduced an old partner’s CSV downloading after a scope change before the fix. Afterward, the same check blocked that download and confirmed the current partner’s export still worked. The finance overview and outflow browser checks, typecheck, and production build passed. The linked production build succeeded and the live dashboard serves its matching finance asset. A signed-in hosted download remains to verify.

Repositories: Partners, Partners API. Status: Released; signed-in delivery remains to verify.

What’s Changed: Partner notification settings now accept Discord webhook addresses only over HTTPS. The API also rejects previously saved HTTP addresses before sending a message, so webhook details are not sent over an unencrypted connection.

Impact: Partner teams using an HTTPS Discord webhook can continue receiving messages. A team with an HTTP webhook address must replace it with an HTTPS address to restore Discord delivery. Telegram targets and other notification settings are unchanged.

Upgrade Notes: Local checks reproduced HTTP acceptance before the fix and confirmed rejection afterward. The organization-settings browser workflow, API notification checks, typechecks, builds, and production dependency audits passed. Both linked production builds succeeded; the API has a new production deployment, and the dashboard deployment and custom domain serve matching asset names. Signed-in hosted delivery remains to verify.

Repository: Partners. Status: Released.

What’s Changed: Direct links to migrated administration pages now pass through a dedicated redirect that keeps the intended Admin page while discarding the original link’s query details. The Admin portal remains the home for platform administration.

Impact: Partners following an Admin link reach the same destination. Unrelated one-time codes or other details in the original link are no longer sent to Admin in the redirect address.

Upgrade Notes: No action is needed. Before the change, a hosted redirect forwarded extra query details. Local preview, hosted preview, production deployment, and production custom-domain checks after the change kept normal Admin destinations, dropped those details, and preserved public Rego redirects.