Conversation
…1948) Public endpoint for team admins to set user email (triggers (re-)sending of activation email)
There seems to be no direnv plugin for VSCode that works with remotes. (I haven't checked the local / non-remote case.) This commit introduces a shell.nix file that depends on the same package list as direnv.nix, but uses mkShell instead of buildEnv to create the environment. This works fine with nix-shell itself and VSCode's 'Nix Environment Selector' plugin.
Add shell.nix for ad-hoc development environments
Document how to setup VSCode
* migrate db, and git add schema un root using cabal * unify to db-reset target * change name to db-migrate-package for consistency * Update doc Co-authored-by: Stefan Matting <stefan@wire.com>
* Add additionalArgs cfg * add note * add changelog entry
* Add Cargohold component to federator * Add federation API stub to cargohold * Add test stub for federator call to cargohold * Add cargohold config to federator helm chart, too Co-authored-by: jschaul <jschaul@users.noreply.github.com>
* Document general federation error mapping strategy * Move swagger header to a separate file The markdown file is converted to a haskell module by a custom `Setup.hs`. * Return 400 error code for federation-denied The federation-denied error is client-visible, since it may be due to errors in the original request. This makes the error propagate to the client with status code 400. * Update federation error documentation Also change some error labels and status codes to make them more consistent. The authentication error category has been merged with the remote federation error category, and all errors of the same category now have similar status codes.
* Improvements to cabal make targets - Speed up installation by using parallel xargs - Allow `package=all` to act on all packages
* Generate doc files in repl phase * Brig: fix sdist tarball generation
This matches the version currently deployed in the public cloud instance.
Contributor
I think I mis-filed that. If you want to be nit-picky, you can move it to "Features", but it kinda fits into both. |
fisx
approved these changes
Dec 10, 2021
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
6 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.
Release notes
selfDeletingMessagesconfigured ingalley.yaml, addlockStatus: unlocked. ((Un-)lock Status for Self-Deleting Messages (#1937 re-run) #1963)API changes
put /users/:uid/email) that allows a team owner to initiate changing/setting a user email by (re-)sending an activation email. (SQSERVICES 1099 Public API end-point for re-sending email validation #1948)Features
Team and server wide config for conversation guest link feature to configure feature status and lock status (SQSERVICES-547 add feature config for guest links #1964). If the feature is not configured on the server, the defaults will be:
featureFlags: ... conversationGuestLinks: defaults: status: enabled lockStatus: unlockedLock status for the self deleting messages feature can be set internally by ibis and customer support ((Un-)lock Status for Self-Deleting Messages (#1937 re-run) #1963)
Bug fixes and other updates
Documentation
Internal changes
additionalArgs(sftd chart: add config key additionalArgs #1972)Federation changes