chore(deps): update dependency node to v24.14.0

This PR contains the following updates:

| Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Adoption](https://docs.renovatebot.com/merge-confidence/) | [Passing](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) |
|---|---|---|---|---|---|
| [astro](https://astro.build) ([source](https://github.com/withastro/astro/tree/HEAD/packages/astro)) | [`5.17.3` → `5.18.0`](https://renovatebot.com/diffs/npm/astro/5.17.3/5.18.0) | ![age](https://developer.mend.io/api/mc/badges/age/npm/astro/5.18.0?slim=true) | ![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/astro/5.18.0?slim=true) | ![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/astro/5.17.3/5.18.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/astro/5.17.3/5.18.0?slim=true) |

---

### Release Notes

<details>
<summary>withastro/astro (astro)</summary>

### [`v5.18.0`](https://github.com/withastro/astro/releases/tag/astro%405.18.0)

[Compare Source](https://github.com/withastro/astro/compare/astro@5.17.3...astro@5.18.0)

##### Minor Changes

- [#&#8203;15589](https://github.com/withastro/astro/pull/15589) [`b7dd447`](b7dd447e31) Thanks [@&#8203;qzio](https://github.com/qzio)! - Adds a new `security.actionBodySizeLimit` option to configure the maximum size of Astro Actions request bodies.

  This lets you increase the default 1 MB limit when your actions need to accept larger payloads. For example, actions that handle file uploads or large JSON payloads can now opt in to a higher limit.

  If you do not set this option, Astro continues to enforce the 1 MB default to help prevent abuse.

  ```js
  // astro.config.mjs
  export default defineConfig({
    security: {
      actionBodySizeLimit: 10 * 1024 * 1024, // set to 10 MB
    },
  });
  ```

##### Patch Changes

- [#&#8203;15594](https://github.com/withastro/astro/pull/15594) [`efae11c`](efae11cef1) Thanks [@&#8203;qzio](https://github.com/qzio)! - Fix X-Forwarded-Proto validation when allowedDomains includes both protocol and hostname fields. The protocol check no longer fails due to hostname mismatch against the hardcoded test URL.

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update again.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yNS43IiwidXBkYXRlZEluVmVyIjoiNDMuMjUuNyIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiZGVwZW5kZW5jeSJdfQ==-->

Reviewed-on: #172
Co-authored-by: Renovate Bot <renovate-bot@alexlebens.net>
Co-committed-by: Renovate Bot <renovate-bot@alexlebens.net>

.gitea/workflows/release-image-gitea.yml

@@ -22,7 +22,7 @@ jobs:
       - name: Set up Node.js
         uses: actions/setup-node@v6
         with:
-          node-version: 24.13.1
+          node-version: 24.14.0
           cache: pnpm
 
       - name: Install Dependencies

.gitea/workflows/release-image-harbor.yml

@@ -22,7 +22,7 @@ jobs:
       - name: Set up Node.js
         uses: actions/setup-node@v6
         with:
-          node-version: 24.13.1
+          node-version: 24.14.0
           cache: pnpm
 
       - name: Install Dependencies

.gitea/workflows/test-build.yaml

@@ -24,7 +24,7 @@ jobs:
       - name: Set up Node.js
         uses: actions/setup-node@v6
         with:
-          node-version: 24.13.1
+          node-version: 24.14.0
           cache: pnpm
 
       - name: Install Dependencies

Dockerfile

@@ -28,7 +28,7 @@ ENV HOST=0.0.0.0
 ENV SITE_URL=https://docs.alexlebens.dev
 ENV PORT=4321
 
-LABEL version="0.1.3"
+LABEL version="0.1.5"
 LABEL description="Astro based documentation website"
 
 EXPOSE $PORT

package.json

@@ -1,7 +1,7 @@
 {
   "name": "site-documentation",
   "type": "module",
-  "version": "0.1.3",
+  "version": "0.1.5",
   "scripts": {
     "dev": "astro dev",
     "build": "astro build",

src/content/docs/guides/talos-upgrade-1-12-0.md

@@ -1,5 +1,5 @@
 ---
-title: Talos Upgrade
+title: Talos Upgrade 1.12.0
 description: Steps followed for the v1.12.0 upgrade process
 ---
 

src/content/docs/guides/talos-upgrade-generic.md

@@ -0,0 +1,68 @@
+---
+title: Talos Upgrade Generic
+description: Steps followed for the standard upgrade process
+---
+
+This is the standard upgrade process for Talos. Relatively simple, just verify, run commands, and verify.
+
+## Health Check
+
+### Etcd
+
+Check status of etcd, ensure there is a leader and there are no errors.
+
+```bash
+talosctl -n 10.232.1.11,10.232.1.12,10.232.1.13 etcd status
+```
+
+### Ceph
+
+Check if ceph is healthy:
+
+Either browse to the [webpage](https://ceph.alexlebens.net/#/dashboard), or run the following commands on the tools container
+
+```bash
+kubectl -n rook-ceph exec -it $(kubectl -n rook-ceph get pod -l "app=rook-ceph-tools" -o jsonpath='{.items\[\*].metadata.name}') -- bash
+```
+
+Inside the rook-ceph-tools container check the status:
+```bash
+ceph status
+```
+
+### Cloudnative-PG
+
+Check the status of the Cloudnative-PG clusters to ensure they are all healthy. There is potential data loss if a worker node has a failure or the local volume isn't reattached.
+
+[Dashboard](https://grafana.alexlebens.net/d/cloudnative-pg/cloudnativepg)
+
+### Garage
+
+Check the status of the Garage cluster to ensure there is no data loss of the local S3 store. This will result in data loss of short term WALs if this cluster fails
+
+[Dashboard](https://garage-webui.alexlebens.net/)
+
+## Upgrade
+
+Reference the [config repo](https://gitea.alexlebens.dev/alexlebens/talos-config/src/branch/main) for the exact commands, links to the factory page, and update the image versions. Each type has its own image string.
+
+As an example to upgrade a NUC node:
+```bash
+talosctl upgrade --nodes 10.232.1.23 --image factory.talos.dev/metal-installer/495176274ce8f9e87ed052dbc285c67b2a0ed7c5a6212f5c4d086e1a9a1cf614:v1.12.0
+```
+
+# Apply new configuration
+
+Use the generate command in the README of the talos-config repo to make the configuration to be supplied.
+
+As an example to apply that generated config to a NUC node:
+```bash
+talosctl apply-config -f generated/worker-nuc.yaml -n 10.232.1.23
+```
+
+## Verification
+
+Verify all is health on the dashboard:
+```bash
+talosctl -n 10.232.1.23 dashboard
+```