commit 4851f1796c10c4d21be6fe890569b42230ee4e42
Author: Nick Craig-Wood <nick@craig-wood.com>
Date:   Tue Dec 9 16:35:07 2025 +0000

    log: fix backtrace not going to the --log-file #9014
    
    Before the log re-organisation in:
    
    8d353039a694fb27 log: add log rotation to --log-file
    
    rclone would write any backtraces to the --log-file which was very
    convenient for users.
    
    This got accidentally disabled due to a typo which meant backtraces
    started going to stderr even if --log-file was supplied.
    
    This fixes the problem.

commit 4ff8899b2c0b16c8753a27f8d9d124794dfd1124
Author: Nick Craig-Wood <nick@craig-wood.com>
Date:   Tue Dec 9 16:14:26 2025 +0000

    build: fix lint warning after linter upgrade

commit 8f29a0b0a1b967e71ac4c140256b67535ad6a8fd
Author: Nick Craig-Wood <nick@craig-wood.com>
Date:   Tue Dec 9 16:15:07 2025 +0000

    Add Jonas Tingeborn to contributors

commit 8b0e76e53b91de5cacf67cca4385e02666cd517f
Author: Nick Craig-Wood <nick@craig-wood.com>
Date:   Tue Dec 9 16:15:07 2025 +0000

    Add Tingsong Xu to contributors

commit 233fef5c4de64b1902df4ae23c60e9f01bd55dce
Author: Jonas Tingeborn <134889+jojje@users.noreply.github.com>
Date:   Sat Dec 6 07:31:20 2025 +0100

    configfile: add piped config support - fixes #9012

commit b9586c3e0392ec67e0f7ccc30ec8e1a6ddc7ba6f
Author: Tingsong Xu <tingsong.xu@rightcapital.com>
Date:   Mon Dec 8 14:05:19 2025 +0800

    fs/log: fix PID not included in JSON log output
    
      When using `--log-format pid,json`, the PID was not being added to the JSON log output. This fix adds PID support to JSON logging.

commit 0dc0ab13302515ede4e54d97b8a9d117d05df5f1
Author: Nick Craig-Wood <nick@craig-wood.com>
Date:   Mon Dec 8 14:43:49 2025 +0000

    build: adjust lint rules to exclude new errors from linter update

commit a6bbdb35a0a2bd5c4b4b43253b3cc98ad029b752
Author: Nick Craig-Wood <nick@craig-wood.com>
Date:   Mon Dec 8 12:32:04 2025 +0000

    proxy: fix error handling in tests spotted by the linter

commit b33cb77b6cddb22aa8ee1c3a9053c9dff2401329
Author: Nick Craig-Wood <nick@craig-wood.com>
Date:   Mon Dec 8 14:44:40 2025 +0000

    Add Johannes Rothe to contributors

commit d51322bb5fa117954d5675f69e3e41f642be88ac
Author: Nick Craig-Wood <nick@craig-wood.com>
Date:   Mon Dec 8 14:44:40 2025 +0000

    Add Leo to contributors

commit e718ab60914b60e64ff7d832fd9384c13d991ba3
Author: Nick Craig-Wood <nick@craig-wood.com>
Date:   Mon Dec 8 14:44:40 2025 +0000

    Add Vladislav Tropnikov to contributors

commit 0a9e6e130fb8204faadec1f5b907478fb7d4ea3d
Author: Nick Craig-Wood <nick@craig-wood.com>
Date:   Mon Dec 8 14:44:40 2025 +0000

    Add Cliff Frey to contributors

commit 3358b9049c216f489bf160aeecaa18d5af651efb
Author: Nick Craig-Wood <nick@craig-wood.com>
Date:   Mon Dec 8 14:44:40 2025 +0000

    Add vicerace to contributors

commit 847734d421d219f1b12b144fcb0d08a6556e1485
Author: DianaNites <5275194+DianaNites@users.noreply.github.com>
Date:   Tue Dec 2 15:13:00 2025 -0600

    b2: Fix listing root buckets with unrestricted API key
    
    Fixes previous pull request #8978
    
    An oversight meant that unrestricted API keys
    never called b2_list_buckets,
    meaning the root remote could not be listed.
    
    The call is now made in the event there are no allowed buckets,
    indicating an unrestricted API key
    
    Fixes #9007

commit f7b255d4ec760e4d1fe28fe2f064bb02261207b4
Author: Johannes Rothe <mail@johannes-rothe.de>
Date:   Thu Nov 27 22:07:26 2025 +0100

    googlecloudstorage: improve endpoint parameter docs
    
    When specifying a custom endpoint with a subpath, there is a limitation
    in the Google cloud storage integration that the subpath is ignored
    during upload operations. For example with the custom endpoint
    "example.org/custom/endpoint" on upload the /custom/endpoint is not
    reflected.
    
    As this is most likely an issue with the underlying API client, there is
    no way to fix this in rclone. By extending the documentation at least
    rclone users are made aware of this limitation.
    
    Related forum thread: https://forum.rclone.org/t/googlecloudstorage-custom-endpoint-subpath-removed-for-upload/53059

commit 24c752ed9e48d3d409f4a380f1bda536deef962b
Author: Leo <i@hardrain980.com>
Date:   Mon Dec 1 11:17:10 2025 +0800

    serve webdav: implement download-directory-as-zip
    
    Signed-off-by: Leo <i@hardrain980.com>

commit a99d155fd4e091504ded67a36ea3111b0e765f5d
Author: Vladislav Tropnikov <vtr.name@gmail.com>
Date:   Sat Nov 29 14:53:00 2025 +0100

    s3: The ability to specify an IAM role for cross-account interaction

commit f72b32b4709bffef392f7bf5e22f4bfb9910e9f6
Author: Cliff Frey <cliff@openai.com>
Date:   Thu Nov 27 08:58:07 2025 -0800

    azureblob: add metadata and tags support across upload and copy paths
    
    This change adds first-class metadata support to the Azure Blob backend,
    including headers, user metadata, tags, and modtime overrides, and wires
    it through uploads and server-side copies.
    
    There is a behavior change in that rclone will now set the "mtime"
    custom metadata when doing server side copies to azure and the
    `--metadata` argument is given.
    
    - Map standard headers: cache-control, content-disposition, content-encoding,
      content-language, content-type to corresponding x-ms-blob-* HTTP headers.
    - Map user metadata: any non-reserved keys (excluding x-ms-*) are sent as
      blob user metadata. Keys are normalized to lowercase for consistency.
    - Support tags: parse `x-ms-tags` as a comma-separated list of key=value
      pairs and apply them on uploads and copies.
    - Support mtime override: accept `mtime` in metadata (RFC3339/RFC3339Nano)
      to override the stored modtime persisted in user metadata.

commit 9be7f99bf8287084a91b8a6e3fd554f23e2c1658
Author: vicerace <vicerace@sohu.com>
Date:   Tue Nov 25 18:26:16 2025 +0800

    refactor: use strings.Cut to simplify code
    
    Signed-off-by: vicerace <vicerace@sohu.com>

commit 6858bf242ef3daef7d19d5b09bf41f6f44ddf455
Author: Nick Craig-Wood <nick@craig-wood.com>
Date:   Wed Nov 26 12:18:38 2025 +0000

    docs: note where a provider has an S3 compatible alternative

commit e8c6867e4c2b3ddf64e98c4fa48a619957471bdf
Author: Nick Craig-Wood <nick@craig-wood.com>
Date:   Wed Nov 26 12:00:00 2025 +0000

    Add Shade as sponsor

commit 50fbd6b04915e11fd9a05aebc9e1e7f942c110f2
Author: Nick Craig-Wood <nick@craig-wood.com>
Date:   Wed Nov 26 12:22:29 2025 +0000

    Add Duncan Smart to contributors

commit 0783cab952454dc10f9ebf3428fff9ceae8712c9
Author: Nick Craig-Wood <nick@craig-wood.com>
Date:   Wed Nov 26 12:22:29 2025 +0000

    Add Diana to contributors

commit 886ac7af1d1ca83bd1425a64f8b5e17b43037f54
Author: Duncan Smart <duncan.smart@gmail.com>
Date:   Sun Nov 23 15:08:40 2025 +0000

    docs: Clarify OAuth scopes for readonly Google Drive access

commit 3c40238f020d47ffb6f2f2dac24343048d1d1226
Author: Diana <5275194+DianaNites@users.noreply.github.com>
Date:   Mon Nov 24 09:46:41 2025 -0600

    b2: support authentication with new bucket restricted application keys
    
    Backblaze has updated its b2_authorize_account API endpoint, newly created
    application keys are now "multi-bucket" keys, capable of being limited to
    multiple buckets. These keys can only be used with the v4 endpoint, not v1 which
    returns an HTTP 400.
    
    This commit switches authorization to the v4 endpoint, and allowing such keys to
    work with any of the allowed buckets.
    
    With multi-bucket keys, missing restricted buckets can be non-fatal.
    
    Supports listing root with multi-bucket API keys

commit 46ca0dd7fe62ef2524d0f81238d99f492bcc2840
Author: Nick Craig-Wood <nick@craig-wood.com>
Date:   Sun Nov 23 11:30:29 2025 +0000

    docs: update sponsor logos

commit 2e968e7ce00927b52b2a2349dc9d6b6a80efb4d2
Author: Nick Craig-Wood <nick@craig-wood.com>
Date:   Fri Nov 21 18:23:16 2025 +0000

    docs: fix lint error in changelog

commit 1886c552db8d5c530936e9d6ae97d872d0662e52
Author: Nick Craig-Wood <nick@craig-wood.com>
Date:   Fri Nov 21 18:23:07 2025 +0000

    Start v1.73.0-DEV development
