Skip to content

V1.1.0

Latest

Choose a tag to compare

@EgbertLudema EgbertLudema released this 12 Jun 15:52

MemoryVault Community Edition v1.1.0 expands the self-hosted app with Open When Messages, a recipient account area, delivery claiming, stronger app-managed encryption coverage, and a more complete guided experience across the app.

This release keeps the same Community Edition promise: a private, self-hosted MemoryVault deployment with no product feature limits in Community Edition entitlements.

For this release, Community Edition adds:

Open When Messages

  • New Open When Messages section in the app
  • Create, edit, and delete personal messages for future moments
  • Built-in templates such as “Open when you miss me”, “Open when you need advice”, “Open on your birthday”, and more
  • Link each Open When message to one or more loved ones
  • Add optional trigger dates
  • Mark messages as allowed to send on a chosen date even while the vault owner is still active
  • Add optional photo attachments to Open When messages
  • Color and icon selection for organizing message types
  • Open When message API endpoints
  • New Payload collection for Open When Messages
  • Open When Messages included in recipient delivery data

Recipient area

  • New Recipient section in the app
  • Recipients can keep delivered content available inside their own MemoryVault account
  • Recipient dashboard showing shared collections
  • Recipient collection pages for shared memories and Open When Messages
  • Recipient-specific navigation, breadcrumbs, and content views
  • Claimed deliveries are linked to the recipient user account
  • Existing logged-in users can claim a delivery
  • New recipients can create an account directly from a delivery link

Legacy delivery improvements

  • Legacy delivery pages now support both memories and Open When Messages
  • Delivery unlock flow has been expanded with account-claim support
  • Recipient delivery content now includes owner display information and owner profile image support
  • Shared memory titles and notes are resolved through the encrypted-field helpers
  • Open When Messages are included when building delivery payloads for linked loved ones
  • Trusted contact “passed away” confirmation now uses an explicit hold-to-confirm step before triggering delivery
  • Check-in confirmation responses now redirect to a dedicated confirmation page
  • Legacy deliveries can now store the recipient user that claimed the delivery

Encryption and privacy improvements

  • Added encrypted storage support for Open When message title, prompt, and message body
  • Added encrypted storage support for memory titles
  • Added encrypted storage support for loved-one custom notes
  • Added shared encrypted-field helpers for encrypting, decrypting, and serializing sensitive app content
  • Media encryption-related fields are now hidden in Payload Admin to reduce accidental editing
  • Legacy and recipient delivery views now decrypt app-managed encrypted content before rendering

Memories improvements

  • Memory creation and editing validation has been tightened
  • Clearer validation messages for missing title, missing content, missing recipients, and missing loved ones
  • Added support for changing uploaded media inside memory editing
  • Added quick path to add a loved one while creating or editing a memory
  • Memory APIs now handle encrypted title/content serialization paths
  • Memory media access handling has been improved for shared and delivered content
  • Memory list and card behavior received UI refinements

Loved ones improvements

  • Loved-one forms now support encrypted custom notes
  • Loved-one directory cards and group controls received UI refinements
  • Loved-one recipient preview flow has been improved
  • Loved-one export now uses the updated encrypted/sensitive field handling
  • Added recipient preview guidance from loved-one cards

Dashboard and navigation updates

  • Dashboard now includes Open When Messages as a first-class content type
  • Added dashboard action for writing an Open When message
  • Added trusted-contact setup status when legacy protection is active
  • Updated welcome copy and dashboard stat presentation
  • App shell and sidebar now include Open When Messages and Recipient navigation
  • Mobile navigation has been expanded with Open When, Recipient, menu, and close-menu states
  • Layout behavior has been improved for smaller screens

Onboarding and help tours

  • Added Open When Messages help tour
  • Added Recipient area help tour
  • Expanded dashboard intro tour with trusted-contact setup and navigation guidance
  • Expanded memories tour with memory card/open/edit guidance
  • Expanded loved-ones tour with recipient preview guidance
  • Improved app help button and tooltip behavior
  • Updated English and Dutch translations for the new flows

Admin and schema updates

  • Added Open When Messages to Payload config
  • Added migration for Open When Messages
  • Added migration for recipient user links on legacy deliveries
  • Updated generated Payload types
  • Updated Payload Admin custom styling
  • Updated Payload import map for the new admin/component state

Limits and entitlement plumbing

  • Added Open When Messages limit plumbing
  • Added Open When photo feature key
  • Added storage limit plumbing
  • Community Edition continues to return no enforced product feature limits by default

Dependencies and project maintenance

  • Pinned @payloadcms/storage-s3 to 3.84.1
  • Added scripts for encrypting sensitive content:
    • encrypt:sensitive-content
    • encrypt:sensitive-content:live
  • Updated package lock data
  • Removed test.env from the repository
  • Updated app-managed encryption documentation

Upgrade notes

  • This release adds new database migrations:
    • 20260601_130000_add_open_when_messages
    • 20260601_140000_add_recipient_user_to_legacy_deliveries
  • Run the project’s normal migration/startup flow before using the new Open When Messages and recipient claiming features.
  • If you already have existing memories or loved-one notes, review the new sensitive-content encryption scripts before enabling or migrating encrypted-field storage in a live deployment.