Skip to content

onedrive client version 2.4.11
Compare
Choose a tag to compare
@abraunegg abraunegg released this 06 Apr 21:08
· 412 commits to master since this release
v2.4.11
6c64bec
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Release Overview:

  • Fix support for '/*' regardless of location within sync_list file (#1293)
  • Fix 429 response handling correctly check for 'retry-after' response header and use set value (#1305)
  • Fix 'sync_list' path handling for sub item matching, so that items in parent are not implicitly matched when there is no wildcard present (#1317)
  • Removed the depreciated config option 'force_http_11' which was flagged as depreciated by PR #549 in v2.3.6 (June 2019) (#1323)
  • Fix --get-O365-drive-id to use 'nextLink' value if present when searching for specific SharePoint site names (#1329)
  • Updated error output of --get-O365-drive-id to provide more details why an error occurred if a SharePoint site lacks the details we need to perform the match (#1329)
  • Updated Docker build files for Raspberry Pi to dedicated armhf & aarch64 Dockerfiles (#1335)
  • Added support in --get-O365-drive-id to provide the 'drive_id' for multiple 'document libraries' within a single Shared Library Site (#1350)
  • Fix OneDrive Business Shared Folder existing name conflict check (#1351)
  • Fix uploading documents to Shared Business Folders when the shared folder exists on a SharePoint site due to Microsoft Sharepoint 'enrichment' of files (#1352)
  • Fix incorrect error message 'Item cannot be deleted from OneDrive because it was not found in the local database' when item is actually present (#1354)
  • Updated logging output when in --monitor mode, avoid outputting misleading logging when the new or modified item is a file, not a directory (#1364)
  • Fix application crash when unable to rename folder structure due to unhandled file-system issue (#1366)
  • Fix that a file record is kept in database when using --no-remote-delete & --remove-source-files (#1383)
  • Updated documentation (various)

Known Issues:

Outstanding Issues:

Assets 2
Loading