Repository navigation
ticket-api 1.2.1 (hotfix)
- Fixed:
GET /v1/historyanswered500when the history had rows from version 1.1.0. Those rows have noscore; the API now uses theirconfidence. This happened while 1.1.0 and 1.2.0 ran at the same time on one database, during the rollout of 1.2.0. - Why the checks missed it: the database tests made all their rows with 1.2.0, and the smoke check did not call
/v1/history. Both are added in this release: a test with a row from 1.1.0, and a smoke check that fails on a5xxfrom/v1/history. - Made from: the tag
v1.2.0, on the branchhotfix/1.2.1. The same fix is merged intomain. - Owner: Amira. Watch after release:
GET /v1/historyand the error rate, for one day. - Rollback: deploy the 1.2.0 digest (the bug comes back), or 1.1.0.
Image: ghcr.io/usmanahmed99/ticket-api-ci@sha256:84937455beb63744755622d539748c9adb1772f379c9eb7e4f961c5b7f1bc924 (tag 1.2.1)