Skip to content

✨ meetings: Settings, Meeting attendee Email section wired to email-in (Betty C2 part 6) - #18487

Merged
hivecommons-hive[bot] merged 1 commit into
v5from
feat/18395-attendee-email
Nov 16, 2026
Merged

hivecommons-hive[bot] merged 1 commit into
v5from
feat/18395-attendee-email

Conversation

@clubanderson

Copy link
Copy Markdown
Member

Part 6 of #18395 (Betty C2, email in): wires the Email section of Settings, Meeting attendee (#18417) to email-in (#18431, #18471).

  • SetMailAllowlist now also installs a MeetingsAttendeeEmail (api_meetings_email_attendee.go), so the section reports available: true: each user's calendar emails with proof status (verified with time, or pending), the mail-in files waiting for the owner, and the effective meetings.email.* switches. Invites waiting for approval stay in the Calendar, where they are approved.
  • My calendar emails: each signed-in user adds, sees the proof code and instruction for, and removes their own addresses (/api/meetings/calendar-emails); a failed proof (wrong sender, no DMARC alignment) and an address whose user lost access are shown.
  • Switches: "Accept calendar invites" and "Accept mailed-in files" are live for the owner and saved with Save through an optional email block on PUT /api/meetings/persona (403 for anyone else; a persona save without the block leaves them alone). Both carry their meetings.email.* yaml hints, so the settings-parity allowlist entries added in ✨ meetings: email invites with an allowlist of proven calendar emails (Betty C2 part 4) #18431 are removed.
  • meeting_attendee_ui_test.go extended for the new markup; static/index.html regenerated; meetings.md and api-reference.

🤖 Generated with Claude Code

…n (Betty C2, part 6)

The Email section of Settings, Meeting attendee (#18417) is live once the
calendar email allowlist is wired: SetMailAllowlist installs a
MeetingsAttendeeEmail that reports each user's calendar emails with
proof status (verified/pending), the mail-in files awaiting approval and
the meetings.email switches. Each user adds, proves (code and
instruction shown) and removes their own addresses under My calendar
emails (GET/POST/DELETE /api/meetings/calendar-emails). The owner's
switches save through PUT /api/meetings/persona with an optional email
block (owner only, 403 otherwise). static/index.html regenerated;
meetings.md and api-reference.

Part of #18391, #18395.

Signed-off-by: Andy Anderson <andy@clubanderson.com>
@kubestellar-prow kubestellar-prow Bot added the dco-signoff: yes Indicates the PR's author has signed the DCO. label Nov 16, 2026
@kubestellar-prow

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign kellyaa for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubestellar-prow kubestellar-prow Bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Nov 16, 2026
@hivecommons-hive
hivecommons-hive Bot merged commit 6a4fd4c into v5 Nov 16, 2026
91 of 96 checks passed
@kubestellar-prow
kubestellar-prow Bot deleted the feat/18395-attendee-email branch November 16, 2026 20:41
@hivecommons-hive

Copy link
Copy Markdown
Contributor

Hive status — updated in place; edits do not notify. Full history is in the Activity Monitor.

Evidence bundle `#184871d9620a` sha256:71918b97adc5cafa3da33d76e37e81aa3060306ada116fd3ca12cc825f10a40a — download from the dashboard or `hivectl review evidence #18487`.

@hivecommons-hive

Copy link
Copy Markdown
Contributor

merged by Hive trusted-author auto-merge: author @clubanderson holds role owner and GitHub permission admin on repo; CI green at 1d9620a.

@clubanderson clubanderson added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Nov 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has signed the DCO. lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant