Conversation
Master->Develop after release
…rch (second attempt). (#5488) * Include team collaborators in contact search. * Implement TeamCollaboratorsSubsystem interpreter with BrigAPIAccess. Was previously UserSubsystem, but since it TeamCollaboratorsSubsystem is also used outside of Brig, that is not always available. Further changes: - Support BrigAPIAccess locally in Brig. - Change collaborator field type in UserDoc to collapse `Nothing` and `Just []` (remove the Maybe). * Fix brig-index: do not bump index version in failure case. * Add release notes on required postgres setup steps. --------- Co-authored-by: Gautier DI FOLCO <gautier.difolco@wire.com>
Deleted SCIM users could still register with their invitation code and be then part of the team - just with a new non-SCIM user. This does not reflect the intuition of deleting a user. Now, invitations are deleted when the user gets deleted.
This prevents us from running the app with unintended configurations and/or confusing assumptions about them. For `fromKeyValueParams` this implies being able to handle failures. For now, they are just propagated as there is little value in running a service with erroneous connection strings.
* brig: Reduce gc_grace_seconds on user tables * PostgresMarshall/Unmarshall instances for tuples of length 25 * UserStore.Migration: Implement migration * integration: Add test for user migration to pg * background-worker: Run user migration * integration: Wait max 30s for migrations * changelog and docs * integration: Add test case for inconsistent handle claims * UserStore: Deal with handle update during migration * integration: Test edge cases of migrating invalid users * integration: Test migration of user when handle is claimed in Cassandra and PG by different users * pg-migration: Use AtomicState to keep track of errors When using `State` sometimes the error count is not correct. * UserStore.Migration: Gracefully deal with duplicate handle claims These can happen due to race in the migration interpreter. The user who gets it in postgresql first, wins. * Wire.MigrationLock: Sort lock ids to avoid deadlocks --------- Co-authored-by: Gautier DI FOLCO <gautier.difolco@wire.com>
…revoked or expired via teams UI (#5510)
* Remove instruction for unneeded cabal update from developer build guideline
…ifications (#5501) * implement new unsupported version policy * changelog * roundtrip and golden test added * moved spec to correct place, ranemed tests according to lint rule
* implement federation support for adminless * some fixes in the implementation * formatting * updated tests with remote notification cases * add legacy federation test * changelog * filter already present users to prevent spam * cache fedaration supported state during scan * used bucketed recipients * avoid redundant per-domain grouping for system notifications * only search bounded fed api versions * simplified by removing deconstruction * replace Set.from/toList with nubOrd * removed unused parameter
--------- Co-authored-by: Leif Battermann <leif.battermann@wire.com>
…les have been touched. (#5509)
zebot
added
the
ok-to-test
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
7 participants
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.
[2026-09-18] (Chart Release 5.36.0)
Release notes
preventAdminlessGroupsis unlocked by default (WPB-28237 unlock prevent adminless groups feature #5496)API changes
Features
Add federation support for
preventAdminlessGroupssystem notifications, with capability-aware handling for older remote backends. (WPB-26650 federate senderless adminless events #5525, WPB-28697 add federated reminder events with origin user #5540)Add
ssoIdpChangeDetectionEnabledtoGET /system/settings. (WPB-28246: expose ssoIdpChangeDetectionEnabled via GET /system/settings #5527)Change the default value of totalLimitBytes from one terrabyte to unlimited (WPB-28484 change default total limit bytes value to -1 #5519)
Meeting events (
meeting.create,meeting.update,meeting.delete,meeting.member-add) are now delivered to all push channels, including native push (APNs/FCM), so offline or backgrounded clients learn about meeting changes via native push instead of waiting for the next foreground sync. (WPB-28685 :Deliver meeting events via native push (APNs/FCM) #5537)Support migrating user data to postgresql from cassandra (UserStore: Add migration logic and migration interpreter #5324)
Bug fixes and other updates
Revoking a pending SCIM invitation now removes the associated Brig account and
Spar SCIM metadata synchronously, allowing the same SCIM user to be invited
again. (WPB-18929 fix: SCIM cannot re invite user if initial invitation was revoked or expired via teams UI #5510)
MLS message validation has been hardened. (WPB-23427 Adjust uncommon request flow #5517)
Account pages now use the correct backend URL and CSP header on each multi-ingress domain. This applies to both ingress charts:
nginx-ingress-servicesno longer includes the account-pages host in its generic CSP snippet, andwire-ingress(envoy-gateway) no longer injects a Content-Security-Policy response header on the account-pages route. The same fix is applied to the webapp route inwire-ingress, which had the same problem (nginx-ingress-servicesalready skipped it). (WPB-27964 use CSP header of account pages #5534)Deleted SCIM users could still have pending team invitations. These are now
deleted (invalidated) with the SCIM user. (Fix: active team invitation after SCIM user deletion #5492)
Postgresql connection strings with mismatched host/port counts in service
configurations now lead to immediate failure with a clear error message instead
of silently producing an erroneous connection. (Fix: Enforce correct host port assignment for postgresql connection strings #5494)
Documentation
Internal changes
Script listing all commits and releases in which given files have been touched. ([WPB-27169] Script listing all commits and releases in which given files have been touched. #5509)
MLS commit-bundles are processed with less sequential I/O: proposal references are resolved from a single store read, client and client-store updates fan out concurrently, and welcome pushes no longer block the response. (WPB-28483: remove serial per-user round trips from MLS commit-bundle path #5528)
Add diagnostic logging for failed MLS commit-bundle operations, including typed failures and exceptions during commit-lock handling. (WPB-28709 additional logging on failed mls commits #5544)
Federation changes
Add an opt-in policy for dropping queued federation notifications when the target backend supports no compatible API version. (WPB-28421 add an opt in policy for dropping unsupported federated notifications #5501)
Remove stale local memberships when a remote conversation is definitively reported as not found. (WPB-28422 reconcile stale local memberships for deleted remote conversations #5504)