Release v0.12.3 (#371)

.github/SECURITY.md

@@ -9,4 +9,4 @@
 
 ## Reporting a Vulnerability
 
-Write an mail to aiko@aitsys.dev or open an issue on GitHub.
+Write an mail to aiko@aitsys.dev or report it via [Security](https://github.com/TediCross/TediCross/security/advisories/new).

.github/workflows/codeql.yml

@@ -23,7 +23,7 @@ jobs:
         language: ["javascript"]
     steps:
       - name: Checkout repository
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
       - name: Initialize CodeQL
         uses: github/codeql-action/init@v2
         with:

.github/workflows/docker_publish.yml

@@ -14,13 +14,13 @@ jobs:
       contents: read
     steps:
       - name: Check out the repo
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
 
       - name: Set up QEMU
         uses: docker/setup-qemu-action@v2.2.0
 
       - name: Set up Docker Buildx
-        uses: docker/setup-buildx-action@v2.9.1
+        uses: docker/setup-buildx-action@v2.10.0
 
       - name: Log in to Docker Hub
         uses: docker/login-action@v2.2.0
@@ -44,7 +44,7 @@ jobs:
 #            ghcr.io/${{ github.repository }}
 
       - name: Build and push Docker images
-        uses: docker/build-push-action@v4.1.1
+        uses: docker/build-push-action@v4.2.1
         with:
           context: .
           file: ./Dockerfile

.github/workflows/manual_docker_publish.yml

@@ -17,13 +17,13 @@ jobs:
     timeout-minutes: 60
     steps:
       - name: Checkout repository
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
 
       - name: Set up QEMU
         uses: docker/setup-qemu-action@v2.2.0
 
       - name: Set up Docker Buildx
-        uses: docker/setup-buildx-action@v2.9.1
+        uses: docker/setup-buildx-action@v2.10.0
 
       - name: Log in to Docker Hub
         uses: docker/login-action@v2.2.0
@@ -32,7 +32,7 @@ jobs:
           password: ${{ secrets.DOCKERHUB_TOKEN }}
 
       - name: Build and push image
-        uses: docker/build-push-action@v4.1.1
+        uses: docker/build-push-action@v4.2.1
         with:
           context: .
           file: ./Dockerfile

.github/workflows/nodejs.yml

@@ -15,7 +15,7 @@ jobs:
     env:
       NODE_ENV: "dev"
     steps:
-      - uses: actions/checkout@v3
+      - uses: actions/checkout@v4
       - name: Use Node.js ${{ matrix.node-version }}
         uses: actions/setup-node@v3
         with:

Dockerfile

@@ -1,4 +1,4 @@
-FROM node:19-alpine
+FROM node:20.5.1-alpine3.18
 
 RUN apk add --no-cache python3 g++ make
 

README.md

@@ -102,10 +102,11 @@ As mentioned in the step-by-step installation guide, there is a settings file. H
 	* `discord.relayLeaveMessages`: Whether to relay messages to Telegram about people leaving the Discord chat
 	* `discord.sendUsernames`: Whether to send the sender's name with the messages to Telegram
 	* `discord.crossDeleteOnTelegram`: Whether to also delete the corresponding message on Telegram when one is deleted in Discord
-        * `discord.useEmbeds`: Whether to use embeds for current bridge. Can be `always`, `never`, `auto`. Defaults to `false`
+	* `discord.disableWebPreviewOnTelegram`: Whether to disable links preview when relaying to Telegram
+	* `discord.useEmbeds`: Whether to use embeds for current bridge. Can be `always`, `never`, `auto`. Defaults to `false`
 	* `threadMap`: An array containing all threads mapping for each bridge
-    	* `telegram`: Telegram thread ID. See step 13 on how to acquire it
-    	* `discord`: Discord thread ID. See step 13 on how to acquire it
+		* `telegram`: Telegram thread ID. See step 13 on how to acquire it
+		* `discord`: Discord thread ID. See step 13 on how to acquire it
 
 The available settings will occasionally change. The bot takes care of this automatically
 

example.settings.yaml

@@ -40,6 +40,7 @@ bridges:
       relayLeaveMessages: true
       sendUsernames: true
       crossDeleteOnTelegram: true
+      disableWebPreviewOnTelegram: false
       useEmbeds: 'auto' # always / never / auto
 debug: false
 messageTimeoutAmount: 24