Skip to content

v0.2.3

Choose a tag to compare

@romerramos romerramos released this 11 Oct 15:40
· 3 commits to main since this release
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.