Skip to content

🚀 Release 0.65.0 (leafcutter ant)

Choose a tag to compare

@github-actions github-actions released this 23 Oct 20:32
· 247 commits to main since this release
leafcutter-ant-2.mp4

The video above was generated with Oxen.ai.

Leafcutter ant: A tropical ant that cuts pieces of leaf and carries them home like green sails, where its colony grows the fungus garden it feeds on.

Breaking changes

  • oxen rm refuses to delete work that exists nowhere else, as git rm does: a file whose staged edit has not been committed, a file added under a directory given with -r since the last commit, and an edited file whose committed content is missing locally. Pass the new -f (force=True on Python's Repo.rm) to remove them anyway. -f also overrides the existing refusal of a file with unsaved edits. Scripts that relied on oxen rm deleting such files need -f. #1105
  • oxen rm --staged refuses when the staged content matches neither the file on disk nor the last commit, since that content has no other copy. #1105
  • oxen rm --staged with a glob whose every match already has its removal staged fails with an error pointing at oxen restore --staged, rather than exiting 0 having done nothing. #1101

New features

  • Workspaces move and remove whole directories in one request. A move takes every file under the directory along with its subfolders and data frame edits, and either all of it moves or none of it does. Removing a directory also drops files staged only in the workspace under it, so committing no longer re-creates the deleted folder. #1094

Bug fixes

  • In a workspace, moving or renaming a file or data frame whose removal was staged brought the deleted content back at the new path. It now returns a 409. #1094
  • Renaming a data frame in a workspace onto a path where the workspace had staged another file replaced that file, losing its rows and edits without an error. Moving anything to a path beneath a file staged a directory over that file. Both now return a 409. #1094
  • Renaming a data frame that had not been opened in the workspace failed. #1094
  • Deleting every row of a .json data frame in a workspace and committing left a file with no columns that could not take rows again. That commit is now refused, as it already was for .jsonl. #1109
  • Audio added to a workspace, through oxen workspace add, the web UI, or the API, was committed without its duration, channel count, and sample rate, which oxen add records. Both routes now record the same metadata. #1100
  • oxen merge and oxen pull run from a subdirectory of a repository refused with "your local changes to the following files would be overwritten" for files that already matched the merge. #1104
  • After oxen add staged the removal of a deleted directory, oxen status kept listing files that had been staged under it as new files. #1097

Performance

  • Adding files to a workspace stores the uploaded copy directly instead of writing each file twice: adding 100 small files went from 865 ms to 771 ms (11% faster), and adding one 128 MiB file from 146 ms to 104 ms (29% faster). #1096
  • The server runs the repository work of directory zip downloads, merges, and imports off its request worker threads, so a slow one no longer holds up other requests on the same worker. #1092 #1098 #1107

Security

  • The oxen CLI, the Python package, and oxen-server distrust the compromised eMudhra intermediate CAs, and the server's Docker image requires the Debian ca-certificates update that distrusts them. #1110

Internal improvements

  • Rust 1.99.1, DuckDB 1.10506.1, and tempfile in place of async-tempfile. #1099 #1109 #1095
  • File types and metadata are read from a file's bytes through one function that opens each file once, with every file's metadata and hash unchanged. #1103 #1106
  • Test suite, CI, and documentation improvements. #1087 #1091 #1093 #1102 #1108 #1111

Binaries are available for the following platforms:

  • Docker arm64
  • Docker x86_64
  • Linux arm64
  • Linux x86_64
  • MacOS arm64 (Apple Silicon)
  • MacOS x86_64 (Intel)
  • Windows x86_64

🐧 Linux Binaries
The Linux binaries require a minimum glibc version of 2.34.

These are the minimum versions of common distributions with glibc 2.34 or later.

Distribution First version with glibc 2.34+
Amazon Linux 2023
Arch 2021
CentOS Stream 9
Debian 12
Fedora 35
RHEL 9.0
Ubuntu 22.04

The -rhel8 tarballs and wheels are for RHEL 8 and its rebuilds, which have glibc
2.28. No distribution in the table above needs them.

🖥️ Windows Binaries
The Windows binaries require a minimum version of Visual C++ 2022.
You may need to install the latest Microsoft Visual C++ Redistributable.

🍏 MacOS Binaries
The MacOS arm64 (Apple Silicon) binaries require a minimum version of MacOS 11 Big Sur.
The MacOS x86_64 (Intel) binaries require a minimum version of MacOS 10.13 High Sierra.

🐍 Python Wheels
The Python wheels are abi3 wheels built against Python 3.11 and compatible with
Python 3.11+. They are available for the following platforms:

  • Linux arm64
  • Linux x86_64
  • MacOS arm64 [Apple Silicon]
  • MacOS x86_64 [Intel]
  • Windows x86_64