Merge pull request ipfs#1439 from ipfs/bump-documentation-to-latest-versions

Update release version numbers

Author: galargh

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.17.0
+current-ipfs-version: v0.18.0
 ---
 
 # Install IPFS Kubo
@@ -31,13 +31,13 @@ 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.17.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.18.0/docs/config.md#datastorestoragemax) for data retrieved from other peers.
 
 ### Kubo on resource-constrained systems 
 
 If you are running Kubo on a resource-constrained system (such as a Raspberry Pi), you should complete the following steps:
 
-  1. Install OpenSSL and rebuild Kubo manually with `make build GOTAGS=openssl`. See the [download and compile](https://github.com/ipfs/kubo/blob/v0.17.0/README.md#download-and-compile-ipfs) section for more information on compiling Kubo.
+  1. Install OpenSSL and rebuild Kubo manually with `make build GOTAGS=openssl`. See the [download and compile](https://github.com/ipfs/kubo/blob/v0.18.0/README.md#download-and-compile-ipfs) section for more information on compiling Kubo.
   1. Initialize your daemon with the `lowpower` profile. This reduces daemon overhead on the system but may degrade performance of content discovery and data fetching.
 
   ```bash
@@ -73,27 +73,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.17.0/kubo_v0.17.0_windows-amd64.zip -Outfile kubo_v0.17.0.zip
+   wget https://dist.ipfs.tech/kubo/v0.18.0/kubo_v0.18.0_windows-amd64.zip -Outfile kubo_v0.18.0.zip
    ```
 
-1. Unzip the file to a sensible location, such as `~\Apps\kubo_v0.17.0`.
+1. Unzip the file to a sensible location, such as `~\Apps\kubo_v0.18.0`.
 
    ```powershell
-   Expand-Archive -Path kubo_v0.17.0.zip -DestinationPath ~\Apps\kubo_v0.17.0
+   Expand-Archive -Path kubo_v0.18.0.zip -DestinationPath ~\Apps\kubo_v0.18.0
    ```
 
-1. Move into the `kubo_v0.17.0` folder
+1. Move into the `kubo_v0.18.0` folder
 
    ```powershell
-   cd ~\Apps\kubo_v0.17.0\kubo
+   cd ~\Apps\kubo_v0.18.0\kubo
    ```
 
 1. Check that the `ipfs.exe` works:
 
    ```powershell
    .\ipfs.exe --version
 
-   > ipfs version 0.17.0
+   > ipfs version 0.18.0
    ```
 
    At this point, Kubo is usable. However, it's strongly recommended that you first add `ipfs.exe` to your `PATH` using the following steps:
@@ -139,7 +139,7 @@ For installation instructions for your operating system, select the appropriate
    ```powershell
    ipfs --version
 
-   > ipfs version 0.17.0
+   > ipfs version 0.18.0
    ```
 
 :::
@@ -160,28 +160,28 @@ For installation instructions for your operating system, select the appropriate
 1. Download the appropriate macOS binary from [`dist.ipfs.tech`](https://dist.ipfs.tech/#kubo) based on your hardware. For example:
 
    ```bash
-   curl -O https://dist.ipfs.tech/kubo/v0.17.0/kubo_v0.17.0_darwin-amd64.tar.gz
+   curl -O https://dist.ipfs.tech/kubo/v0.18.0/kubo_v0.18.0_darwin-amd64.tar.gz
    ```
 
    > :warning:
    > Ensure that you download and install the appropriate binary, as the binary for an Intel-based system won't work on a system with Apple Silicon, and vice-versa.
 
-   - _If you are using hardware with Apple Silicon, download the `darwin-arm64` binary._ For example, to download the IPFS binary for `Kubo v0.17.0` for an Apple-based system, run the following command:
+   - _If you are using hardware with Apple Silicon, download the `darwin-arm64` binary._ For example, to download the IPFS binary for `Kubo v0.18.0` for an Apple-based system, run the following command:
 
      ```bash
-     curl -O https://dist.ipfs.tech/kubo/v0.17.0/kubo_v0.17.0_darwin-arm64.tar.gz
+     curl -O https://dist.ipfs.tech/kubo/v0.18.0/kubo_v0.18.0_darwin-arm64.tar.gz
      ```
 
-   - _If you are using hardware with an Intel Processor, download the `darwin-amd64` binary._ For example, to download the IPFS binary for `Kubo v0.17.0` for an Intel-based system, run the following command:
+   - _If you are using hardware with an Intel Processor, download the `darwin-amd64` binary._ For example, to download the IPFS binary for `Kubo v0.18.0` for an Intel-based system, run the following command:
 
      ```bash
-     curl -O https://dist.ipfs.tech/kubo/v0.17.0/kubo_v0.17.0_darwin-amd64.tar.gz
+     curl -O https://dist.ipfs.tech/kubo/v0.18.0/kubo_v0.18.0_darwin-amd64.tar.gz
      ```
 
-1. Unzip the file. For example, to unzip `Kubo v0.17.0` for an Intel-based system:
+1. Unzip the file. For example, to unzip `Kubo v0.18.0` for an Intel-based system:
 
    ```bash
-   tar -xvzf kubo_v0.17.0_darwin-amd64.tar.gz
+   tar -xvzf kubo_v0.18.0_darwin-amd64.tar.gz
    ```
 
    The following output displays:
@@ -219,7 +219,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.17.0
+   > ipfs version 0.18.0
    ```
 
 :::
@@ -231,13 +231,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.17.0/kubo_v0.17.0_linux-amd64.tar.gz
+   wget https://dist.ipfs.tech/kubo/v0.18.0/kubo_v0.18.0_linux-amd64.tar.gz
    ```
 
 1. Unzip the file:
 
    ```bash
-   tar -xvzf kubo_v0.17.0_linux-amd64.tar.gz
+   tar -xvzf kubo_v0.18.0_linux-amd64.tar.gz
 
    > x kubo/install.sh
    > x kubo/ipfs
@@ -266,7 +266,7 @@ For installation instructions for your operating system, select the appropriate
    ```bash
    ipfs --version
 
-   > ipfs version 0.17.0
+   > ipfs version 0.18.0
    ```
 
 :::
@@ -278,13 +278,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.17.0/kubo_v0.17.0_freebsd-amd64.tar.gz
+   wget https://dist.ipfs.tech/kubo/v0.18.0/kubo_v0.18.0_freebsd-amd64.tar.gz
    ```
 
 1. Unzip the file:
 
    ```bash
-   tar -xvzf kubo_v0.17.0_freebsd-amd64.tar.gz
+   tar -xvzf kubo_v0.18.0_freebsd-amd64.tar.gz
 
    > x kubo/install.sh
    > x kubo/ipfs
@@ -313,7 +313,7 @@ For installation instructions for your operating system, select the appropriate
    ```bash
    ipfs --version
 
-   > ipfs version 0.17.0
+   > ipfs version 0.18.0
    ```
 
 :::
@@ -325,13 +325,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.17.0/kubo_v0.17.0_openbsd-amd64.tar.gz
+   wget https://dist.ipfs.tech/kubo/v0.18.0/kubo_v0.18.0_openbsd-amd64.tar.gz
    ```
 
 1. Unzip the file:
 
    ```bash
-   tar -xvzf kubo_v0.17.0_openbsd-amd64.tar.gz
+   tar -xvzf kubo_v0.18.0_openbsd-amd64.tar.gz
 
    > x kubo/install.sh
    > x kubo/ipfs
@@ -360,7 +360,7 @@ For installation instructions for your operating system, select the appropriate
    ```bash
    ipfs --version
 
-   > ipfs version 0.17.0
+   > ipfs version 0.18.0
    ```
 
 :::
@@ -372,7 +372,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.17.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.18.0/README.md#build-from-source) section in the Kubo repository.
 
 ## Determining which node to use with the command line
 

docs/reference/kubo/cli.md

@@ -5,22 +5,22 @@ description: API documentation for the Kubo command-line executable.
 
 # Kubo command-line
 
-::: tip Generated on 2022-11-22 16:36:20, from kubo 0.17.0
-This document was autogenerated from CLI help text in [kubo 0.17.0](https://github.com/ipfs/kubo/releases/tag/v0.17.0)
+::: tip Generated on 2023-01-24 05:33:54, from kubo 0.18.0
+This document was autogenerated from CLI help text in [kubo 0.18.0](https://github.com/ipfs/kubo/releases/tag/v0.18.0)
 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.
 :::
 
 <!-- DO NOT EDIT THIS FILE. This file is auto-generated from `generate-cli-docs.sh`. Any changes you make to this file will be overwritten. To edit this file, change the contents of the `generate-cli-docs.sh` script. -->
 
 IPFS can run in either _online_ or _offline_ mode. Online mode is when you have IPFS running separately as a daemon process. If you do not have an IPFS daemon running, you are in offline mode. Some commands, like `ipfs swarm peers`, are only supported when online.
 
-The [command-line quickstart guide](../../how-to/command-line-quick-start.md#take-your-node-online) explains how to start the IPFS daemon and take your node online.
+The [command-line quickstart guide](/how-to/command-line-quick-start/#take-your-node-online) explains how to start the IPFS daemon and take your node online.
 
 
 
 ### Alignment with Kubo RPC API
 
-Every command usable from the CLI is also available through the [RPC API v0](../../reference/kubo/rpc.md). For example:
+Every command usable from the CLI is also available through the [RPC API v0](/reference/kubo/rpc). For example:
 
 ```sh
 > ipfs swarm peers
@@ -1044,16 +1044,6 @@ SYNOPSIS
 DESCRIPTION
 
   Available profiles:
-    'server':
-      Disables local host discovery, recommended when
-      running IPFS on machines with public IPv4 addresses.
-    '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.
-      
     'flatfs':
       Configures the node to use the flatfs datastore.
       
@@ -1070,15 +1060,6 @@ DESCRIPTION
       
       This profile may only be applied when first initializing the node.
       
-    '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.
     'badgerds':
       Configures the node to use the experimental badger datastore.
       
@@ -1104,6 +1085,25 @@ DESCRIPTION
       
     'randomports':
       Use a random port number for swarm.
+    '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.
+      
+    '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.
@@ -1236,7 +1236,7 @@ DESCRIPTION
   
     ipfs config Addresses.Gateway /ip4/127.0.0.1/tcp/8082
   
-  The API address can be changed the same way:
+  The RPC API address can be changed the same way:
   
     ipfs config Addresses.API /ip4/127.0.0.1/tcp/5002
   
@@ -1247,14 +1247,14 @@ DESCRIPTION
   
     ipfs config Addresses.Gateway /ip4/0.0.0.0/tcp/8080
   
-  Be careful if you expose the API. It is a security risk, as anyone could
+  Be careful if you expose the RPC API. It is a security risk, as anyone could
   control your node remotely. If you need to control the node remotely,
   make sure to protect the port as you would other services or database
   (firewall, authenticated proxy, etc).
   
   HTTP Headers
   
-  ipfs supports passing arbitrary headers to the API and Gateway. You can
+  ipfs supports passing arbitrary headers to the RPC API and Gateway. You can
   do this by setting headers on the API.HTTPHeaders and Gateway.HTTPHeaders
   keys:
   
@@ -1288,18 +1288,6 @@ DESCRIPTION
   
     export IPFS_PATH=/path/to/ipfsrepo
   
-  Routing
-  
-  IPFS by default will use a DHT for content routing. There is an alternative
-  that operates the DHT in a 'client only' mode that can be enabled by
-  running the daemon as:
-  
-    ipfs daemon --routing=dhtclient
-  
-  Or you can set routing to dhtclient in the config:
-  
-    ipfs config Routing.Type dhtclient
-  
   DEPRECATION NOTICE
   
   Previously, ipfs used an environment variable as seen below:
@@ -5895,8 +5883,8 @@ ARGUMENTS
 
 OPTIONS
 
-  --min-used-limit-perc  int - Display only resources that are using above the
-                               specified percentage.
+  --min-used-limit-perc  int - Only display resources that are using above the
+                               specified percentage of their respective limit.
 
 DESCRIPTION
 
@@ -5910,6 +5898,9 @@ DESCRIPTION
   - all           -- reports the resource usage for all currently active scopes.
   
   The output of this command is JSON.
+  
+  To see all resources that are close to hitting their respective limit, one can do something like:
+    ipfs swarm stats --min-used-limit-perc=90 all
 
 
 ```

docs/reference/kubo/rpc.md

@@ -47,8 +47,8 @@ I AM SERIOUS, DO NOT EDIT ANYTHING BELOW ;-D
 
 -->
 
-::: tip Generated on 2023-01-19, from kubo v0.17.0
-This document was autogenerated from [v0.17.0](https://github.com/ipfs/kubo/releases/tag/v0.17.0).
+::: tip Generated on 2023-01-24, from kubo v0.18.0
+This document was autogenerated from [v0.18.0](https://github.com/ipfs/kubo/releases/tag/v0.18.0).
 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.
 :::
 
@@ -4362,7 +4362,7 @@ Report resource usage for a scope.
 ### Arguments
 
 - `arg` [string]: scope of the stat report Required: **yes**.
-- `min-used-limit-perc` [int]: Display only resources that are using above the specified percentage. Required: no.
+- `min-used-limit-perc` [int]: Only display resources that are using above the specified percentage of their respective limit. Required: no.
 
 
 ### Response

tools/http-api-docs/go.mod

@@ -5,8 +5,8 @@ go 1.16
 require (
 	github.com/Stebalien/go-json-doc v0.0.2
 	github.com/ipfs/go-cid v0.3.2
-	github.com/ipfs/go-ipfs-cmds v0.8.1
-	github.com/ipfs/kubo v0.17.0
+	github.com/ipfs/go-ipfs-cmds v0.8.2
+	github.com/ipfs/kubo v0.18.0
 	github.com/libp2p/go-libp2p-core v0.20.1
-	github.com/multiformats/go-multiaddr v0.7.0
+	github.com/multiformats/go-multiaddr v0.8.0
 )