Repository navigation
New features
- You choose who sees each part of your profile. Every field and section in the profile form has
its own audience: everyone, members, your circle, or only you. The profile-wide setting, now at the
top of the form, is the default for anything you haven't set individually. A hidden field is removed
on the server, so it is also left out of search filters and keyword search rather than merely not
drawn. Details in docs/profile-visibility.md - Circles. Add members one by one to the circle that can see what you keep for people you trust.
Someone you have already talked with can ask to be added; requests and additions arrive in-app, by
push and by email - "View as" in your own profile's menu previews what a visitor, a member or someone in your circle
sees, and a notice on your profile says who it is currently visible to - Pause your profile instead of deleting it. What used to be "disable" now lives in Settings, and
the delete-account dialog offers it as the gentler option - /careers: open positions, with an application form and a
list of what you have applied to
Improvements
- The photo and video viewer swipes as a sliding strip: the next item follows your finger instead of
swapping in after the gesture - In the apps, a long press on an internal link no longer pops up its URL
- On wide screens the profile details column scrolls with the page instead of inside its own box, and
the actions menu stays above the photos - Live updates come back by themselves after a long session: a tab in use reconnects and fetches what
it missed, and your own profile comment shows up as soon as you post it - The Help Center and the delete-account page are rewritten and reorganised, in English, French and
German - Online communities on a profile carry a caption, so the text reads as an answer rather than a stray
block of links - The block dialog closes once the block or unblock went through, and stays open to retry if it failed
- Narrow pages are centred in the layout, and profile cards have a quieter hover
- Members who voted on or wrote a proposal can now delete their account. Their ballots go with it;
the proposal stays, without an author - Saving your profile recomputes compatibility once rather than once per changed field
- The feed carries whichever fields you made public; its separate visibility level is retired
- The privacy policy and terms describe the new visibility model
Fixes
- Removing or toggling a message reaction only affects your own, not everyone's on that emoji
- A slow signed-out request could replace your own profile with the redacted version until reload
- Direct links to members-only profiles said endorsements were off
- The data export no longer fails for an account without a profile, and includes every like and ship
- A deleted member no longer lingers in other members' likes, ships and search alerts
- Usernames containing
_or%are matched exactly
Trust & safety
- Banned profiles are redacted by the server, not only by the browser
- Banned and held accounts can no longer publish events, proposals or compatibility prompts
- Only admins can un-hide a comment, so an author cannot reverse a removal by a moderator or by the
profile's owner - The referrer on an account is fixed after signup, so referral counts cannot be inflated
- Event location links must be http(s), and sign-in redirects are validated before use
- Error pages no longer leak database details, and the anonymous rate limit keys on the real client
address
Backend & API
- Per-field visibility: a
profiles.field_visibilityjsonb of per-field exceptions and a
profile_accesstable for circles (requested,approved,removed; service-role only); newget-profile-access,set-profile-accessandrequest-profile-access
endpoints.helpers/profile-access.tsandhelpers/profile-visibility.tsredact in
get-user-and-profile,get-profiles(hidden fields dropped from filters and keyword search),
get-profile-feed, answers and comments; admins read in full. Blocking removes circle membership.
Newcircleemail - Careers:
apply-to-positionandget-my-job-applications, ajob_applicationstable with RLS,
Discord notification on submit - Websockets: connections are authenticated and private topics restricted to their owner behind
WS_ENFORCE_TOPIC_AUTH; profile-comment broadcasts are viewer-neutral so subscribers refetch with
access rules applied; the client reconnects after the session limit for tabs in use and refetches,
while idle tabs disconnect so the API can scale to zero - Compatibility: scoring consolidated into fewer SQL statements, score inserts batched with chunked
unnest, andupdate-profilebatches option writes and runs one recompute. Answer importance is
bounded to the supported range - Security pass: generic message for every 500, failed JWTs and API keys no longer logged, Cloud Run
detected fromK_SERVICEtoo, Discord webhooks sent with mentions disabled, anon inserts on
deleted_usersand anon reads ofuser_notificationsrevoked,user_eventsinsert-only for anon,
X-Frame-OptionsandPermissions-Policyon the web app, rejected Firebase tokens return 401
rather than 500,updateProfileno longer accepts anid, express 5.2.1 - Deleted members: likes and ships cascade,
delete-meclears search alerts, ballots cascade and
proposals keep a null author. Ban events are no longer written to the non-existentaudit_events - Staff checks for message and profile gates go through the shared
isStaff;messaging_statusis
dropped from the first-message fields; the unused prompt answer-count RPC is removed - Reply-to on emails is hello@compassmeet.com; Gemini model list updated
- API version 1.92.0 → 1.98.0
Database & deploys
- Migrations move to the Supabase CLI:
supabase/migrations/, starting from a baseline pulled from
prod, tracked per database insupabase_migrations.schema_migrations. Merging tomainapplies
them to dev, then prod, then deploys the API (cd-api.ymlbecomescd-backend.yml). The pre-CLI
SQL underbackend/supabaseis removed (tagpre-cli-migrations); the local stack is Postgres 17.
Seedocs/database-migrations.md - Drift cleanup: legacy
love_*objects renamed, missing indexes added, duplicate unique indexes
dropped (keeping whicheverprivate_user_message_channelskey the foreign keys reference) - Supabase CLI 3.1.0; generated schema aligned with PostgREST 14.18
Web
audience-chip.tsx,field-visibility.tsxandprofile-access.tsxfor the per-field audience and
circle UI;use-pause-profilewithpause-profile-settingandpause-instead-of-deletemedia-modal.tsxrenders a three-panel strip that tracks the draguse-suppress-link-long-pressfor internal links in the native shellsuse-sticky-railreplacesScrollPanelon the two-column profile; the top bar gets a z-indexuse-profileignores a late signed-out response once the signed-in one has landed/careerswithapplication-form.tsx, linked from the footer, the organization page and the sitemap- The contact page drops its feedback-form and social links
Mobile
- Android
versionCode193 → 195, iOS build 27 → 28, both on 1.48.0
Tooling, scripts & docs
yarn test:integration: API handlers against real Postgres built from the migrations, covering
privacy, access, auth, the data export and account deletion, with Supabase's default grants applied- A scan that runs
prepareon every query string in the API and shared code against the real schema - E2E covers the main web journeys (people, messaging, profile edit and access, block, compatibility,
endorsements, settings), split into two shards; web unit tests can render through
jest-environment-jsdom - A coverage ratchet per workspace and a patch coverage target, replacing the 90% goal
- New docs:
profile-visibility.md,database-migrations.md,websocket-auth.md,
altruists-only.md,test-coverage-plan.md;feed.md,profile-fields.mdand the bounty rules
updated
Full Changelog: 1.47.0...1.48.0