* Support node 20, drop node 16
* Update workflow versions
* Update backendmeta
* Use version file
* Update packages
* Yarn updates
* Changelog
* Fix glibc compatibility
* Target es2021
Without this, CI tests fail
* Drop unused metrics parameter
* Revert "Drop unused metrics parameter"
This reverts commit 4d874549bcec3dea0d6941215ac5c4f4707966ac.
* Make a note about broken support
---------
Co-authored-by: Andrew Ferrazzutti <andrewf@element.io>
* Add network timeouts to Docker builds
* Split cargo build out
* Put cargo in the right place
* debug usage
* install time
* Fix docker build OOMing in CI for arm64 builds
Yoinked from synapse:
- https://github.com/matrix-org/synapse/pull/14173
- 424d1d28cc
* Update changelog
Co-authored-by: Half-Shot <will@half-shot.uk>
* Remove --no-script from yarn
As it turns out, we need to run the script to build the all important
crypto modules that we don't use. The --no-script is intended to avoid
us trying to build the project, but in practise I think this does more
harm than good (we don't seem to build when the production flag is used)
* changelog
* Use node:16-slim for final image build
* changelog
* Add ignore scripts to final install step
* Copy matrix-sdk-crypto-nodejs built files
* Add workaround to build images foo crypto-nodejs
* chmod +x
* require bash for builds
* Add apt install to hopefully make the rust bits build for arm
* Fix missing multilib (#349)
* Update and rename 336.misc to 339.bugfix
Co-authored-by: Paul Tötterman <ptman@users.noreply.github.com>
* Do not explicitly pass --target to rustup
It doesn't seem to be necessary to install Rust.
Passing `--target` prevents the Dockerfile from being built on different architectures.
Not passing it makes it auto-detect what to install.
Discussed here: https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1505
* Add changelog entry