Release Notes
This release requires a manual change in your galley configuration: settings.conversationCodeURI
in galley.yaml
was had to be set to ${WEBAPP}/join
before this release, and must be set to ${ACCOUNTS}/conversation-join
from now on, where ${WEBAPP}
is the url to the webapp and ${ACCOUNTS}
is the url to the account pages.
API Changes
- Several public team feature endpoints are removed (their internal and
Stern-based counterparts remain available):PUT /teams/:tid/features/sso
PUT /teams/:tid/features/validateSAMLemails
PUT /teams/:tid/features/digitalSignatures
- All endpoints that fetch conversation details now also include a new key
qualified_id
for a qualified conversation ID (#1640) - New endpoint
POST /list-conversations
similar toGET /conversations
, but which will also return your own remote conversations (if federation is enabled). (#1591)
Features
- Change
settings.conversationCodeURI
in galley.yaml (#1643). - [Federation] RPC to propagate messages to other backends (#1596).
- [Federation] Fetch remote user's clients when sending messages (#1635).
- [Federation] Actually propagate messages to other backends (#1638).
- [Federation] Support sending messages to remote conversations (#1609).
- [Federation] Guard against path traversal attacks (#1646).
Internal changes
- Feature endpoints are rewritten in Servant (#1642).
- Internal federation endpoints using the publicly-facing conversation data type
now also include a qualified conversation ID under thequalified_id
key
(#1640) - schema-profunctor: add
optField
combinator and corresponding documentation (#1621, #1624). - [Federation] Let a receiving backend decide conversation attribute specifics of its users
added to a new conversation viaPOST /federation/register-conversation
(#1622). - [Federation] Adjust scripts under ./hack/federation to work with recent changes to the federation API (#1632).
- Refactored Proteus endpoint to work with qualified users (#1634).
- Refactored Federator InternalServer (#1637)
Internal Federation API changes
- Breaking change on InwardResponse and OutwardResponse in router.proto for improved error handling (#1637)
- Note: federation should not be in use anywhere yet, so this should not have any impact
Documentation
- Fix validation errors in Swagger documentation (#1625).