-
Notifications
You must be signed in to change notification settings - Fork 333
Release 2022-03-01 #2169
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Release 2022-03-01 #2169
Conversation
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
Co-authored-by: Sven Tennie <[email protected]>
Merge master
Co-authored-by: Zebot <[email protected]>
* Enable benchmarks when building with cabal * gundeck/benchmark: Fix import of amazonka
…ist (#2161) Co-authored-by: Paolo Capriotti <[email protected]>
* Add key package table * Key package upload endpoint * Key package validation * Parse and validate extensions * Add MLS media type * Improve MLS key package Swagger * Compute and store key package refs * Add endpoint for claiming key packages * Add key package count endpoint * Validate key package lifetimes * Verify key package signatures * Key package upload test * Unit tests for key package validation functions * Unit test KeyPackage extension parsing * Fix key package integration test * Add key package count test * Test key package claim endpoint * Validate key package protocol version * Add nginz routes for MLS endpoints * Upgrade nixpkgs * Add crypto-cli to direnv * Document key package lifetime option
* Dockerfile.builder: Add cabal update * add changelog entry
pcapriotti
approved these changes
Mar 2, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but maybe lose the "Hi CI" commit.
I cannot it is already in develop 😢 |
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.
[2022-03-01]
Release notes
API changes
The
api-version
endpoint now returns additional information about the backend:federation
);domain
).Note that the federation domain is always set, even if federation is disabled. (Add extra information to
api-version
endpoint #2146)Add MLS key package API (MLS key packages #2102)
Internal changes
Bump aeson to v2.0.3.0 and update amazonka fork from upstream repository. (Upgrade aeson and amazonka #2153, Fix version bounds. #2157, Fix: Ensure asset download URL uses S3DownloadEndpoint when provided #2163)
Add schema-profunctor instances for
QueuedNotification
andQueuedNotificationList
(Add ToSchema instances for QueuedNotification and QueuedNotificationList #2161)Dockerfile.builder: Add cabal update (Dockerfile.builder: Add "cabal update" step #2168)
Federation changes
NoSearch
,ExactHandleSearch
andFullSearch
.Details about the configuration are described in config-options.md.
There are sane defaults (deny to find any users as long as there is no other configuration for the domain), so no measures have to be taken by on-premise customers (unless the default is not the desired behavior). (Add configurable restriction to federated user searches #2087)