-
Notifications
You must be signed in to change notification settings - Fork 334
Release 2022-01-27 #2080
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-01-27 #2080
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
…in certificate. (#2054) * generate cert with multiple domains in the SAN also, the subject CN has yet another value than the ones inside Subject alternative name fields. * add unit test for multi-domain cert
* cabal wrapper: define CONFIG_SHELL * add changelog
Merge release 2022-01-18 back into develop
* Tag a negative test case for X509v3 Extended Key Usage * Tag a test for remote user removal when guests disallowed - When the access is updated such that it disallows guests from accessing, all guests, both local and remote, are kicked out of the conversation. This just tags such a test case. * Tag a negative test for getting remote conversation details
* Add licenses * Changelog * Refresh headroom. * Changelog Co-authored-by: Matthias Fischmann <[email protected]>
Co-authored-by: fisx <[email protected]>
* Split up Spar.Data * make format * Fix test * changelog
…upByTeam (#2068) * Rename ScimTokenStore.GetByTeam -> ScimTokenStore.LookupByTeam * changelog * CI
Also, provide better swagger doc inspired by MultiVerb and add names to endpoints (including the public one). Use PushNotificationStream to abstract from FromSourceIO: This makes the conversion to ConduitT a bit easier to find, because it's literately written in the code. Use latest master of Servant.
There are a lot left, but these ones should be safe to not change the application's behavior.
* charts/nginz: Add restrictive CORS headers to all origins and explicitly allowlist allowed origins * charts/nginz: Set some default allowlisted origins * Update changelog * Spelling and style fixes in changelog. * charts/nginz: fix fail-open behaviour in CORS configuration. * charts/nginz: use singular "account" for consistency with other resources. Co-authored-by: Molly Miller <[email protected]>
* Fix: nginz template broken for allowlisted_origins * changelog
Fix bug: Calls config crashes when SFTs are unreachable
julialongtin
approved these changes
Jan 27, 2022
5890932 to
0641f90
Compare
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.
Release notes
The
nginzchart now configures nginx to only allow cross-origin requests from an explicit allow list of subdomains. By default these are:If you changed the names of these services, you must adjust those names in the nginz config as well. (charts/nginz: Add restrictive CORS headers to all URLs and explicitly… #1630)
Backend now separates conversation access control for guests and services. The old access roles are still supported but it is encouraged to upgrade clients since mapping between the old access roles and the new access roles is not isomorphic. For more details refer to the API changes below or the Swagger docs.
Old clients are fully supported; if new clients and old clients are mixed, to old clients, either guests of services may appear to be enable if they are not, which may lead to error messages (confusing but harmless). (SQSERVICES-1083 Separate Access Control For Guests And Services #2035)
API changes
access_rolein their payload will now acceptaccess_role_v2as well which will take precedence overaccess_role. See Swagger docs for how values are mapped. Endpoints that recently have returnedaccess_rolein their payload will now additionally return theaccess_role_v2field. (SQSERVICES-1083 Separate Access Control For Guests And Services #2035)Features
Bug fixes and other updates
Internal changes
Federation changes