Support group messaging and unify website footers - #515
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
Group conversations can now be explicitly enrolled through GhostGet’s owner messaging host for Beeper, iMessage, and WhatsApp. Direct conversations remain the default, and clients negotiate support before requesting groups.
Each group enrollment binds one account, conversation, and complete participant list. A positively observed change permanently disables the enrollment and revokes its sends, including after restoration or restart. New enrollments begin with new messages, and providers recheck the binding at the final send boundary.
Website footers now use one product navigation row, compact analytics preferences, and a panel that stays inside the viewport. The change removes duplicate project-information rows from all 32 templates and retains the unique agent-documentation link. Release preparation uses the separately reserved 0.18.71 version and preserves all published 0.18.66–0.18.70 source and release notes.
Validation:
The protected-main join preserves the legacy body-free WhatsApp projection repair without changing group enrollment or native dispatch authority. All historical notes through 0.18.70 remain verbatim; group automation and the footer changes are reserved for 0.18.71. Final delivery requires current-head CI, merged-source CI, immutable publication, and production verification.