Skip to content

ref(api): correct release threshold response types#119925

Open
cvxluo wants to merge 1 commit into
masterfrom
cvxluo/correct-release-threshold-response-types
Open

ref(api): correct release threshold response types#119925
cvxluo wants to merge 1 commit into
masterfrom
cvxluo/correct-release-threshold-response-types

Conversation

@cvxluo

@cvxluo cvxluo commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

Fix some types in the release thresholds endpoint.

@github-actions github-actions Bot added the Scope: Backend Automatically applied to PRs that change backend components label Jul 17, 2026
The status endpoint's documented types diverged from the serializer:
threshold_type is serialized as a string name (not an int), the date
field is emitted as date_added, and trigger_type has a fixed vocabulary.
Add Literal name types at the constants owner, annotate the int-to-str
maps with them, and align the docs example and test fixtures with the
real payload shape.

Co-authored-by: Claude <noreply@anthropic.com>
@cvxluo
cvxluo marked this pull request as ready for review July 17, 2026 18:43
@cvxluo
cvxluo requested review from a team as code owners July 17, 2026 18:43
@cvxluo
cvxluo force-pushed the cvxluo/correct-release-threshold-response-types branch from b79ef06 to 5d32c11 Compare July 20, 2026 18:16

@coolguyzone coolguyzone left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good from a docs standpoint.

@cvxluo
cvxluo requested a review from a team July 20, 2026 21:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants