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 2022-11-03 - (expected chart version 4.26.0) #2821

Merged
merged 69 commits into from
Nov 3, 2022

Conversation

zebot
Copy link
Contributor

@zebot zebot commented Nov 3, 2022

[2022-11-03] (Chart Release 4.26.0)

Release notes

API changes

Features

Bug fixes and other updates

Documentation

Internal changes

Veki301 and others added 30 commits September 29, 2022 10:20
* feat: make repl

* doc: changelog
* feat: add unsafe concurrency effect
* feat: just hoist traverse
* feat: add a "safety" flag
* refactor: UnsafeConcurrency -> Concurrency
* feat: add haddocks
* Bump servant-swagger-ui

* Fixup

* bycatch

* don't remove from cabal, add to stack.yaml!

* hi ci
Documentation updates fix - missing -h param in nodetool
Master->Develop after release
* Servantify /i-api

* Serve servant api under path prefix.

* More servant end-points

* More servant end-points

* More servant end-points

* More servant end-points

* More servant end-points

* More servant end-points

* Keep wai-route routing table only for swagger1.2 (part 1).

* Keep wai-route routing table only for swagger1.2 (part 2).

* More servant end-points

* More servant end-points

* Fun with schema-profunctor

* More servant end-points (feature config)

* More servant end-points (feature config)

* More servant end-points (feature config)

* More servant end-points

* Cleanup

* Fixup

* Bug fix: make routes distinguishable by path.

Given two routes with the same path, some swagger-ui version
distinguish by query params, some (including the servant-swagger-ui
version we're going to use moving forward) will collapse all of them
into the last.  This commit makes the paths different by adding string
literal segments.

* Update docs

* Revert "Cleanup"

This reverts commit 7d1c0e1.

* changelog

* Removed unused imports.

* imports

* Fixup

* Cleanup

* docs.

* hi ci

Co-authored-by: Igor Ranieri <igor@elland.me>
* rpc effect machinery
* propagate effects
* move RPC calls into interpreter
* feat: use unsafe concurrency for lookupProfiles
* services/gundeck: move appName closer to where it's used

* services/gundeck: document SNS Platform Application requirements
This seems to have gotten broken, it complains about some resources that
can't be found:

```
level=error ts=2022-09-30T08:09:08.703284478Z caller=klog.go:116 component=k8s_client_runtime func=ErrorDepth msg="status \"default/wire-server-metrics-kube-p-prometheus\" failed: failed to update status subresource: prometheuses.monitoring.coreos.com \"wire-server-metrics-kube-p-prometheus\" not found"
```

Describing how to install a monitoring system, shipping our own wrapper
chart, and documenting how to install it shouldn't be something we did
in first place. It's a potential endless game of whack-a-mole with
upstream changes, and mirroring it downstream in our documentation
shouldn't be part of wire-server.

Instead, describe what wire-server can do, how it marks its metrics
endpoints via ServiceMonitor, and refer to the upstream docs of two
commonly used metrics operators.
* refactor: build UserSpec tests out of more composable pieces
Co-authored-by: Marko Dimjašević <marko.dimjasevic@wire.com>
Co-authored-by: Stefan Matting <stefan@wire.com>
Co-authored-by: Zebot <zebot@users.noreply.github.com>
Co-authored-by: Zebot <zebot@users.noreply.github.com>
Major changes:
1. Instead of pinning things in `cabal.project`, we pin them in `nix/haskell-pins.nix`. This allows us to share built artefacts among the team and helps us avoid problems of compiling things with newer C libraries because cabal doesn't invalidate the built artefacts in the cabal-store.
2. Images are built using nixpkgs' `dockerTools.streamLayeredImage`. This allows us to build minimal images without needing a docker daemon to be running. This also helps us cache most of our images in the nix cache.
3. Every time any cabal file is changed or a new package is added, we must run `make regen-local-nix-derivations`. This will update various nix derivations we have for our project. This is protected by `make check-local-nix-derivations` which runs as a dependency of `make lint-all` in CI. 

Co-authored-by: Stefan Matting <stefan@wire.com>
Co-authored-by: Akshay Mankar <akshay@wire.com>
* Makefile: Avoid building haddocks while building production images

* Add changelog for nix builds, forgotten in #2331
… http(s) managers (#2772)

* cacert-fixup attempt

* Use SSL.contextSetDefaultVerifyPaths so we respect SSL_CERT_FILE env var

* Revert "cacert-fixup attempt"

This reverts commit 398cec1.

No need.

* Set SSL_CERT_FILE in all docker images

* Changelog

* Redundant imports

* more redundant imports

Co-authored-by: Akshay Mankar <akshay@wire.com>
* New version of hlint is more reliable

* Change file check for -all

* Fixed compilation breaking b/c of operation order?

* Fixed lint script -k true

* Apply lint correctly
fisx and others added 24 commits October 24, 2022 15:54
* Fix content type used when testing MLS commit bundles

* shellcheck .cabal file

* Must not forget to regen derivations
…m clients/TM (#2786)

After not using the wire client for some time, it can easily happen that many conversations have many assets that should be downloaded. We may wish to be more lenient on asset download (well, getting signed URLs to download assets) requests. See https://wearezeta.atlassian.net/browse/SQCORE-1372 and https://wearezeta.atlassian.net/browse/SQSERVICES-1763
* Refactor for clarity.

* More hints in case of compiler errors.

* Make `make full-clean` fuller.
* Use ormolu 0.5.0.1 in dev environment

* use ghc92

* add ormolu fixity configuration

* reformat all files

* Formatted pending changes from develop

Co-authored-by: Igor Ranieri <igor@elland.me>
Co-authored-by: jschaul <jschaul@users.noreply.github.com>
* Check external commit criteria
- Extract the key package from the update path
- Validate key package before replacing the old one
* Fix the serialiseMLS instance for `Sender 'MLSPlainText`
* Update the mls-test-cli reference
* Integration tests for external commits
* Add optional client ID to tokens

* Add client ID to access token

* Access can now take a client ID

* Add client ID access test

* More client ID access tests

* hlint

* Regenerate nix derivations

* Change client ID field in token

libzauth expects one-letter fields

* Disable automatic formatting in libzauth

* Test client id token metadata

* Add Z-Client variable

* Add ZClient combinator

* Add CHANGELOG entry

* Check validity of client ID on access

* Throw error on /access with a different client ID

* Add Z-Client header to nginz in charts
* nix: Pin openssl to 1.1

* Revert "nix: Pin openssl to 1.1"

This causes a world rebuild of nixpkgs (which takes a lot of time), and the
build in CI doesn't complete successfully anyhow.

This reverts commit dc1f54e.

* nix: selectively pin openssl to 1.1 for Haskell packages.

This injects openssl 1.1 into the build of specifically the HsOpenSSL package,
which other Haskell derivations depend on for TLS functionality.

Co-authored-by: Molly Miller <molly.miller@wire.com>
* chore: add advisory regarding openssl

* name files consistently to have security responses show up ordered by date

* Set reversed order to have most recent entry on top

Co-authored-by: jschaul <jschaul@users.noreply.github.com>
Co-authored-by: Zebot <zebot@users.noreply.github.com>
* `GET /api/event-notification-schemas` for server-initiated events

* s/TODO/FUTUREWORK/g
add sphinx extension sphinx-reredirects and configuration to generate simple JavaScript based redirects to new locations of previously inconsistently named files/URLs. Cleanup of old redirect pages.
@zebot zebot temporarily deployed to cachix November 3, 2022 13:56 Inactive
@zebot zebot added the ok-to-test Approved for running tests in CI, overrides not-ok-to-test if both labels exist label Nov 3, 2022
@smatting smatting self-requested a review November 3, 2022 13:59
@smatting smatting merged commit eead65e into master Nov 3, 2022
@smatting smatting deleted the release_2022-11-03_13_56 branch November 3, 2022 14:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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.