Repository navigation
Upstream 3/5: speaker portal, volunteers and exhibitor export (dddperth #175–#181) - #24
Merged
JakeGinnivan merged 6 commits intoOct 19, 2026
Conversation
…the Experts schedule email Upstreamed from dddwa/dddperth#175 (fork merge bd04c69). Visual baselines are left fork-local. - feat(admin): speaker RSVP lists, Meet the Experts schedule email, day-details email - feat(admin): editable speaker settings at /admin/settings/speakers
Upstreamed from dddwa/dddperth#176 (fork merge e28bef9). Visual baselines are left fork-local. - fix(admin): read queued planner saves as JSON, not the page's HTML - feat(admin): volunteer roster for room coordinators and photographers
Upstreamed from dddwa/dddperth#179 (fork merge ff63280). Visual baselines are left fork-local. - fix(portal): explain an unlinked email instead of "something went wrong"
…off digital and in-kind sponsors Upstreamed from dddwa/dddperth#180 (fork merge 7d149e0). Visual baselines are left fork-local. - feat(sponsors): loading dock attendees column in exhibitor export - feat(sponsors): leave digital and in-kind sponsors off the exhibitor export
…order Upstreamed from dddwa/dddperth#181 (fork merge 376383f). Visual baselines are left fork-local. - feat(sponsors): room, space number and screen order in exhibitor export
Two more tests from the fork assumed DDD Perth's configuration: - getExhibitorLogistics reads the conference's real Jira field mappings. Gate it on a configured sponsor portal, like the other Jira suites. - The speaker settings tests hardcoded Perth's +08:00 offset. The behaviour under test is "parse in the conference's timezone", so derive the expected instant from the manifest's timezone instead. It still catches a server-timezone parse in any conference whose zone isn't the server's.
JakeGinnivan
force-pushed
the
jakeginnivan/upstream-3-speaker-portal-volunteers
branch
from
October 19, 2026 01:47
130705b to
5721e18
Compare
JakeGinnivan
deleted the
jakeginnivan/upstream-3-speaker-portal-volunteers
branch
October 19, 2026 02:08
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
3/5 of the upstream catch-up. Speaker portal, volunteers and exhibitor export, fork PRs #175, #176 (including #177), #179, #180 and #181.
One commit is new here (130705b).
speakers.test.tshardcoded Perth's+08:00, so it now derives offsets frompublic.timezone.getExhibitorLogisticstests are gated on the sponsor portal being configured.Evidence
After: build, typecheck, lint, unit tests, e2e (55 passed) and
pnpm vr(81 passed) all pass. Visual baselines are unchanged.Merge Danger
Door: one-way
Adds D1 migrations 0026–0027.
Blast Radius: portals
Note that in the stub, server time and conference time are both UTC, so
speakers.test.tscan't tell them apart there. Forks in other timezones exercise that path.Part of a 5-PR stack that brings ddd-core up to date with every
core/change merged indddwa/dddperthsince #157. Each fork PR is replayed as one commit, credited to its author, with its fork PR number in the message. Merge the stack in order, starting at 1/5.