v1.2.1

ticket-api 1.2.1 (hotfix)

• Fixed: GET /v1/history answered 500 when the history had rows from version 1.1.0. Those rows have no score; the API now uses their confidence. 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 a 5xx from /v1/history.
• Made from: the tag v1.2.0, on the branch hotfix/1.2.1. The same fix is merged into main.
• Owner: Amira. Watch after release: GET /v1/history and 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)

v1.2.0

ticket-api 1.2.0

• New for clients: every classification has score, from 0 to 1. confidence has the same value and is deprecated: it stays until version 2.0, so clients have time to change. History items have score too.
• New, off by default: classifier keywords-1.1 (CLASSIFIER_VERSION=1.1). On the 33 holdout tickets: accuracy 0.909 (keywords-1.0: 0.636), every must-pass ticket right. We turn it on in production step by step.
• Database: migrations replace the table that the app made at start-up. Run python -m ticket_api.migrate before the new version starts (Compose does it in the migrate service). Migration 002_add_score adds a column; version 1.1.0 keeps working with it.
• Owner: Amira. Watch after release: the smoke checks, the error rate in the logs, and GET /v1/history, for one day.
• Rollback: deploy the 1.1.0 digest. The database needs no change: 1.1.0 ignores the new column.

Image: ghcr.io/usmanahmed99/ticket-api-ci@sha256:bd2316b56067c738199d6203a23845c97fb7b85b550379411eddd7cc6a2ddab8 (tag 1.2.0)

v1.1.0

ticket-api 1.1.0

The first release through the pipeline. The code is the same as at the end of C18.

• Changes for clients: none.
• Checks: lint, 25 tests, pip-audit, image smoke check, staging smoke check.
• Owner: Amira. Watch after release: the production smoke check and the logs, for one hour.
• Rollback: deploy the previous digest with the Deploy workflow (Run workflow).

Image: ghcr.io/usmanahmed99/ticket-api-ci@sha256:4eb3db8d4ea249fb9b44b27d96deb68aba6da3e3fbc9cf32311a9cbadf4d857a (tag 1.1.0)