Update dependencies (#1378)

.github/workflows/pull_request.yml

@@ -15,7 +15,7 @@ jobs:
       - name: Set up Go
         uses: actions/setup-go@v3
         with:
-          go-version: "~1.20"
+          go-version: "~1.23"
       - name: Get Go module cache directory path
         id: go-module-cache-dir-path
         run: echo "::set-output name=dir::$(go env GOMODCACHE)"

.github/workflows/release.yml

@@ -17,7 +17,7 @@ jobs:
       - name: Set up Go
         uses: actions/setup-go@v3
         with:
-          go-version: "~1.20"
+          go-version: "~1.23"
       - name: Get Go module cache directory path
         id: go-module-cache-dir-path
         run: echo "::set-output name=dir::$(go env GOMODCACHE)"
@@ -81,4 +81,4 @@ jobs:
         run: make gateways.csv
       - name: Sync gateways.csv to airtable
         run: |
-          curl -X POST ${{ secrets.AIRTABLE_GATEWAYS_API_ENDPOINT }} -H "Authorization: Bearer ${{ secrets.AIRTABLE_GATEWAYS_API_KEY }}" -H "Content-Type: text/csv" --data-binary "@gateways.csv"
+          curl -X POST ${{ secrets.AIRTABLE_GATEWAYS_API_ENDPOINT }} -H "Authorization: Bearer ${{ secrets.AIRTABLE_GATEWAYS_API_KEY }}" -H "Content-Type: text/csv" --data-binary "@gateways.csv"

doc/config/_default/config.toml

@@ -6,7 +6,6 @@ theme = "the-things-stack"
 
 disableKinds = [
   "taxonomy",
-  "taxonomyTerm",
   "RSS",
 ]
 

doc/content/gateways/_index.md

@@ -10,4 +10,4 @@ aliases: [/guides/connecting-gateways]
 
 This section contains information to help you work with gateways in {{% tts %}}. Here, you'll find guides for connecting gateways using {{% lbs %}} or the {{% udp-pf %}}, and instructions for connecting many popular LoRaWAN® gateways.
 
-If your {{% tts %}} deployment is connected to [Packet Broker]({{< ref "the-things-stack/packet-broker" >}}), you can take advantage of coverage from The Things Network without adding any gateways of your own. See [Adding Gateways]({{< relref "/adding-gateways" >}}) for instructions to add gateways and to find out if your location has nearby gateways.
+If your {{% tts %}} deployment is connected to [Packet Broker]({{< ref "the-things-stack/packet-broker" >}}), you can take advantage of coverage from The Things Network without adding any gateways of your own. See [Adding Gateways]({{< relref "concepts/adding-gateways" >}}) for instructions to add gateways and to find out if your location has nearby gateways.

doc/content/gateways/concepts/lora-basics-station/cups-forwarding.md

@@ -8,18 +8,18 @@ This section explains how redirect your gateway from one {{% tts %}} instance to
 
 <!--more-->
 
-If your gateway is using [CUPS]({{< relref "/cups" >}}) to connect to {{% tts %}}, and you want to redirect it from one {{% tts %}} instance to another, just follow the steps below. As an example, we consider redirecting a gateway from {{% ttss %}} to {{% tts %}} Cloud. 
+If your gateway is using [CUPS]({{< relref "cups" >}}) to connect to {{% tts %}}, and you want to redirect it from one {{% tts %}} instance to another, just follow the steps below. As an example, we consider redirecting a gateway from {{% ttss %}} to {{% tts %}} Cloud.
 
-First, register your gateway in the target instance ({{% tts %}} Cloud in our example). You can choose to **Generate API key for LNS** upon registering, or to follow steps to create an [LNS key]({{< relref "/cups#create-separate-cups-and-lns-api-keys" >}}) (gateway API key with linking rights) in the target instance after registering.
+First, register your gateway in the target instance ({{% tts %}} Cloud in our example). You can choose to **Generate API key for LNS** upon registering, or to follow steps to create an [LNS key]({{< relref "cups#create-separate-cups-and-lns-api-keys" >}}) (gateway API key with linking rights) in the target instance after registering.
 
 {{< figure src="../target-instance-registration.png" alt="Registering gateway in the target The Things Stack instance" >}}
 
-Copy the LNS key from the target instance (that you created in previous step). In the source instance ({{% ttss %}} in our example), navigate to your gateway's **General settings** tab and paste the LNS key you've copied in the **LoRa Basics Station LNS Authentication Key** field. 
+Copy the LNS key from the target instance (that you created in previous step). In the source instance ({{% ttss %}} in our example), navigate to your gateway's **General settings** tab and paste the LNS key you've copied in the **LoRa Basics Station LNS Authentication Key** field.
 
 Navigate to your gateway's **General settings** tab in the target instance, copy the **Gateway Server address** and paste it in the **Gateway Server address** field of the source instance.
 
 {{< figure src="../change-lns-key-and-gs-addr.png" alt="Changing LNS key and GS address in the source instance" >}}
 
 You can optionally invalidate the old LNS key in the source instance, either by deleting it or by removing the linking right.
 
-Upon the next CUPS request, the gateway will connect to the target {{% tts %}} instance and stop sending packets to the source instance. Usually, a CUPS request is sent every 24h, but in this case, it will happen sooner. Changing the Gateway Server address forces the gateway to reconnect in about 10 minutes on average. Also, invalidating the old LNS key in the source instance results in CUPS lookup being done before the 24h window finishes, during which the gateway will redirect to the target instance.
+Upon the next CUPS request, the gateway will connect to the target {{% tts %}} instance and stop sending packets to the source instance. Usually, a CUPS request is sent every 24h, but in this case, it will happen sooner. Changing the Gateway Server address forces the gateway to reconnect in about 10 minutes on average. Also, invalidating the old LNS key in the source instance results in CUPS lookup being done before the 24h window finishes, during which the gateway will redirect to the target instance.

doc/content/reference/telemetry/_index.md

@@ -5,11 +5,11 @@ aliases: [/telemetry]
 new_in_version: "3.27.1"
 ---
 
-This section contains detailed information on telemetry collected by the [CLI]({{<ref "/reference/cli">}}) and by each of {{% tts %}}\'s [components]({{<ref "/components">}}).
+This section contains detailed information on telemetry collected by the [CLI]({{<ref "/reference/cli">}}) and by each of {{% tts %}}\'s [components]({{<relref "components">}}).
 
 <!--more-->
 
-{{% tts %}}'s [CLI]({{<ref "/reference/cli">}}) and [components]({{<ref "/components">}}) have the ability to collect and send telemetry data to The Things Industries. We are interested in gaining insights on how users use {{% tts %}} in the field to give us a better idea on things that need improvement.
+{{% tts %}}'s [CLI]({{<ref "/reference/cli">}}) and [components]({{<relref "components">}}) have the ability to collect and send telemetry data to The Things Industries. We are interested in gaining insights on how users use {{% tts %}} in the field to give us a better idea on things that need improvement.
 
 {{% tts %}} does **not** collect, store and/or transmit personally identifiable information. All information collected is **anonymised** by {{% tts %}} before transmission.
 

doc/content/the-things-stack/concepts/networking/_index.md

@@ -16,7 +16,7 @@ The following table lists the default ports used.
 | **Purpose**                                              | **Protocol**                                                                                      | **Authentication** | **Port**   | **Port (TLS)** |
 | -------------------------------------------------------- | ------------------------------------------------------------------------------------------------- | ------------------ | ---------- | -------------- |
 | Gateway data                                             | [Semtech Packet Forwarder](https://github.com/Lora-net/packet_forwarder/blob/master/PROTOCOL.TXT) | None               | 1700 (UDP) | N/A            |
-| Gateway data                                             | MQTT (V2)                                                                                         | API key, token     | 1881       | 8881           |
+| Gateway data                                             | MQTT (legacy)                                                                                     | API key, token     | 1881       | 8881           |
 | Gateway data                                             | MQTT                                                                                              | API key, token     | 1882       | 8882           |
 | Application data, events                                 | MQTT                                                                                              | API key, token     | 1883       | 8883           |
 | Management, data, events                                 | gRPC                                                                                              | API key, token     | 1884       | 8884           |

doc/content/the-things-stack/management/sso/cognito/index.md

@@ -55,17 +55,17 @@ Ensure that **Cognito User Pool** is checked for **Enabled Identity Providers**.
 
 For the **Callback URL**, enter the **OAuth Callback URL** of your {{% tts %}} deployment. This is the [Server Address]({{< ref "the-things-stack/concepts/server-addresses" >}}) followed by the OAuth endpoint, which includes an **Authentication Provider ID** of your choosing:
 
-`
+```
 /oauth/login/<authentication-provider-id>/callback
-`
+```
 
 You will actually create the Authentication Provider in {{% tts %}} using this Authentication Provider ID, so remember it.
 
 For example, with a tenant `tenant1` in the `eu1` cluster and an Authentication Provider ID of `aws-cog`, the OAuth Callback URL is:
 
-`
+```
 https://tenant1.eu1.cloud.thethings.industries/oauth/login/aws-cog/callback
-`
+```
 
 Additionally, ensure the following **Allowed OAuth Scopes** are checked:
 
@@ -93,7 +93,7 @@ Finally, go to **App clients** and choose your **App Client** to view your Clien
 
 {{< figure src="secret.png" >}}
 
-Proceed to [Configure {{% tts %}} for SSO]({{< relref "../../sso#configure-the-things-stack-for-sso" >}}) using the following information:
+Proceed to [Configure {{% tts %}} for SSO]({{< relref "../sso#configure-the-things-stack-for-sso" >}}) using the following information:
 
 - **Client ID**: Provided by Cognito
 - **Client Secret**: Provided by Cognito

doc/content/the-things-stack/management/sso/google/index.md

@@ -1,7 +1,7 @@
 ---
 title: "Google OpenID Connect"
 description: ""
-weight: 
+weight:
 aliases: [/getting-started/sso/google]
 ---
 
@@ -25,23 +25,23 @@ Choose **Web application** for the **Application type**.
 
 Give the Application a **Name** of your choosing, and enter the **Redirect URI** of your {{% tts %}} deployment. The URI is the [Server Address]({{< ref "the-things-stack/concepts/server-addresses" >}}) followed by the OAuth endpoint, which includes an **Authentication Provider ID** of your choosing:
 
-`
+```
 /oauth/login/<authentication-provider-id>/callback
-`
+```
 
 You will actually create the Authentication Provider in {{% tts %}} using this Authentication Provider ID, so remember it.
 
 For example, with a tenant `tenant1` in the `eu1` cluster and an Authentication Provider ID of `goog`, the OAuth Callback URL is:
 
-`
+```
 https://tenant1.eu1.cloud.thethings.industries/oauth/login/goog/callback
-`
+```
 
 {{< figure src="callback.png" >}}
 
 Click **Create** and you will be presented with the **Client ID** and **Client Secret** for this provider.
 
-Proceed to [Configure {{% tts %}} for SSO]({{< relref "../../sso#configure-the-things-stack-for-sso" >}}) using the following information:
+Proceed to [Configure {{% tts %}} for SSO]({{< relref "../sso#configure-the-things-stack-for-sso" >}}) using the following information:
 
 - **Client ID**: Provided by Google
 - **Client Secret**: Provided by Google

doc/themes/the-things-stack/layouts/partials/head/head.html

@@ -7,7 +7,7 @@
   {{- if hasPrefix .Permalink "http" }}<link rel="canonical" href="{{ .Permalink }}" />{{ end }}
   <link rel="alternate icon" type="image/png" href="{{ "favicon.png" | relURL }}">
   <link rel="icon" type="image/svg+xml" href="{{ "favicon.svg" | relURL }}">
-  {{- $style := resources.Get "css/theme.scss" | resources.ToCSS | resources.Minify | resources.Fingerprint }}
+  {{- $style := resources.Get "css/theme.scss" | css.Sass | resources.Minify | resources.Fingerprint }}
   <link rel="stylesheet" href="{{ $style.Permalink }}" integrity="{{ $style.Data.Integrity }}" crossorigin="anonymous">
   {{- if .Site.Params.search.enabled -}}
   <link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@docsearch/css@3" />