Skip to content

v0.1.220

Choose a tag to compare

@github-actions github-actions released this 09 Sep 17:13
· 1534 commits to main since this release
8a2d1f0

Alpha

OMG is alpha software: the CLI, flags, and on-disk formats can change without a compatibility guarantee.

Breaking changes

These CLI and release changes shipped in 0.1.215 and remain in later alphas.

omg license removed

Local features are no longer license-gated. Dashboard identity is optional.

# Removed
omg license
omg license check
omg license pricing

# Use instead
omg account status
omg account link <token>
omg account unlink

Team, Enterprise, and Fleet commands no longer require a paid JWT. Scripts that expected those commands to fail without a license will now succeed locally. Remote dashboard sync still needs a valid token from omg account link.

Installation

Quick Install (Linux/macOS):

curl -fsSL https://getomg.xyz/install.sh | bash

Windows Subsystem for Linux: Use the Linux installer inside your WSL distribution.

What's New in v0.1.220

Review

  • Audit: Verify cross-filesystem migration copies file contents

🐛 Bug Fixes

  • Audit: Copy history across filesystems when atomic migration fails

prepare_system_audit_directory refused to migrate /var/log/omg when

rename(2) returned EXDEV (e.g. btrfs subvolume mounts), failing every

privileged operation until an operator intervened. Fall back to a

byte-verified copy: stage under a temp sibling, preserve ownership and

modes, fsync, verify path/size snapshot, rename into place, then remove

the source. Symlinks and special files still fail closed.

  • Install: Point bootstrap at getomg.xyz and sync installer to the release bucket

👷 CI/CD

  • Release: Verify installer sidecar and stop claiming latest-version early

The new bucket installer upload wrote a hash-only sidecar and printed

latest-version success before that marker was published. Use a standard

sha256sum sidecar, round-trip verify it, and echo installer success only

after the script itself is confirmed.

📚 Documentation

  • Record installer domain repair [skip ci]
  • Record v0.1.219 release verification [skip ci]

🔧 Maintenance

  • Checkpoint generated astra report

🧪 Testing

  • Audit: Restore elevated-path isolation skips

OMG_DATA_DIR is still ignored when running as root, so these fixtures

must not touch the real /var/lib/omg audit log in elevated CI.

Merged pull requests

This release includes every PR merged between v0.1.219 and v0.1.220:

  • #392 chore(release): prepare v0.1.220 — version bump and changelog promotion (d95e47cd)
  • #391 fix(audit): copy audit history across filesystems when atomic migration fails — EXDEV migration plus SHA-256 content-digest verification (08be0a66; commits d651f6d9, 3c31eef4, de64c751)
  • #390 fix(install): point bootstrap at getomg.xyz and sync installer to the release bucket — canonical installer domain and release-bucket installer with sha256 sidecar (1a7f492f; commits 5fd3ce04, 3066811e)
  • #388 chore: checkpoint generated astra report (d7358d89)

Direct-to-main documentation commits are also included: 2e4c05b8, 3caaf155, 3bd9192e ([skip ci]).

Performance

  • Benchmark green on the exact tagged SHA 8a2d1f00 (run 34377481911): search 18.8 ms / 12.3x vs pacman, status 9.8 ms — unchanged from the v0.1.219 baseline. The 0.1.220 changes (audit migration fallback, installer/CI) do not touch the query hot path.
  • The v0.1.219 baseline (search 18.8 ms) reflects the accepted metadata-scan cost from #372; see the v0.1.219 release notes for the regression-gate rationale.

Known limitations

  • Audit migration has not fired on every host: the EXDEV fallback first runs when a privileged operation next needs to move /var/log/omg to /var/lib/omg/audit. If /var/log and /var/lib are on the same filesystem, hosts continue to use the plain atomic rename(2) path.
  • Non-gating CI checks remain red (pre-existing, unchanged): the coverage container (elevated-path isolation), the docker-e2e test_docker_update_check flake, and QEMU arm64 guest legs on runners without /dev/kvm.
  • Dependabot: one high-severity dependency alert on main is still open.
  • omg.latham.cloud/install.sh still serves the legacy installer until the omg-web site redeploys; use https://getomg.xyz/install.sh (canonical) or https://releases.omg.latham.cloud/install.sh (release bucket).

Platform Support

Platform Architecture Binary
Arch Linux x86_64 omg-v0.1.220-x86_64-linux-arch.tar.gz
Debian x86_64 omg-v0.1.220-x86_64-linux-debian.tar.gz
Ubuntu x86_64 omg-v0.1.220-x86_64-linux-ubuntu.tar.gz
Fedora/RHEL x86_64 omg-v0.1.220-x86_64-linux-fedora.tar.gz
macOS ARM64 omg-v0.1.220-aarch64-darwin.tar.gz
WSL x86_64 Use the binary matching the installed Linux distribution

Verification

Verify the downloaded archive before extracting or installing it.

Integrity (checksum):

Linux:

sha256sum -c omg-v0.1.220-*.sha256

macOS:

shasum -a 256 -c omg-v0.1.220-*.sha256

Provenance (recommended): every release archive carries a Sigstore build
provenance attestation generated by GitHub Actions. Verify it with the GitHub
CLI:

gh attestation verify omg-v0.1.220-x86_64-linux-arch.tar.gz -R PyRo1121/omg

omg self-update and install.sh perform this check automatically whenever
the GitHub CLI is installed locally.

Manual Installation

Linux/macOS:

tar -xzf omg-v0.1.220-*.tar.gz
cd omg-v0.1.220-*
sudo cp omg /usr/local/bin/

Full Changelog: https://github.com/PyRo1121/omg/blob/main/docs/changelog.md