Skip to content

Releases

v0.2.4

Choose a tag to compare

@romerramos romerramos released this 11 Oct 16:35
a6c24da

Verdicts from the open API now have a public page, and the API returns its link.

New

  • Public verdict page: /verdicts/<token> shows the verdict for a diff sent to the API, with its probabilities and each file's verdict. It's the same design as the signed-in page, anyone with the link can open it without signing in, and it lasts until the verdict expires (30 days).
  • The API's url now links to that page instead of being null. The same diff sent again gets the same link.

Privacy

  • Kept out of sight: the page is kept out of search engines, caches and referrers. Wrong or expired links are 404s.
  • Nothing that needs an account: no asking again, no voting, no GitHub links.

Upgrade notes

None: no migrations, secrets or settings.

v0.2.3

Choose a tag to compare

@romerramos romerramos released this 11 Oct 15:40
91945f2

Verdicts for diffs sent to the open API are now saved like other verdicts, ready for a public link.

Improved

  • Saved in the database: API verdicts are kept for 30 days instead of 7 days in the cache. The same diff sent again gets its saved verdict back without asking Jev.
  • Ready for a public link: each API verdict gets a random, unguessable token, which an upcoming public page will use.
  • Kept out of the web app: API verdicts belong to no repository or user, so signed-in users never see them in lists, on verdict pages or in votes. The database enforces this too.
  • One Jev request per diff: the database now guarantees only one pending request for the same diff at a time.

Privacy

  • Stored for API verdicts: the diff's hash, title, line counts, file names and statuses, and the verdicts. They're deleted after 30 days.
  • Never stored: patches, the description, branch or repository names, accounts or IP addresses.

Upgrade notes

  • One migration, which bin/update runs. It's additive, so the previous release still works with the migrated database.
  • New hourly job (config/recurring.yml) that deletes expired API verdicts.
  • No new secrets or settings.
  • One-time re-ask: verdicts cached by v0.2.x aren't carried over, so a diff sent before gets asked once more.

v0.2.2

Choose a tag to compare

@romerramos romerramos released this 11 Oct 15:11
9a21331

bin/update is now the whole deploy for servers that run the app from a git checkout: backup, update, restart, health check and automatic rollback.

New

  • One-command deploys: with a server's own config/server.yml (copy config/server.example.yml), bin/update vX.Y.Z does all of this in order:
    • loads the app's environment
    • backs up the SQLite databases
    • checks out the release, installs gems, migrates and precompiles assets
    • restarts the app
    • waits until /up answers with the new version
  • Automatic rollback: if any step after the backup fails, it goes back to the previous release, restarts it and says where the backup is.
  • Version on /up: it now sends the running version in an X-App-Version header.

Improved

  • AGENTS.md → Deploying a release: one long-lived checkout per server, deployed only with bin/update.

Upgrade notes

  • No migrations, secrets or app settings.
  • Without config/server.yml, bin/update works as before: it updates the checkout, and you restart.
  • The first time you use the new deploy, the checkout still has the old bin/update. Run git fetch --tags && git checkout v0.2.2, then bin/update v0.2.2.

v0.2.1

Choose a tag to compare

@romerramos romerramos released this 11 Oct 14:42
456f14c

Jev my PR now has an open JSON API: send any diff, get Jev's verdict back, with no sign-in.

New

  • Open API: POST /api/verdicts takes a diff as JSON (title, description, branches and the files with their patches) and returns the verdict (human, llm or none), how sure Jev is, a verdict for each file, and whether patches were left out. It needs no sign-in, cookie or API key. The README's Open API section documents the request, the response and every error.
  • Free repeats: the same diff sent again within 7 days returns its saved verdict without asking Jev.

Improved

  • Limits for the API, per IP address: 1 call every 2 minutes and 10 new verdicts in any 24 hours.
  • The API gets a quarter of the monthly budget. Once it has spent that, it pauses until the 1st while signed-in use carries on.
  • Request bodies over 2 MB are refused before they're read.
  • Clear errors: limits and pauses return a plain JSON error with Retry-After.

Privacy

  • Patches and IP addresses aren't stored for API calls. Only the diff's hash, its file names and the verdicts are kept, in the cache for 7 days.
  • A keyed hash of each caller's IP address is kept for 2 days so the daily limit can be counted, then deleted.

Upgrade notes

  • One migration (jev_requests.source and jev_requests.ip_digest), which bin/update runs.
  • New hourly job (config/recurring.yml) that forgets IP hashes older than 2 days.
  • No new secrets or settings.
  • Behind a proxy: make sure the real client IP reaches Rails (X-Forwarded-For from a trusted proxy). Otherwise every API caller shares one limit.

v0.2.0

Choose a tag to compare

@romerramos romerramos released this 11 Oct 11:49
5e8f2ce

Verdicts are now shared with everyone who has GitHub access to the repository, while your votes stay private.

New

  • Shared repository verdicts. A verdict on a pull request is visible to anyone who currently has GitHub access to that repository. If someone already asked Jev about the same commit, you see that verdict straight away, without using your weekly allowance.
  • Private votes. Your vote and reason on a verdict are personal. Teammates can't see them, even on shared verdicts.
  • Refresh links. The repository and pull request lists show when they were last read from GitHub, with a Refresh link to read them again. The verdicts page has a "Check again" link to re-check your repository access.

Improved

  • Repository and pull request lists load faster: GitHub reads are cached briefly, and diff stats are cached per commit.
  • "Ask Jev again" always gets a fresh verdict, even when a saved one exists for the commit.
  • Repositories are tracked by GitHub's stable ID, so renames and reused names never mix up verdicts.
  • A pull request marked as too big is only skipped for the exact commit Jev couldn't read.

Upgrade notes

  • Back up your database before upgrading. This release has a migration (share_repository_verdicts) that can't be rolled back: it moves votes into a new table and removes the old columns. To roll back, restore the backup.
  • Verdicts saved before this release stay private to the person who asked for them. Asking again creates a new shared verdict.
  • Deleting an account now removes the user, their token, sessions, pins, votes and older private verdicts. Shared verdicts and usage records stay, without a link to the account.
  • No new secrets, settings or routes.

v0.1.5

Choose a tag to compare

@romerramos romerramos released this 02 Oct 15:59

Tell Jev when it got a verdict right or wrong, and see how often you agree.

New

  • Vote on a verdict. The verdict page asks "Did Jev get this right?". Agree takes one click. Disagree asks what the verdict should have been and, if you like, why. You can change or clear your vote at any time.
  • Your agreement at a glance. The verdicts list sums up your votes, e.g. "You agreed with 18 of 20 verdicts you rated. 1 needed more review than Jev said."

Your data

  • Votes are stored with the verdict they belong to. Only you see them, nothing is collected unless you vote, and Delete my data removes them along with your verdicts. The README's Your data section lists them.

Upgrade notes

  • One database migration, which adds three optional columns to verdicts. bin/update runs it. No new secrets or settings.

v0.1.4

Choose a tag to compare

@romerramos romerramos released this 02 Oct 15:36

Try Jev my PR locally without a GitHub OAuth app or a TypeSafe key, using sample data.

New

  • Development preview. In development, when the GitHub OAuth app or the TypeSafe key is missing, the sign-in page offers Try with sample data. It walks sample repositories and pull requests through all three verdicts (human review, LLM review, no review), including a verdict for each changed file. Set PREVIEW_MODE=1 to force it on even with credentials.
  • Nothing in preview is sent to GitHub or Jev, and sample verdicts use zero tokens, so they don't count against the monthly budget.

Improved

  • Development now accepts *.onamp.dev hosts, so the app loads through an Amp portal.

Upgrade notes

None. Preview is never on in production: its sign-in route returns a 404 there, and real GitHub sign-in is unchanged.

v0.1.3

Choose a tag to compare

@romerramos romerramos released this 02 Oct 14:06

Searching for a pull request now finds older ones too, not just the 100 most recently updated.

Fixed

  • Search reaches every open pull request (#8). On repositories with more than 100 open PRs, older ones couldn't be found, even by number. Now:
    • #123 (or 123) finds that pull request directly, if it's open.
    • Other words also search the titles of older open pull requests.
    • A single username also finds older open pull requests by that author.

The list you see before searching is unchanged: the 100 most recently updated open pull requests.

Upgrade notes

None: no migrations, secrets or settings.

v0.1.2

Choose a tag to compare

@romerramos romerramos released this 02 Oct 13:25

Jev now tags every changed file too, so you can see where a reviewer should look first.

New

  • A verdict for each file. When you ask Jev about a pull request, it also tags each changed file as Human review, LLM review or No review. It's all one request: Jev reads the pull request once and answers for the whole PR and every file in parallel, so it still counts as a single verdict.
  • The verdict page lists files that need a human first, then those an LLM review covers, then the ones that need no review, with a count of each above the list. Hover a file's tag to see Jev's probabilities.

Improved

  • The human review verdict reads more gently: "Jev thinks a human reviewer would be useful here."
  • Jev now reads the diff file by file, using whole patches up to 100 KB, rather than cutting the diff off partway through a file.

Upgrade notes

None: no migrations, secrets or settings. Verdicts saved before this release have no file tags; ask Jev again to get them.

v0.1.1

Choose a tag to compare

@romerramos romerramos released this 26 Sep 19:52

Huge pull requests now get a clear "too big" answer instead of a raw error.

Improved

  • When a pull request is too big for Jev to read, you see a friendly message instead of "Jev returned HTTP 400".
    The pull request is marked Too big in the list and opens on GitHub instead of asking Jev again (and failing).
    If it changes later, you can ask Jev again.
  • The verdict page no longer asks for a coffee under the answer; the link in the footer stays.

Upgrade notes

  • One new migration (a table for too-big marks). bin/update runs it. No new secrets or settings.