github.com/rclone/rclone@v1.66.1-0.20240517100346-7b89735ae726/docs/content/commands/rclone_selfupdate.md (about) 1 --- 2 title: "rclone selfupdate" 3 description: "Update the rclone binary." 4 slug: rclone_selfupdate 5 url: /commands/rclone_selfupdate/ 6 versionIntroduced: v1.55 7 # autogenerated - DO NOT EDIT, instead edit the source code in cmd/selfupdate/ and as part of making a release run "make commanddocs" 8 --- 9 # rclone selfupdate 10 11 Update the rclone binary. 12 13 ## Synopsis 14 15 This command downloads the latest release of rclone and replaces the 16 currently running binary. The download is verified with a hashsum and 17 cryptographically signed signature; see [the release signing 18 docs](/release_signing/) for details. 19 20 If used without flags (or with implied `--stable` flag), this command 21 will install the latest stable release. However, some issues may be fixed 22 (or features added) only in the latest beta release. In such cases you should 23 run the command with the `--beta` flag, i.e. `rclone selfupdate --beta`. 24 You can check in advance what version would be installed by adding the 25 `--check` flag, then repeat the command without it when you are satisfied. 26 27 Sometimes the rclone team may recommend you a concrete beta or stable 28 rclone release to troubleshoot your issue or add a bleeding edge feature. 29 The `--version VER` flag, if given, will update to the concrete version 30 instead of the latest one. If you omit micro version from `VER` (for 31 example `1.53`), the latest matching micro version will be used. 32 33 Upon successful update rclone will print a message that contains a previous 34 version number. You will need it if you later decide to revert your update 35 for some reason. Then you'll have to note the previous version and run the 36 following command: `rclone selfupdate [--beta] OLDVER`. 37 If the old version contains only dots and digits (for example `v1.54.0`) 38 then it's a stable release so you won't need the `--beta` flag. Beta releases 39 have an additional information similar to `v1.54.0-beta.5111.06f1c0c61`. 40 (if you are a developer and use a locally built rclone, the version number 41 will end with `-DEV`, you will have to rebuild it as it obviously can't 42 be distributed). 43 44 If you previously installed rclone via a package manager, the package may 45 include local documentation or configure services. You may wish to update 46 with the flag `--package deb` or `--package rpm` (whichever is correct for 47 your OS) to update these too. This command with the default `--package zip` 48 will update only the rclone executable so the local manual may become 49 inaccurate after it. 50 51 The [rclone mount](/commands/rclone_mount/) command may 52 or may not support extended FUSE options depending on the build and OS. 53 `selfupdate` will refuse to update if the capability would be discarded. 54 55 Note: Windows forbids deletion of a currently running executable so this 56 command will rename the old executable to 'rclone.old.exe' upon success. 57 58 Please note that this command was not available before rclone version 1.55. 59 If it fails for you with the message `unknown command "selfupdate"` then 60 you will need to update manually following the install instructions located 61 at https://rclone.org/install/ 62 63 64 ``` 65 rclone selfupdate [flags] 66 ``` 67 68 ## Options 69 70 ``` 71 --beta Install beta release 72 --check Check for latest release, do not download 73 -h, --help help for selfupdate 74 --output string Save the downloaded binary at a given path (default: replace running binary) 75 --package string Package format: zip|deb|rpm (default: zip) 76 --stable Install stable release (this is the default) 77 --version string Install the given rclone version (default: latest) 78 ``` 79 80 81 See the [global flags page](/flags/) for global options not listed here. 82 83 # SEE ALSO 84 85 * [rclone](/commands/rclone/) - Show help for rclone commands, flags and backends. 86