Repository navigation
v0.2.1
What's Changed
S3 Structured Log Paths + Gzip Compression
- Structured S3 keys: Logs are now stored at
{prefix}{workspace}/{task}/YYYY/MM/DD/YYYY-MM-DDTHH-MM-SS_{job_id}.jsonl.gzinstead of flat{prefix}{job_id}.jsonl, making S3 browsing and debugging much easier - Gzip compression: Log files are compressed on upload and decompressed on read, reducing storage costs
- Server events preserved: S3 upload now happens after hooks fire, so hook failures and orchestration errors are included in the archived logs
- No DB column for S3 key: The key is reconstructed from job metadata (
JobLogMetastruct) to stay storage-agnostic for future GCP/Azure support
Breaking Changes
- No backward compatibility with old flat S3 key format — this is a clean break
upload_to_s3(),get_log(), andget_step_log()now require a&JobLogMetaparameter
Full Changelog: v0.2.0...v0.2.1
Full Changelog: v0.2.0...v0.2.1