Skip to content

v0.2.0 — Auto Push & CI verify gate

Choose a tag to compare

View all tags
@Plumvery Plumvery released this 21 Jul 14:46
· 13 commits to main since this release
v0.2.0
0ecb650

Automatic uploads and a CI safety net: the "forgot to push the blobs" failure mode is now caught on both ends.

✨ What's new

🔄 Auto Push

When tracked files have local changes that were never uploaded, UniLFS detects it — on focus changes, and in Automatic mode right after the asset is saved/imported — and asks or uploads in the background. Blobs are already in storage by the time you commit the manifest. Configure via Project Settings > UniLFS > Auto Push (Ask by default / Automatic / Off).

🤖 CI verify gate (no Unity needed)

  • Documentation~/ci/verify_manifest.py — Python-stdlib-only script that fails CI when a committed manifest references blobs missing from storage. Works for both S3-compatible and Google Drive providers; also usable as a client-side pre-push hook. No Unity license required.
  • UniLFS.Editor.UniLfsCli.Verify — the same gate as a Unity batch-mode entry point.

See Documentation~/ci.md for GitHub Actions examples and why uploads themselves must happen client-side.

📦 Install / upgrade

https://github.com/Plumvery/UniLFS.git#v0.2.0

Full changelog: v0.1.0...v0.2.0

Assets 2
Loading