commit e2531e08bec806f9bb9108999f2a234d6799996d
Author: Nick Craig-Wood <nick@craig-wood.com>
Date:   Mon Mar 8 10:04:23 2021 +0000

    Version v1.54.1

commit 86babc63937c78d927c39a69c5c671014142df4e
Author: Nick Craig-Wood <nick@craig-wood.com>
Date:   Sun Mar 7 16:42:22 2021 +0000

    build: fix nfpm install by using the released binary

commit d45d48cbe528f7e2bab6ce4208ed5d85fd0c9ccb
Author: Ivan Andreev <ivandeex@gmail.com>
Date:   Sun Mar 7 09:45:45 2021 +0300

    chunker: fix integration tests after backport commit 6baa4e294
    
    It was my stupid typo: "f.base.NewObject" instead of correct "f.NewObject"
    I made it during backport. The commit on master was correct.

commit 7ad2c22d5b6ceff08ff1386c9e2b82714394ed57
Author: edwardxml <56691903+edwardxml@users.noreply.github.com>
Date:   Wed Feb 17 22:37:17 2021 +0000

    docs: remove dead link from rc.md (#5038)

commit 0cfcc08be19e0eb21dfaee425765bc7a2995ff0e
Author: Dmitry Chepurovskiy <me@dm3ch.net>
Date:   Wed Feb 17 15:04:26 2021 +0300

    s3: Fix shared_credentials_file auth
    
    S3 backend shared_credentials_file option wasn't working neither from
    config option nor from command line option. This was caused cause
    shared_credentials_file_provider works as part of chain provider, but in
    case user haven't specified access_token and access_key we had removed
    (set nil) to credentials field, that may contain actual credentials got
    from ChainProvider.
    
    AWS_SHARED_CREDENTIALS_FILE env varible as far as i understood worked,
    cause aws_sdk code handles it as one of default auth options, when
    there's not configured credentials.

commit 2c4a25de5bc062b291a12cbdbb0c0b68db662ca8
Author: edwardxml <56691903+edwardxml@users.noreply.github.com>
Date:   Tue Feb 16 22:20:49 2021 +0000

    docs: convert bogus example link to code
    
    Convert the bogus example plex url from a url that is auto created to code format that hopefully isn't.

commit f5a95b2ad09f949dce5a796d475e733ca9463bf3
Author: edwardxml <56691903+edwardxml@users.noreply.github.com>
Date:   Tue Feb 16 22:16:03 2021 +0000

    docs: badly formed link
    
    Fix for a badly formed link created in earlier rewrite

commit f2caa0eabbe04e78bdffcc65d8ffc0cfbefc38a2
Author: Nick Craig-Wood <nick@craig-wood.com>
Date:   Tue Feb 16 17:15:05 2021 +0000

    vfs: document simultaneous usage with the same cache shouldn't be used
    
    Fixes #2227

commit 4943a5028c9b3c0d0d84b29aa4b7bd8656ba84d3
Author: Miron Veryanskiy <MironVeryanskiy@gmail.com>
Date:   Fri Feb 12 18:00:43 2021 -0600

    docs: replace #file-caching with #vfs-file-caching
    
    The documentation had dead links pointing to #file-caching. They've been
    moved to point to #vfs-file-caching.

commit 60bebe4b35e6ccea4dac34ede910e47419fdd40f
Author: Romeo Kienzler <romeo.kienzler@gmail.com>
Date:   Wed Feb 17 17:11:57 2021 +0100

    docs: fix typo in crypt.md (#5037)

commit 61031cfdea01592b1761784a2355cf0387509de3
Author: edwardxml <56691903+edwardxml@users.noreply.github.com>
Date:   Tue Feb 16 22:24:11 2021 +0000

    docs: fix broken link in sftp page
    
    Just a spare line break had crept in breaking the link form.

commit da7e4379fa2e848cb49960d89ab08c463f5a0c12
Author: edwardxml <56691903+edwardxml@users.noreply.github.com>
Date:   Wed Feb 10 18:18:01 2021 +0000

    docs: fix nesting of brackets and backticks in ftp docs

commit 7e7a91ce3d459207df4f939e33a75410962c1be5
Author: Nick Craig-Wood <nick@craig-wood.com>
Date:   Mon Feb 8 12:24:44 2021 +0000

    rc: sync,copy,move: document createEmptySrcDirs parameter - fixes #4489

commit 6baa4e2947b18a3096b4107972a909ccc8258f93
Author: Ivan Andreev <ivandeex@gmail.com>
Date:   Thu Mar 4 14:26:48 2021 +0300

    address stringent ineffectual assignment check in golangci-lint (#5093)

commit 3f53283ebf216d741bd99e1be0aa09ceb73d0c47
Author: Nick Craig-Wood <nick@craig-wood.com>
Date:   Fri Mar 5 11:04:57 2021 +0000

    s3: fix Wasabi HEAD requests returning stale data by using only 1 transport
    
    In this commit
    
    fc5b14b62046b240 s3: Added `--s3-disable-http2` to disable http/2
    
    We created our own transport so we could disable http/2. However the
    added function is called twice meaning that we create two HTTP
    transports. This didn't happen with the original code because the
    default transport is cached by fshttp.
    
    Rclone normally does a PUT followed by a HEAD request to check an
    upload has been successful.
    
    With the two transports, the PUT and the HEAD were being done on
    different HTTP transports. This means that it wasn't re-using the same
    HTTP connection, so the HEAD request showed the previous object value.
    This caused rclone to declare the upload was corrupted, delete the
    object and try again.
    
    This patch makes sure we only create one transport and use it for both
    PUT and HEAD requests which fixes the problem with Wasabi.
    
    See: https://forum.rclone.org/t/each-time-rclone-is-run-1-3-fails-2-3-succeeds/22545

commit da9dd543e4b75aa9019f15dc0cc44bd4b06496ae
Author: Nick Craig-Wood <nick@craig-wood.com>
Date:   Mon Feb 8 13:22:12 2021 +0000

    s3: fix failed to create file system with folder level permissions policy
    
    Before this change, if folder level access permissions policy was in
    use, with trailing `/` marking the folders then rclone would HEAD the
    path without a trailing `/` to work out if it was a file or a folder.
    This returned a permission denied error, which rclone returned to the
    user.
    
        Failed to create file system for "s3:bucket/path/": Forbidden: Forbidden
            status code: 403, request id: XXXX, host id:
    
    Previous to this change
    
    53aa03cc44b2a425 s3: complete sse-c implementation
    
    rclone would assume any errors when HEAD-ing the object implied it
    didn't exist and this test would not fail.
    
    This change reverts the functionality of the test to work as it did
    before, meaning any errors on HEAD will make rclone assume the object
    does not exist and the path is referring to a directory.
    
    Fixes #4990

commit e3cf4f82eb30529a5be6fa5a0f9d9683df856993
Author: Ivan Andreev <ivandeex@gmail.com>
Date:   Wed Feb 17 00:37:30 2021 +0000

    build: replace go 1.16-rc1 by 1.16.x (#5036)

commit 406e26c7b79c6c71c97fdee0aa66848fda0d0ae8
Author: buengese <buengese@protonmail.com>
Date:   Mon Feb 22 20:54:27 2021 +0100

    zoho: fix custom client id's

commit f4214882abbb5a9a309c68b918c0191e453e05f8
Author: Nick Craig-Wood <nick@craig-wood.com>
Date:   Sun Feb 21 12:56:19 2021 +0000

    cmount: fix mount dropping on macOS by setting --daemon-timeout 10m
    
    Previously rclone set --daemon-timeout to 15m by default. However
    osxfuse seems to be ignoring that value since it is above the maximum
    value of 10m. This is conjecture since the source of osxfuse is no
    longer available.
    
    Setting the value to 10m seems to resolve the problem.
    
    See: https://forum.rclone.org/t/rclone-mount-frequently-drops-when-using-plex/22352

commit 231ab31d2a34f3a1adf0ee8af9e378fa6c1dfaef
Author: Nick Craig-Wood <nick@craig-wood.com>
Date:   Tue Feb 16 16:05:27 2021 +0000

    union: fix mkdir at root with remote:/
    
    Before the this fix if you specified remote:/ then the union backend
    would fail to notice the root directory existed.
    
    This was fixed by stripping the trailing / from the root.
    
    See: https://forum.rclone.org/t/upgraded-from-1-45-to-1-54-now-cant-create-new-directory-within-union-mount/22284/

commit f76bc86cc887b050595a39135e8f1fb52de36d62
Author: Nick Craig-Wood <nick@craig-wood.com>
Date:   Fri Feb 12 21:15:23 2021 +0000

    accounting: fix --bwlimit when up or down is off - fixes #5019
    
    Before this change the core bandwidth limit was limited to upload or
    download value if the other value was off.
    
    This fix only applies a core bandwidth limit when both values are set.

commit 2d11f5672db4cc3f3fe2ed0bbafce069042db9a0
Author: Nick Craig-Wood <nick@craig-wood.com>
Date:   Thu Feb 11 16:29:52 2021 +0000

    dropbox: add scopes to oauth request and optionally "members.read"
    
    This change adds the scopes rclone wants during the oauth request.
    Previously rclone left these blank to get a default set.
    
    This allows rclone to add the "members.read" scope which is necessary
    for "impersonate" to work, but only when it is in use as it require
    authorisation from a Team Admin.
    
    See: https://forum.rclone.org/t/dropbox-no-members-read/22223/3

commit cf0563f99e55616d7d76a892108547ab33b621fa
Author: Nick Craig-Wood <nick@craig-wood.com>
Date:   Tue Feb 9 09:58:44 2021 +0000

    b2: fix failed to create file system with application key limited to a prefix
    
    Before this change, if an application key limited to a prefix was in
    use, with trailing `/` marking the folders then rclone would HEAD the
    path without a trailing `/` to work out if it was a file or a folder.
    This returned a permission denied error, which rclone returned to the
    user.
    
        Failed to create file system for "b2:bucket/path/":
            failed to HEAD for download: Unknown 401  (401 unknown)
    
    This change assumes any errors on HEAD will make rclone assume the
    object does not exist and the path is referring to a directory.
    
    See: https://forum.rclone.org/t/b2-error-on-application-key-limited-to-a-prefix/22159/

commit 65f691f4de2f5ad3705b85ba5f908cb70e4dc299
Author: Nick Craig-Wood <nick@craig-wood.com>
Date:   Sun Feb 7 11:38:17 2021 +0000

    drive: refer to Shared Drives instead of Team Drives

commit f627d42a51eb1297131c728c809ec6d3894e2034
Author: Nick Craig-Wood <nick@craig-wood.com>
Date:   Tue Feb 2 17:46:10 2021 +0000

    lsjson: fix unterminated JSON in the presence of errors
    
    See: https://forum.rclone.org/t/rclone-lsjson-invalid-json-produced-no-at-the-end/22046

commit f08e43fb770843c322882837581618cc16b512a3
Author: Nick Craig-Wood <nick@craig-wood.com>
Date:   Sun Aug 2 11:13:29 2020 +0100

    b2: automatically raise upload cutoff to avoid spurious error
    
    Before this change, if --b2-chunk-size was raised above 200M then this
    error would be produced:
    
        b2: upload cutoff: 200M is less than chunk size 1G
    
    This change automatically reaises --b2-upload-cutoff to be the value
    of --b2-chunk-size if it is below it, which stops this error being
    generated.
    
    Fixes #4475

commit cd7611e7ce9d6fadbbaf77efe6c28b838685ad38
Author: Nick Craig-Wood <nick@craig-wood.com>
Date:   Wed Feb 3 16:18:29 2021 +0000

    s3: add --s3-no-head to reducing costs docs - Fixes #2163

commit 42f28f9458695b2295f03c97e78e712c3181e7a1
Author: Nick Craig-Wood <nick@craig-wood.com>
Date:   Wed Feb 3 14:44:40 2021 +0000

    build: update GitHub release tool to use gh and put a link to changelog
    
    Fixes #4994

commit 92046b457fcd33a683245400d8d90b35075946a5
Author: Alex JOST <25005220+dimejo@users.noreply.github.com>
Date:   Tue Feb 2 18:26:41 2021 +0100

    docs: Changelog: Correct link to digitalis.io

commit 098de1cff5a52d3471f910de24792ff01ca8e18b
Author: Nick Craig-Wood <nick@craig-wood.com>
Date:   Wed Feb 10 15:23:43 2021 +0000

    Start v1.54.1-DEV development
