Skip to content

Releases: lucheeseng827/mergestro-gate

v1

v1

Choose a tag to compare

@github-actions github-actions released this 26 Sep 13:44
sync: mirror from monorepo @ 6132c05e5 (mergestro-gate-oss-v0.6.0)

v0.6.1

Choose a tag to compare

@github-actions github-actions released this 26 Sep 14:24
sync: mirror from monorepo @ 04aa0a125 (mergestro-gate-oss-v0.6.1)

v0.6.0

Choose a tag to compare

@lucheeseng827 lucheeseng827 released this 26 Sep 11:32

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

v0.5.0

Choose a tag to compare

@github-actions github-actions released this 07 Jul 19:24
sync: mirror from monorepo @ 0df98676 (mergestro-gate-oss-v0.5.0)

Mergestro Gate

Choose a tag to compare

@lucheeseng827 lucheeseng827 released this 24 Jun 12:25

Mergestro Gate v0.1.1 — first public release

A behavioral merge gate for AI-generated code. It mutation-tests the changed
lines in a PR: any mutant that survives is a line your tests don't really check.
Plus static slop / security / convention lanes over the same diff. One verdict,
gate-able in CI.

Use it

- uses: lucheeseng827/mergestro-gate@v1
  with:
    advisory: "true"   # comment-only first; flip off to block
    comment: "true"

Full inputs, the advisory→blocking rollout, and tuning are in ACTION.md.

What's in this release

  • Behavioral mutation gate (Rust, via cargo-mutants) — stable. Python / JS /
    Go / JVM engines included as experimental advisory PoCs.
  • Pattern lanes — slop (AST signatures), security (anti-pattern rules),
    convention (hallucinated-import).
  • Gating — --max-survivors, --block-on-severity, --block-on-zero-assertion,
    --block-on-debt, --block-on-pattern; advisory mode for rollout.
  • Telemetry — per-run JSON-Lines + analyze trends (off by default).
  • Idempotent PR comment; prebuilt static musl binary + sha256.

Install

  • GitHub Actions: lucheeseng827/mergestro-gate@v1
  • Docker (non-GH CI / local): mancube/mergestro-gate:0.1.0
  • crates.io: coming

Apache-2.0.


Two things to know:

  • Marketplace publishing requires the repo public + a release with the "Publish to Marketplace" box checked. So flip the OSS repo public first.
  • After flipping public, re-point the v1 tag (it'll need a fresh release attached for the Marketplace flow, or publish from v0.1.0).

Full Changelog: v0.1.0...v1