chore(deps-dev): bump js-yaml from 4.1.0 to 4.1.1 in the npm_and_yarn group across 1 directory

.github/workflows/preview.yml

@@ -35,6 +35,6 @@ jobs:
         with:
           source-dir: .vitepress/dist
           deploy-repository: celestiaorg/docs-preview
-          token: ${{ secrets.PREVIEW_DEPLOY }}
+          token: ${{ secrets.PR_PREVIEW_DEPLOY }}
           preview-branch: main
           umbrella-dir: .

.vitepress/config.ts

@@ -416,10 +416,6 @@ function sidebarHome() {
                   text: "Arabica devnet",
                   link: "/how-to-guides/arabica-devnet",
                 },
-                {
-                  text: "Mammoth testnet",
-                  link: "/how-to-guides/mammoth",
-                },
                 {
                   text: "Local devnet",
                   link: "/how-to-guides/local-devnet",
@@ -435,10 +431,6 @@ function sidebarHome() {
                   collapsed: true,
                   items: [
                     { text: "Light node", link: "/how-to-guides/light-node" },
-                    {
-                      text: "Full node",
-                      link: "/how-to-guides/full-storage-node",
-                    },
                     { text: "Bridge node", link: "/how-to-guides/bridge-node" },
                   ],
                 },
@@ -685,15 +677,15 @@ function sidebarHome() {
               link: "/how-to-guides/submit-data",
             },
             {
-              text: "Celestia clients",
+              text: "Celestia transaction (tx) clients",
               collapsed: true,
               items: [
                 {
                   text: "Overview",
                   link: "/how-to-guides/client/overview",
                 },
                 {
-                  text: "Golang client guide",
+                  text: "Golang tx client guide",
                   link: "/how-to-guides/client/go",
                 },
               ],

.vitepress/constants/arabica_versions.js

@@ -1,7 +1,7 @@
 const arabicaVersions = Object.freeze({
-  "app-latest-tag": "v6.1.2-arabica",
-  "app-latest-sha": "bd8fc305106a9af4624ee9ca79a9479dc226bb92",
-  "node-latest-tag": "v0.28.1-arabica",
-  "node-latest-sha": "df2e63b84e2db8d3c2fbd380168c4a1f7be42b92",
+  "app-latest-tag": "v6.2.5-arabica",
+  "app-latest-sha": "7b98de1e3bbb196cb358825220bf4a8f8fc4c81b",
+  "node-latest-tag": "v0.28.3-arabica",
+  "node-latest-sha": "72ca378cd924772e96ea9537352572a25b8996ca",
 });
 export default arabicaVersions;

.vitepress/constants/mainnet_versions.js

@@ -1,7 +1,7 @@
 const mainnetVersions = Object.freeze({
-  "app-latest-tag": "v5.0.11",
-  "app-latest-sha": "4e34cf6bac0bc9c7a3be796470e6f03cd7b34546",
-  "node-latest-tag": "v0.26.4",
-  "node-latest-sha": "1b84e2b3f0df39a6f2197096fb2a58d9cd250687",
+  "app-latest-tag": "v6.2.5",
+  "app-latest-sha": "52a3cfadbf4439e5e1bd89a8c47e14d3209ca525",
+  "node-latest-tag": "v0.28.2",
+  "node-latest-sha": "e4384c0f4b5de00d65e321ee9f4f400850165e6d",
 });
 export default mainnetVersions;

.vitepress/constants/mocha_versions.js

@@ -1,7 +1,7 @@
 const mochaVersions = Object.freeze({
-  "app-latest-tag": "v6.0.5-mocha",
-  "app-latest-sha": "6d05e9ea9ad801cb717df404bc50f65583cc2033",
-  "node-latest-tag": "v0.27.5-mocha",
-  "node-latest-sha": "e6a940b6c222a9f73590462329fa4a1a3c1e2d3e",
+  "app-latest-tag": "v6.2.5-mocha",
+  "app-latest-sha": "7b98de1e3bbb196cb358825220bf4a8f8fc4c81b",
+  "node-latest-tag": "v0.28.2-mocha",
+  "node-latest-sha": "e4384c0f4b5de00d65e321ee9f4f400850165e6d",
 });
 export default mochaVersions;

how-to-guides/celestia-node-store-structure.md

@@ -12,7 +12,7 @@ configuration, and other information relevant to the node.
 The following are the directories and files found in the datastore:
 
 - `/blocks`: This directory stores blocks. Each file contained in this directory
-  represents a block on Celestia and contains its associated data. This directory is present in the datastore for bridge and full nodes but not light nodes, as light nodes do not store blocks.
+  represents a block on Celestia and contains its associated data. This directory is present in the datastore for bridge nodes but not light nodes, as light nodes do not store blocks.
 
 - `/data`: This directory contains block headers and various files belonging to the node's log-structured merge (LSM) storage system. The LSM files (such as `DISCARD`, `KEYREGISTRY`, and `MANIFEST`) manage the efficient storage and retrieval of data.
 

how-to-guides/celestia-node-troubleshooting.md

@@ -89,7 +89,7 @@ manually specify the `--node.store` flag for each RPC request.
 
 - The presence of a lock signifies a running node.
 - Networks are ordered as Mainnet Beta, Mocha, Arabica, private, custom.
-- Node types are ordered as bridge, full, and light.
+- Node types are ordered as bridge and light.
 - Each network has only one running node type.
 - Multiple nodes of the same network and type are prohibited
   (resulting in an `Error: node: store is in use`).
@@ -121,8 +121,8 @@ celestia <node-type> init --node.store /home/user/celestia-<node-type>-location/
 Next, start your node:
 
 ```bash
-celestia full start --core.ip rpc-mocha.pops.one --p2p.network mocha \
-    --node.store /home/user/celestia-<node-type>-location/ --core.port <port>
+celestia bridge start --core.ip rpc-mocha.pops.one --p2p.network mocha \
+    --node.store /home/user/celestia-bridge-location/ --core.port <port>
 ```
 
 If you choose to change the location of your node store,
@@ -137,15 +137,15 @@ When using `cel-key`, the process is different.
 To show the keys you should add `--keyring-dir` like this example:
 
 ```bash
-./cel-key list --p2p.network mocha --node.type full \
-    --keyring-dir /home/user/celestia-<node-type>-location/keys/
+./cel-key list --p2p.network mocha --node.type bridge \
+    --keyring-dir /home/user/celestia-bridge-location/keys/
 ```
 
 ### Examples
 
-#### Mainnet Beta full and Mocha light
+#### Mainnet Beta bridge and Mocha light
 
-This example uses a Mainnet Beta full node and a Mocha light node. When
+This example uses a Mainnet Beta bridge node and a Mocha light node. When
 making the request:
 
 ```bash
@@ -159,9 +159,9 @@ The request will go to the Mainnet Beta node, and a 401 will show in
 this node's logs. Note that a 401 is expected because this blob was
 posted to Mocha and neither the namespace nor the blob exist on Mainnet Beta.
 
-#### Mocha full and Arabica light
+#### Mocha bridge and Arabica light
 
-This example uses a Mocha full node and an Arabica light node. When
+This example uses a Mocha bridge node and an Arabica light node. When
 making the request:
 
 ```bash
@@ -177,7 +177,7 @@ making the request:
 }
 ```
 
-The request will go to the Mocha full node, and result shown as expected.
+The request will go to the Mocha bridge node, and result shown as expected.
 
 #### Using a custom rpc.config address
 
@@ -232,7 +232,7 @@ celestia <node-type> start --p2p.network <network>
 
 ## Clearing the data store
 
-For **bridge, full, and light nodes**,
+For **bridge and light nodes**,
 remove the data store with this command:
 
 ```bash
@@ -314,7 +314,7 @@ sudo systemctl restart celestia-bridge
 
 ## Error: "no space left on device"
 
-When a bridge or full storage node runs on `ext4` file system, there will be errors like the following due to large folder size:
+When a bridge node runs on `ext4` file system, there will be errors like the following due to large folder size:
 
 ```bash-vue
 ERROR   header/sync     sync/sync.go:227        syncing headers {"from": 5074102, "to": 5161144, "err": "creating file: creating ODSQ4 file: creating Q4 file: creating Q4 file: open /root/.celestia-bridge-{{constants.mochaChainId}}/blocks/C9ADF6D9F862D92993D67977DE407D17ECF7F1DACE5FB7FE9A6845F4BD0172CE.q4: no space left on device"}

how-to-guides/celestia-node-trusted-hash.md

@@ -50,7 +50,7 @@ By configuring these fields, your light node will maintain history from the spec
 3. Set the trusted height & hash in your config file
    1. Open your `config.toml` at `.celestia-light/config.toml` (or `.celestia-light-<other-network>/config.toml`)
    2. Set `Header.Syncer.SyncFromHeight` to the trusted height (e.g. `SyncFromHeight = 123456`)
-   3. Set `Header.Syncer.SyncFromHash` to the trusted hash (e.g. `SyncFromHash = "<hash_of_block_n>"`)
+   3. Set `Header.Syncer.SyncFromHash` to the trusted hash (e.g. `SyncFromHash = "<hash_of_block_n>"`, with **no `0x` prefix**.)
 4. Run the node:
 
 ```sh

how-to-guides/celestia-node.md

@@ -127,10 +127,10 @@ You can install the latest version or specify a particular version:
 
 ```bash-vue
 # Install latest version
-bash -c "$(curl -sL https://docs.celestia.org/celestia-node.sh)"
+bash -c "$(curl -sL https://raw.githubusercontent.com/celestiaorg/docs/main/public/celestia-node.sh)"
 
 # Install specific version, Mainnet Beta in this example
-bash -c "$(curl -sL https://docs.celestia.org/celestia-node.sh)" -- -v {{mainnetVersions['node-latest-tag']}}
+bash -c "$(curl -sL https://raw.githubusercontent.com/celestiaorg/docs/main/public/celestia-node.sh)" -- -v {{mainnetVersions['node-latest-tag']}}
 ```
 
 The script will: