mirror of
https://github.com/the-draupnir-project/Draupnir.git
synced 2026-05-11 01:57:02 +00:00
Gnuxie
82fe093ef3
https://github.com/the-draupnir-project/planning/issues/104 I don't know what the fuck they are doing with the typings in the vector bot-sdk repository but whatever. https://github.com/the-draupnir-project/Draupnir/issues/1053
43 lines
1.4 KiB
Markdown
43 lines
1.4 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.
|
|
|
|
### 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.
|