Skip to content

Releases: edycutjong/overrule

v1.0.2

Choose a tag to compare

@github-actions github-actions released this 17 Aug 19:06
941d17f

1.0.2 (2026-08-17)

Bug Fixes

  • ci: empty release-please package-name so the release actually gets tagged (6ac87c2)
  • ci: pin release-please to an empty component so releases actually cut (66b7f11)

v1.0.1

Choose a tag to compare

@github-actions github-actions released this 17 Aug 18:45
0d16f9c

1.0.1 (2026-08-17)

Bug Fixes

  • ci: drop the duplicated scope from dependabot commit prefixes (276c7df)
  • ci: stop interpolating the release-please PR blob into the shell (9bd890b)

Build System

  • deps: slow dependabot to monthly, grouped, no major bumps (b4fb217)

CI/CD

  • deploy: ship the /verify dashboard to Vercel production on main (7d5c939)
  • release: automate versioning with release-please (fe0b7f4)
  • release: retry release-please once when the GitHub API 5xxs (ebdc9c7)
  • security: scan the full git history for secrets with gitleaks (7ab9a5a)

v1.0.0 — Overrule offline core

Choose a tag to compare

@edycutjong edycutjong released this 17 Aug 18:20

Initial public release: the offline Overrule core as submitted to the XPRIZE hackathon.

Features

  • appeals pipeline — case state machine, mandate middleware, docket engine, redaction, agent pipeline
  • signed, hash-chained decision ledger with an independently re-verifiable export
  • /verify judge dashboard rendering the real outputs of the offline pipeline — https://overrule.edycu.dev
  • deterministic seed fixtures + a 22-invariant end-to-end self-test

Quality

  • 121 vitest tests, tsc --noEmit strict, offline and deterministic (no API key, no network)
  • multi-stage CI, CodeQL SAST, full-history secret scanning

This tag is the version anchor for release-please: every subsequent release is computed automatically from Conventional Commits.