Files
Draupnir/DEPENDENCIES.md
Catalan Lover 020789c5a9 Alpine Docker Image (#1146)
* Update Crypto Bindings to enable Musl builds

* Update DEPENDENCIES.md with information about Temp override for musl

* Move Docker File to Node Alpine Base

* Bump Crypto Bindings to 0.6.6

This is the first version of crypto bindings that has ANY support for arm64 musl.

* Update Aliases to Align with Gnuxie Feedback

* Add Changeset
2026-09-09 16:26:24 +00:00

48 lines
1.5 KiB
Markdown

<!--
SPDX-FileCopyrightText: 2026 Gnuxie <Gnuxie@protonmail.com>
SPDX-License-Identifier: 0BSD
-->
# Dependencies
## Pinned dependencies
### @vector-im/matrix-bot-sdk
This is pinned and overridden because we need to have the exact same version for
all dependencies. As we create and pass `MatrixClient` through Draupnir,
matrix-protection-suite-for-matrix-bot-sdk, the vector bot-sdk fork itself, and
also matrix-appservice-bridge.
### @matrix-org/matrix-crypto-sdk-nodejs
This is pinned waiting for matrix-appservice-bridge to be updated so we have
musl builds working again allowing Alpine Docker Image to become a reality.
### postgres
https://github.com/porsager/postgres/issues/1143
This is pinned specifically as a work around for this issue.
## Workspace dependencies
Workspace dependencies should be kept at their same version and changesets
should be used for any changes. Package release should only be made from the
main branch once changesets have been merged and the associated package versions
bumped. This allows for the workspace state to always be used to build Draupnir
reproducibly on any branch of PR.
## Developer tooling
Developer tooling related `devDependencies` should be kept in the root package
unless it is not common to most packages. This is to make sure the versioning
remains consistent without relying on npm to do that.
## Node
We try to follow the active LTS release to keep us more inline with the
[matrix-appservice-bridge](https://github.com/matrix-org/matrix-appservice-bridge/blob/develop/docs/platforms.md)
stack of libraries.