Skip to content
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

Release 2024-02-12 - (expected chart version 4.40.0) #3879

Closed
wants to merge 183 commits into from

Conversation

zebot
Copy link
Contributor

@zebot zebot commented Feb 12, 2024

[2024-02-12] (Chart Release 4.40.0)

Release notes

  • The settings setDisabledAPIVersions (brig) and disabledAPIVersions (in cannon, cargohold, galley, gundeck, proxy, and spar) are now required.
    The default defined in charts/<service>/values.yaml is set to [ development ] and disables all development API versions.
    For more information see https://docs.wire.com/developer/reference/config-options.html#disabling-api-versions (WPB-4657 Disabling development versions #3772)

  • The mls team feature now has a lock status. If the current installation has default settings defined in wire-server's values.yaml, the lockStatus has to be added, e.g.:

    mls:
      defaults:
        status: enabled
        config:
          protocolToggleUsers: []
          defaultProtocol: mls
          allowedCipherSuites: [1]
          defaultCipherSuite: 1
          supportedProtocols: [proteus, mls] # must contain defaultProtocol
        lockStatus: locked
    ``` (#3681)
    
    • Replace fake-sqs with ElasticMQ

    ElasticMQ is an actively maintained project, fake-sqs hasn't seen a commit since
    2018. This is not expected to have any noticeable effect on deployments that
    don't have any extra configurations for the SQS queues. If the fake-aws-sqs
    chart had configured custom queue names, they have couple of extra limitations:

  • Upgrade team-settings version to 4.15.1-v0.31.19-0-ee1dbce (Update team-settings version in Helm chart [skip ci] #2180)

  • Upgrade webapp to 2023-12-11-production.0-v0.31.17-0-1e91445

    Beside using up-to-date versions in Helm charts is generally beneficial,
    this version also provides multi-ingress support. (webapp: Upgrade to 2023-12-11-production.0-v0.31.17-0-1e91445 #3803)

API changes

Features

Bug fixes and other updates

Documentation

Internal changes

Federation changes

arthurwolf and others added 30 commits September 13, 2023 02:45
Master->Develop after release
* add replace unclaimed key-packages route and endpoint
* Add key package replace test

---------

Co-authored-by: Paolo Capriotti <paolo@capriotti.io>
* Added ingress check for dynamic backends in integration tests.

* Moved some args around. Better error for ingress.

* Restored nginz special handling.

* WIP: check 533 reason
…chable (#3673)

* Add the copyright header to test modules

* Add two integration tests

The tests simply assert the expected behavior in MLS and confirm it is
the same as for Proteus

* Add a changelog

* A test case on adding an unreachable user

This is a scenario where a conversation already has a member from that
backend, but now the backend is unreachable. The test case has both the
Proteus and the MLS implementation and they are consistent in the
observed behavior.
We were sending external remove proposals for each client of a user that was kicked out of a conversation following a remove commit. This was caused by some overgeneralisation of the mechanism that removes clients from subconversations when a user is deleted from the main.
Co-authored-by: Zebot <zebot@users.noreply.github.com>
* More robust consuming of MLS messages

This commit changes the behaviour of `sendAndConsumeMessage` and
`sendAndConsumeCommitBundle` to actually wait for those messages on the
client's websocket.

This should fix a lot of the flakiness of MLS tests that appeared after
the introduction of message queuing.

* Fix testAppMessageSomeReachable

When some backends are down, the new `sendAndConsume*` functions do not
work, because they expect a message to be received by all clients.

This commit changes tests with such a scenario to only post the message,
and not consume it.

* Add protocol field to MLS test state

This is necessary because new users in mixed MLS conversations don't get
join events, and we are waiting for such events before consuming MLS
messages.

* Add CHANGELOG entry
After an application message the ratchet is updated, therefore we need to save the updated group state so that future messages are generated correctly.

This commit includes an mls-test-cli update. The new mls-test-cli version modifies the `message` command to include both `group-in` and `group-out` options, as other similar commands already do.
These function args are unused.
Still using that wireapp/rust-jwt-simple repository, but at least the
latest version of the code, not a commit from Feb 10.
This needs crate2nix 0.11.0 (from a more recent nixpkgs checkout), but
only during Cargo.nix recreation.

Let's hope it's there the next time we update this file.
use crate2nix for some of our rust crates
stefanwire and others added 25 commits January 29, 2024 10:15
Use GitHub wireapp forks for nix dependencies

Co-authored-by: Marco <marcoconti83@gmail.com>
Co-authored-by: Marco Conti <marcoconti83@gmail.com>
* treefmt.toml: Remove run-services from excludes of shellcheck

It is not a shell script anymore

* services/start-services-only.sh: Delete

It doesn't do anything and is not referred from any documentation. It has been
"deprecated" for quite some time.

* Replace services/run-services with dist/run-services
* Update http-client fork to latest upstream and use it

* Revert "Improve usage of http-manager (fixes for fingerprint verification) (#3825)"

This reverts commit 38d3398.

* Revert "Migrate from http-client fork, use upstream. (#3801)"

Except for changes to amazonka things as we're still using latest
http-client (albiet forked) which requires us to upgrade amazonka.
It seems to be OOMKilled sometimes.
…am-for-rabbitmq

Modify federation diagram to include rabbitmq: updating the diagram and the source file
* [fix] use the correct API in the integration tests
* Use HasTests to save a few LOC.

* Fix/extend client CRUD api.

- moved internal add from API.Brig to API.BrigInternal
- created API.BrigCommon for data structured needed in both
- added public add

* Tranlate tests: manually add/delete client.

* Fiddle with test case type abstractions.

* Remove obsolete test from integration/test/Test/Demo.hs
Update coturn image with bugfix to its pre-stop-hook from wireapp/coturn#10 to allow coturn pods to terminate once their traffic has drained, instead of waiting for its terminationGracePeriod (up to 24 hours).
* replace runAsNonRoot to user group and id of 1000

* add changelog
* update annotation key for k8s 1.27+

* add changelog

* add backward compatability
`disabledAPIVersions` is a list which Helm would print as `[item1 item2]` into
YAML, thus, corrupting the YAML format. This can be mitigated by applying the
Helm template function `toJson` (or `toYaml`) to the list in question which
would format the list as `["item1", "item2"]`. This is no issue for scalars,
since Helm's format coincidently matches the one required by YAML.
This commit introduces the concept of Subsystems. Each of these subsystems will
represent an important part of the domain concepts in the product that will
interact with other subsystems. We will use effect systems to encode these
subsystems and test them in isolation as much as possible.

This commit consolidates all the code that spoke to gundeck from brig and galley
into the NotificationSubsystem.

https://wearezeta.atlassian.net/browse/WPB-5985

---------

Co-authored-by: Magnus Viernickel <magnus.viernickel@wire.com>
Co-authored-by: Leif Battermann <leif.battermann@wire.com>
@CLAassistant
Copy link

CLAassistant commented Feb 12, 2024

CLA assistant check
All committers have signed the CLA.

@zebot zebot added the ok-to-test Approved for running tests in CI, overrides not-ok-to-test if both labels exist label Feb 12, 2024
@battermann
Copy link
Contributor

webapp version bump missing

@battermann battermann closed this Feb 12, 2024
@echoes-hq echoes-hq bot added the echoes: bugs Technical or functional defects in the product label Jun 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
echoes: bugs Technical or functional defects in the product ok-to-test Approved for running tests in CI, overrides not-ok-to-test if both labels exist
Projects
None yet
Development

Successfully merging this pull request may close these issues.