Skip to content

Releases

v0.9.0

Choose a tag to compare

@sriinnu sriinnu released this 13 Nov 21:09
v0.9.0
95e8b60

What's Changed

  • Gate: --range with base-branch settings, one verdict, versioned JSON; omit-gate CI job by @sriinnu in #26
  • README: restructure and correct; omit-gate on pull_request_target by @sriinnu in #27
  • Logo: the deleted line by @sriinnu in #28
  • Release v0.9.0 — version bump by @sriinnu in #29

Full Changelog: v0.8.0...v0.9.0

v0.8.0

Choose a tag to compare

@sriinnu sriinnu released this 12 Nov 21:17
v0.8.0
70d7794

What's Changed

  • release: find the publish run without --branch by @sriinnu in #21
  • Sign the tap commit and create the release without gh 2.5 flags by @sriinnu in #22
  • Stage npm releases; maintainer approves with 2FA by @sriinnu in #23
  • Gate: safety always, editorial opt-in; lint the index; trust-key sentinel by @sriinnu in #24
  • Release v0.8.0 — version bump by @sriinnu in #25

Full Changelog: v0.7.0...v0.8.0

v0.7.0

Choose a tag to compare

@sriinnu sriinnu released this 21 Oct 09:22
v0.7.0
46fe58c

What's Changed

  • Add TLS-bypass gate, tamper sentinel and enforced modes; harden guards by @sriinnu in #19
  • Release v0.7.0 — version bump by @sriinnu in #20

Full Changelog: v0.6.0...v0.7.0

v0.6.0

Choose a tag to compare

@sriinnu sriinnu released this 06 Oct 15:53
v0.6.0
00f6df5

What's Changed

  • Publish through npm trusted publishing, with no stored token by @sriinnu in #15
  • Add omit hook install ribhu by @sriinnu in #16
  • Cover Codex patches, add omit doctor and an opt-in context guard by @sriinnu in #17
  • Release v0.6.0 — version bump by @sriinnu in #18

Full Changelog: v0.5.0...v0.6.0

v0.5.0

Choose a tag to compare

@sriinnu sriinnu released this 06 Oct 15:04
v0.5.0
84df812

What's Changed

  • Add release tooling: npm + GitHub + Homebrew in one command by @sriinnu in #4
  • Release v0.4.1 — version bump by @sriinnu in #5
  • Fix skill frontmatter YAML so skill indexers can see omit by @sriinnu in #6
  • Release through PRs: main and the Homebrew tap both reject direct pushes by @sriinnu in #7
  • Pin the Action to a release in the README, and run it on omit's own PRs by @sriinnu in #8
  • Give GETTING-STARTED the same Action snippet as the README by @sriinnu in #9
  • Add omit codemode: sandboxed scripts over read-only repo tools by @sriinnu in #10
  • Add omit codemode run and a skill, so codemode needs no MCP server by @sriinnu in #11
  • Bundle the sandbox in the Homebrew formula, and keep versions in step by @sriinnu in #12
  • Move the Action pins with each release, and lower the sandbox floor by @sriinnu in #13
  • Release v0.5.0: version bump, and a release script that can wait and resume by @sriinnu in #14

Full Changelog: v0.4.0...v0.5.0

v0.4.1

Choose a tag to compare

@sriinnu sriinnu released this 23 Sep 19:09
v0.4.1
e01be77

What's Changed

  • Add release tooling: npm + GitHub + Homebrew in one command by @sriinnu in #4

Full Changelog: v0.4.0...v0.4.1

omit v0.4.0 — fail-closed enforcement, and receipts that are checked

Choose a tag to compare

@sriinnu sriinnu released this 18 Sep 21:33
v0.4.0
34302e0

A four-lens security review of the previous work produced 34 findings, 30 of them confirmed by execution. A fifth pass re-verified each one independently and dropped 2 whose stated impact did not survive checking. This release is the fix.

The architectural finding

Roughly half the confirmed items were one bug in different clothes: errors degraded to let it through instead of refuse.

  • git() returned null on every failure and every call site coalesced it to '', so "git could not answer" and "there is nothing here" were the same value. A diff past Node's 1 MiB buffer threw ENOBUFS, was swallowed, and the gate reported hazards: 0 ✅ with a healthy-looking line count while nothing had been scanned.
  • A hook that threw exited 1 — which the harness reads as a non-blocking error — so an objection became a stack trace the model moved past. A receipt citing a directory was enough to make the new-dependency objection vanish.
  • A committed symlink to /dev/zero hung git commit, the hooks and CI forever.

Every sentinel now fails closed, and "could not determine" is never rendered as an empty result.

Receipts are checked, not recorded

The gate validated receipts.includes(dep) — a substring match against a file the agent writes itself. Evidence is now bound to the claim it supports:

  • run must name what it exercises. Exit status alone proves nothing: ["true"] exits 0 and ["false"] exits 1 while testing neither the standard library nor anything else.
  • A tried entry cites a search, not a location. It names the symbol it looked for and omit searches the tree — tracked and untracked — for itself, so a symbol that is there refutes the author's own conclusion.

Also

  • Secrets are genuinely non-suppressible: the secret rules now run before any marker is consulted. The README claimed this; the code did not do it.
  • omit-allow: requires a trailing comment carrying a real reason. Bare, reason-less, or inside a string literal, it is ignored.
  • Dependency parsing covers BOMs, Cargo [workspace.dependencies], and four more manifest formats; the TOML array reader is linear (1,241 ms → 8 ms on 40k lines).
  • A >1 MiB diff, a rename brace path, a -diff git attribute, and a subdirectory working directory can no longer hide a change.
  • action.yml was invalid YAML at the previous release — an unquoted ": " in the description — so the Action may never have loaded.
  • SKILL.md now asks for a Final Draft the stop gate can actually parse; it previously asked for content in a shape the gate rejected, so honest reports were refused.

Breaking

Receipts written before 0.4.0 read as unverifiable rather than being silently accepted. omit verify names each one individually.

Verification

178 tests, from 54. Every original reproduction re-run end to end after the final changes. Fixes proven by mutation testing — un-doing one fix at a time to confirm its test actually bites. test/docs.test.mjs pins the rule files to the checker, so every documented receipt example must verify against a real fixture.