Drop Node 22, support Node 26, update deps (#524)

* Update supported Node versions, bump Typescript

* Drop recursive `fsPromises.rmdir` for Node 25

Instead use `fsPromise.rm()` with `{ recursive: true }`, as suggested by
NodeJS docs (but don't need `{ force: true }` in this case)

* Use towncrier version that replaces pkg_resources

* Make towncrier ignore git.keep

* Wrap towncrier version range in quotes

Otherwise, the > is used as a redirection operator

* Update matrix-appservice to `4.1.0`

Also bump related dependencies

* Regenerate lockfiles & bump postgres.js

See https://github.com/porsager/postgres/releases/tag/v3.4.9

* Support Node 26

* Tweak towncrier config

Omit extensions on news fragment files created with `towncrier create`
for consistency with how those files have been named in this repo.

* Update matrix-bot-sdk to 0.10.0-element.0

Resolves GHSA-wfq4-36m3-9g4 / CVE-2026-45056

* Remove one more time-of-writing date

Author: AndrewFerr

.github/workflows/changelog.yml

@@ -13,7 +13,7 @@ jobs:
           ref: ${{ github.event.pull_request.head.sha }}
           fetch-depth: 0
       - uses: actions/setup-python@v2
-      - run: pip install towncrier==22.8.0
+      - run: pip install 'towncrier>=23.6.0'
       - run: scripts/check-newsfragment
         env:
           PULL_REQUEST_NUMBER: ${{ github.event.number }}

.github/workflows/docs.yml

@@ -8,7 +8,7 @@ on:
 jobs:
   docs:
     runs-on: ubuntu-24.04
-    container: node:22
+    container: node:24
     steps:
       - uses: actions/checkout@v3
 

.github/workflows/test.yml

@@ -10,7 +10,7 @@ on:
 jobs:
   lint:
     runs-on: ubuntu-24.04
-    container: node:22
+    container: node:24
     steps:
       - uses: actions/checkout@v2
       - run: yarn --strict-semver --frozen-lockfile
@@ -19,7 +19,7 @@ jobs:
   test:
     strategy:
       matrix:
-        node-version: [22, 24]
+        node-version: [24, 26]
     runs-on: ubuntu-24.04
     steps:
       - uses: actions/checkout@v2
@@ -31,7 +31,7 @@ jobs:
       - run: yarn build && yarn test
   test-postgres:
     runs-on: ubuntu-24.04
-    container: node:22
+    container: node:24
     services:
       postgres:
         image: postgres:latest

.node-version

@@ -1 +1 @@
-22
+24

CONTRIBUTING.md

@@ -61,7 +61,7 @@ First of all, thank you for considering making a change to one of our projects.
 ### 🖌️ Code style
 
 Each repository contains an `eslint` configuration which will dictate the style of the code. All code should be written in
-TypeScript. At time of writing, we target ES2022 (supported by Node 22). The CI will lint your code automatically,
+TypeScript. At time of writing, we target ES2024 (supported by Node 24). The CI will lint your code automatically,
 but you can save yourself some time by running (`yarn lint`/`npm lint`) to check locally.
 
 ### 🧪 Tests / CI

README.md

@@ -5,7 +5,7 @@ This library sits on top of the
 and provides an API for setting up bridges quickly. Check out the
 [HOW-TO](HOWTO.md) for a step-by-step tutorial on setting up a new bridge.
 
-`matrix-appservice-bridge` requires Node JS 22.x or greater.
+`matrix-appservice-bridge` requires Node JS 24.x or greater.
 
 If you are looking to contribute to this library, please check out our [CONTRIBUTING](./CONTRIBUTING.md) guide.
 

changelog.d/524.misc

@@ -0,0 +1 @@
+Update matrix-appservice to `4.1.0`.

changelog.d/524.misc.1

@@ -0,0 +1 @@
+Update matrix-bot-sdk to `0.10.0-element.0`.

changelog.d/524.removal

@@ -0,0 +1 @@
+Drop support for Node 22, add support for Node 26.

docs/platforms.md

@@ -14,7 +14,7 @@ Node.JS version falls from Active to Maintenance, we will migrate projects to th
 For users who are on distributions packaging only Maintenance versions of Node.JS, we'd suggest either using Docker
 or an alternative Node.JS source.
 
-At time of writing (August 2025) we support 22.X and 24.X as they are the Active and Current releases of Node.JS.
+At time of writing, we support 24.X and 26.X as they are the Active and Current releases of Node.JS.
 
 Bridge projects do not provide long term support to odd-versioned Node.JS releases, as these are short lived non-LTS
 versions and are difficult to support since they have a 6 month shelf life.