v0.12.3

[0.12.3] - 2026-08-11

Added

• Add AtomicityOptions and AtomicityMode (AUTO, COMMIT_FILE,
  ATOMIC_RENAME) to configure the checkpoint save atomicity protocol in
  both v0 and v1.
• Write commit_success.txt on all newly finalized checkpoints across all
  storage backends, enabling cross-backend reading compatibility.
• Add allow_legacy_atomic_rename option to AtomicityOptions to opt into
  legacy fallback validation when reading legacy AtomicRename checkpoints
  missing commit_success.txt.
• Add multi_tier_checkpointing_backup_interval_steps parameter

Changed

• Deprecate temporary_path_class in CheckpointManagerOptions in favor of
  atomicity_options with AtomicityMode.

[0.12.2] - 2026-07-30

Added

• Reduce Memory Pressure from long held CPU buffers in Pathways MTC
• Support explicit devices for Pathways MTC init
• Avoid stale Pathways MTC worker dummy handles

Changed

• #v1 Drive the safetensors load by the target sharding: each process reads
  only the byte ranges its own devices need (coalesced under
  SafetensorsOptions.max_over_read_ratio, picked per file from the planned
  reads by default, fetched as concurrent ranged reads of
  SafetensorsOptions.read_chunk_bytes each, bounded by
  MemoryOptions.read_concurrent_bytes), replacing the transient-array
  resharding load. Supports arbitrary shardings, including inner-dimension
  partitions; a warning reports shardings whose fragmented byte layout forces
  heavy over-read.