Bumped documentation & installation docs. (#2011)

github-actions[bot] · web-flow · commit 7e1d698a0725 · 2025-03-25T23:53:59.000+01:00
Co-authored-by: lidel@users.noreply.github.com &lt;lidel&gt;
diff --git a/docs/install/command-line.md b/docs/install/command-line.md
@@ -1,7 +1,7 @@
 ---
 title: Kubo
 description: Using IPFS Kubo through the command-line allows you to do everything that IPFS Desktop can do, but at a more granular level, since you can specify which commands to run. Learn how to install it here.
-current-ipfs-version: v0.34.0
+current-ipfs-version: v0.34.1
 ---
 
 # Install IPFS Kubo
@@ -34,7 +34,7 @@ Kubo runs on most Windows, MacOS, Linux, FreeBSD and OpenBSD systems that meet t
 
 Note the following:
 - The amount of disk space your IPFS installation uses depends on how much data you're sharing. A base installation uses around 12MB of disk space.
-- You can enable automatic garbage collection via [--enable-gc](../reference/kubo/cli.md#ipfs-daemon) and adjust using [default maximum disk storage](https://github.com/ipfs/kubo/blob/v0.34.0/docs/config.md#datastorestoragemax) for data retrieved from other peers.
+- You can enable automatic garbage collection via [--enable-gc](../reference/kubo/cli.md#ipfs-daemon) and adjust using [default maximum disk storage](https://github.com/ipfs/kubo/blob/v0.34.1/docs/config.md#datastorestoragemax) for data retrieved from other peers.
 
 
 <!-- TODO: hide this footgun until https://github.com/ipfs/kubo/pull/10524 is merged and released in stable kubo 
@@ -69,13 +69,13 @@ For installation instructions for your operating system, select the appropriate
 1. Download the Linux binary from [`dist.ipfs.tech`](https://dist.ipfs.tech/#kubo).
 
    ```bash
-   wget https://dist.ipfs.tech/kubo/v0.34.0/kubo_v0.34.0_linux-amd64.tar.gz
+   wget https://dist.ipfs.tech/kubo/v0.34.1/kubo_v0.34.1_linux-amd64.tar.gz
    ```
 
 1. Unzip the file:
 
    ```bash
-   tar -xvzf kubo_v0.34.0_linux-amd64.tar.gz
+   tar -xvzf kubo_v0.34.1_linux-amd64.tar.gz
 
    > x kubo/install.sh
    > x kubo/ipfs
@@ -104,7 +104,7 @@ For installation instructions for your operating system, select the appropriate
    ```bash
    ipfs --version
 
-   > ipfs version 0.34.0
+   > ipfs version 0.34.1
    ```
 
 :::
@@ -116,27 +116,27 @@ For installation instructions for your operating system, select the appropriate
 1. Download the Windows binary from [`dist.ipfs.tech`](https://dist.ipfs.tech/#kubo).
 
    ```powershell
-   wget https://dist.ipfs.tech/kubo/v0.34.0/kubo_v0.34.0_windows-amd64.zip -Outfile kubo_v0.34.0.zip
+   wget https://dist.ipfs.tech/kubo/v0.34.1/kubo_v0.34.1_windows-amd64.zip -Outfile kubo_v0.34.1.zip
    ```
 
-1. Unzip the file to a sensible location, such as `~\Apps\kubo_v0.34.0`.
+1. Unzip the file to a sensible location, such as `~\Apps\kubo_v0.34.1`.
 
    ```powershell
-   Expand-Archive -Path kubo_v0.34.0.zip -DestinationPath ~\Apps\kubo_v0.34.0
+   Expand-Archive -Path kubo_v0.34.1.zip -DestinationPath ~\Apps\kubo_v0.34.1
    ```
 
-1. Move into the `kubo_v0.34.0` folder
+1. Move into the `kubo_v0.34.1` folder
 
    ```powershell
-   cd ~\Apps\kubo_v0.34.0\kubo
+   cd ~\Apps\kubo_v0.34.1\kubo
    ```
 
 1. Check that the `ipfs.exe` works:
 
    ```powershell
    .\ipfs.exe --version
 
-   > ipfs version 0.34.0
+   > ipfs version 0.34.1
    ```
 
    At this point, Kubo is usable. However, it's strongly recommended that you first add `ipfs.exe` to your `PATH` using the following steps:
@@ -182,7 +182,7 @@ For installation instructions for your operating system, select the appropriate
    ```powershell
    ipfs --version
 
-   > ipfs version 0.34.0
+   > ipfs version 0.34.1
    ```
 
 :::
@@ -210,7 +210,7 @@ For installation instructions for your operating system, select the appropriate
    If Kubo is installed, the version number displays. For example:
 
    ```bash
-   > ipfs version 0.34.0
+   > ipfs version 0.34.1
    ```
 :::
 
@@ -221,13 +221,13 @@ For installation instructions for your operating system, select the appropriate
 1. Download the FreeBSD binary from [`dist.ipfs.tech`](https://dist.ipfs.tech/#kubo).
 
    ```bash
-   wget https://dist.ipfs.tech/kubo/v0.34.0/kubo_v0.34.0_freebsd-amd64.tar.gz
+   wget https://dist.ipfs.tech/kubo/v0.34.1/kubo_v0.34.1_freebsd-amd64.tar.gz
    ```
 
 1. Unzip the file:
 
    ```bash
-   tar -xvzf kubo_v0.34.0_freebsd-amd64.tar.gz
+   tar -xvzf kubo_v0.34.1_freebsd-amd64.tar.gz
 
    > x kubo/install.sh
    > x kubo/ipfs
@@ -256,7 +256,7 @@ For installation instructions for your operating system, select the appropriate
    ```bash
    ipfs --version
 
-   > ipfs version 0.34.0
+   > ipfs version 0.34.1
    ```
 
 :::
@@ -268,13 +268,13 @@ For installation instructions for your operating system, select the appropriate
 1. Download the OpenBSD binary from [`dist.ipfs.tech`](https://dist.ipfs.tech/#kubo).
 
    ```bash
-   wget https://dist.ipfs.tech/kubo/v0.34.0/kubo_v0.34.0_openbsd-amd64.tar.gz
+   wget https://dist.ipfs.tech/kubo/v0.34.1/kubo_v0.34.1_openbsd-amd64.tar.gz
    ```
 
 1. Unzip the file:
 
    ```bash
-   tar -xvzf kubo_v0.34.0_openbsd-amd64.tar.gz
+   tar -xvzf kubo_v0.34.1_openbsd-amd64.tar.gz
 
    > x kubo/install.sh
    > x kubo/ipfs
@@ -303,7 +303,7 @@ For installation instructions for your operating system, select the appropriate
    ```bash
    ipfs --version
 
-   > ipfs version 0.34.0
+   > ipfs version 0.34.1
    ```
 
 :::
@@ -315,7 +315,7 @@ For installation instructions for your operating system, select the appropriate
 
 ## Build Kubo from source
 
-For the current instructions on how to manually download, compile and build Kubo from source, see the [Build from Source](https://github.com/ipfs/kubo/blob/v0.34.0/README.md#build-from-source) section in the Kubo repository.
+For the current instructions on how to manually download, compile and build Kubo from source, see the [Build from Source](https://github.com/ipfs/kubo/blob/v0.34.1/README.md#build-from-source) section in the Kubo repository.
 
 ## Determining which node to use with the command line
 
diff --git a/docs/install/run-ipfs-inside-docker.md b/docs/install/run-ipfs-inside-docker.md
@@ -1,7 +1,7 @@
 ---
 title: Install IPFS Kubo inside Docker
 description: You can run IPFS inside Docker to simplify your deployment processes, and horizontally scale your IPFS infrastructure.
-current-ipfs-version: v0.34.0
+current-ipfs-version: v0.34.1
 ---
 
 # Install IPFS Kubo inside Docker
@@ -21,7 +21,7 @@ You can run Kubo IPFS inside Docker to simplify your deployment processes, as we
 1. Start a container running ipfs and expose ports `4001` (P2P TCP/QUIC transports), `5001` (RPC API) and `8080` (Gateway):
 
     ```shell
-    docker run -d --name ipfs_host -v $ipfs_staging:/export -v $ipfs_data:/data/ipfs -p 4001:4001 -p 4001:4001/udp -p 127.0.0.1:8080:8080 -p 127.0.0.1:5001:5001 ipfs/kubo:v0.34.0
+    docker run -d --name ipfs_host -v $ipfs_staging:/export -v $ipfs_data:/data/ipfs -p 4001:4001 -p 4001:4001/udp -p 127.0.0.1:8080:8080 -p 127.0.0.1:5001:5001 ipfs/kubo:v0.34.1
     ```
 
     ::: danger NEVER EXPOSE THE RPC API TO THE PUBLIC INTERNET
@@ -71,7 +71,7 @@ You can run Kubo IPFS inside Docker to simplify your deployment processes, as we
 When starting a container running ipfs for the first time with an empty data directory, it will call `ipfs init` to initialize configuration files and generate a new keypair. At this time, you can choose which profile to apply using the `IPFS_PROFILE` environment variable:
 
 ```shell
-docker run -d --name ipfs_host -e IPFS_PROFILE=server -v $ipfs_staging:/export -v $ipfs_data:/data/ipfs -p 4001:4001 -p 4001:4001/udp -p 127.0.0.1:8080:8080 -p 127.0.0.1:5001:5001 ipfs/kubo:v0.34.0
+docker run -d --name ipfs_host -e IPFS_PROFILE=server -v $ipfs_staging:/export -v $ipfs_data:/data/ipfs -p 4001:4001 -p 4001:4001/udp -p 127.0.0.1:8080:8080 -p 127.0.0.1:5001:5001 ipfs/kubo:v0.34.1
 ```
 
 ## Customizing your node
@@ -119,22 +119,22 @@ Example:
 docker run # (....)
     --cpus="4.0" -e GOMAXPROCS=4 \
     --memory="8000m" -e GOMEMLIMIT=7500MiB \
-    ipfs/kubo:v0.34.0
+    ipfs/kubo:v0.34.1
 ```
 
 ## Private swarms inside Docker
 
 It is possible to initialize the container with a swarm key file (`/data/ipfs/swarm.key`) using the variables `IPFS_SWARM_KEY` and `IPFS_SWARM_KEY_FILE`. The `IPFS_SWARM_KEY` creates `swarm.key` with the contents of the variable itself, while `IPFS_SWARM_KEY_FILE` copies the key from a path stored in the variable. The `IPFS_SWARM_KEY_FILE` **overwrites** the key generated by `IPFS_SWARM_KEY`.
 
 ```shell
-docker run -d --name ipfs_host -e IPFS_SWARM_KEY=<your swarm key> -v $ipfs_staging:/export -v $ipfs_data:/data/ipfs -p 4001:4001 -p 4001:4001/udp -p 127.0.0.1:8080:8080 -p 127.0.0.1:5001:5001 ipfs/kubo:v0.34.0
+docker run -d --name ipfs_host -e IPFS_SWARM_KEY=<your swarm key> -v $ipfs_staging:/export -v $ipfs_data:/data/ipfs -p 4001:4001 -p 4001:4001/udp -p 127.0.0.1:8080:8080 -p 127.0.0.1:5001:5001 ipfs/kubo:v0.34.1
 ```
 
 The swarm key initialization can also be done using docker secrets, and requires `docker swarm` or `docker-compose`:
 
 ```shell
 cat your_swarm.key | docker secret create swarm_key_secret -
-docker run -d --name ipfs_host --secret swarm_key_secret -e IPFS_SWARM_KEY_FILE=/run/secrets/swarm_key_secret -v $ipfs_staging:/export -v $ipfs_data:/data/ipfs -p 4001:4001 -p 4001:4001/udp -p 127.0.0.1:8080:8080 -p 127.0.0.1:5001:5001 ipfs/kubo:v0.34.0
+docker run -d --name ipfs_host --secret swarm_key_secret -e IPFS_SWARM_KEY_FILE=/run/secrets/swarm_key_secret -v $ipfs_staging:/export -v $ipfs_data:/data/ipfs -p 4001:4001 -p 4001:4001/udp -p 127.0.0.1:8080:8080 -p 127.0.0.1:5001:5001 ipfs/kubo:v0.34.1
 ```
 
 ## Key rotation inside Docker
@@ -143,10 +143,10 @@ It is possible to do key rotation in an ephemeral container that is temporarily
 
 ```shell
 # given container named 'ipfs-test' that persists repo at /path/to/persisted/.ipfs
-docker run -d --name ipfs-test -v /path/to/persisted/.ipfs:/data/ipfs ipfs/kubo:v0.34.0
+docker run -d --name ipfs-test -v /path/to/persisted/.ipfs:/data/ipfs ipfs/kubo:v0.34.1
 docker stop ipfs-test  
 
 # key rotation works like this (old key saved under 'old-self')
-docker run --rm -it -v /path/to/persisted/.ipfs:/data/ipfs ipfs/kubo:v0.34.0 key rotate -o old-self -t ed25519
+docker run --rm -it -v /path/to/persisted/.ipfs:/data/ipfs ipfs/kubo:v0.34.1 key rotate -o old-self -t ed25519
 docker start ipfs-test # will start with the new key
 ```
diff --git a/docs/reference/kubo/cli.md b/docs/reference/kubo/cli.md
@@ -5,8 +5,8 @@ description: API documentation for the Kubo command-line executable.
 
 # Kubo command-line
 
-::: tip Generated on 2025-03-20 22:58:28, from kubo 0.34.0
-This document was autogenerated from CLI help text in [kubo 0.34.0](https://github.com/ipfs/kubo/releases/tag/v0.34.0)
+::: tip Generated on 2025-03-25 22:49:15, from kubo 0.34.1
+This document was autogenerated from CLI help text in [kubo 0.34.1](https://github.com/ipfs/kubo/releases/tag/v0.34.1)
 For issues and support, check out the [generate-cli-docs.sh](https://github.com/ipfs/ipfs-docs/blob/main/docs/reference/kubo/generate-cli-docs.sh) script on GitHub.
 :::
 
@@ -1102,13 +1102,57 @@ DESCRIPTION
     'local-discovery':
       Sets default values to fields affected by the server
       profile, enables discovery in local networks.
+    'test':
+      Reduces external interference of IPFS daemon, this
+      is useful when using the daemon in test environments.
+    'default-networking':
+      Restores default network settings.
+      Inverse profile of the test profile.
     'default-datastore':
       Configures the node to use the default datastore (flatfs).
       
       Read the "flatfs" profile description for more information on this datastore.
       
       This profile may only be applied when first initializing the node.
       
+    'pebbleds':
+      Configures the node to use the pebble high-performance datastore.
+      
+      Pebble is a LevelDB/RocksDB inspired key-value store focused on performance
+      and internal usage by CockroachDB.
+      You should use this datastore if:
+      
+      - You need a datastore that is focused on performance.
+      - You need reliability by default, but may choose to disable WAL for maximum performance when reliability is not critical.
+      - This datastore is good for multi-terabyte data sets.
+      - May benefit from tuning depending on read/write patterns and throughput.
+      - Performance is helped significantly by running on a system with plenty of memory.
+      
+      See configuration documentation at:
+      https://github.com/ipfs/kubo/blob/master/docs/datastores.md#pebbleds
+      
+      NOTE: This profile may only be applied when first initializing node at IPFS_PATH
+            via 'ipfs init --profile pebbleds'
+      
+    'lowpower':
+      Reduces daemon overhead on the system. May affect node
+      functionality - performance of content discovery and data
+      fetching may be degraded.
+      
+    'announce-off':
+      Disables Reprovide system (and announcing to Amino DHT).
+      
+      		USE WITH CAUTION:
+      		The main use case for this is setups with manual Peering.Peers config.
+      		Data from this node will not be announced on the DHT. This will make
+      		DHT-based routing and data retrieval impossible if this node is the only
+      		one hosting it, and other peers are not already connected to it.
+      
+    'announce-on':
+      Re-enables Reprovide system (reverts announce-off profile).
+    'server':
+      Disables local host discovery, recommended when
+      running IPFS on machines with public IPv4 addresses.
     'flatfs':
       Configures the node to use the flatfs datastore.
       
@@ -1129,25 +1173,6 @@ DESCRIPTION
       NOTE: This profile may only be applied when first initializing node at IPFS_PATH
             via 'ipfs init --profile flatfs'
       
-    'pebbleds':
-      Configures the node to use the pebble high-performance datastore.
-      
-      Pebble is a LevelDB/RocksDB inspired key-value store focused on performance
-      and internal usage by CockroachDB.
-      You should use this datastore if:
-      
-      - You need a datastore that is focused on performance.
-      - You need reliability by default, but may choose to disable WAL for maximum performance when reliability is not critical.
-      - This datastore is good for multi-terabyte data sets.
-      - May benefit from tuning depending on read/write patterns and throughput.
-      - Performance is helped significantly by running on a system with plenty of memory.
-      
-      See configuration documentation at:
-      https://github.com/ipfs/kubo/blob/master/docs/datastores.md#pebbleds
-      
-      NOTE: This profile may only be applied when first initializing node at IPFS_PATH
-            via 'ipfs init --profile pebbleds'
-      
     'badgerds':
       Configures the node to use the legacy badgerv1 datastore.
       
@@ -1174,33 +1199,8 @@ DESCRIPTION
       Use a random port number for swarm.
     'legacy-cid-v0':
       Makes UnixFS import produce legacy CIDv0 with no raw leaves, sha2-256 and 256 KiB chunks.
-    'test':
-      Reduces external interference of IPFS daemon, this
-      is useful when using the daemon in test environments.
-    'default-networking':
-      Restores default network settings.
-      Inverse profile of the test profile.
-    'lowpower':
-      Reduces daemon overhead on the system. May affect node
-      functionality - performance of content discovery and data
-      fetching may be degraded.
-      
-    'announce-off':
-      Disables Reprovide system (and announcing to Amino DHT).
-      
-      		USE WITH CAUTION:
-      		The main use case for this is setups with manual Peering.Peers config.
-      		Data from this node will not be announced on the DHT. This will make
-      		DHT-based routing and data retrieval impossible if this node is the only
-      		one hosting it, and other peers are not already connected to it.
-      
-    'announce-on':
-      Re-enables Reprovide system (reverts announce-off profile).
     'test-cid-v1':
       Makes UnixFS import produce modern CIDv1 with raw leaves, sha2-256 and 1 MiB chunks.
-    'server':
-      Disables local host discovery, recommended when
-      running IPFS on machines with public IPv4 addresses.
 
 SUBCOMMANDS
   ipfs config profile apply <profile> - Apply profile to config.
diff --git a/docs/reference/kubo/rpc.md b/docs/reference/kubo/rpc.md
@@ -47,8 +47,8 @@ I AM SERIOUS, DO NOT EDIT ANYTHING BELOW ;-D
 
 -->
 
-::: tip Generated on 2025-03-20, from kubo v0.34.0
-This document was autogenerated from [v0.34.0](https://github.com/ipfs/kubo/releases/tag/v0.34.0).
+::: tip Generated on 2025-03-25, from kubo v0.34.1
+This document was autogenerated from [v0.34.1](https://github.com/ipfs/kubo/releases/tag/v0.34.1).
 For issues and support, check out the [http-api-docs](https://github.com/ipfs/ipfs-docs/tree/main/tools/http-api-docs) generator on GitHub.
 :::
 
diff --git a/tools/http-api-docs/go.mod b/tools/http-api-docs/go.mod
diff --git a/tools/http-api-docs/go.sum b/tools/http-api-docs/go.sum
