feat: api client support for triggering builds - #388
Merged
Conversation
|
This was referenced Jul 14, 2026
Merged
Blackgaurd
approved these changes
Jul 25, 2026
docs: document build trigger in frontend spec
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
feat: build trigger ui
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds
triggerBuild()anddryRunBuild()to the typed api client (lib/api.ts), both hittingPOST /api/v1/build/{name}/{version}— the dry-run variant passesdry-run=true. Adds theBuildResponseandDryRunBuildResponsetypes (dry-run reuses the existingDataRowshape, same asGET /data).Why
The browsing UI is deliberately read-only (
build-data=falseeverywhere), so until now the only way to build data was curl. This gives the frontend a typed path to the existing build endpoint ahead of the build-panel UI (next PR in the stack).Benefit
Builds become explicitly triggerable from the browser, with dry runs available to preview builder output without writing to the db. Errors reuse
ApiError, so backenddetailmessages (e.g. 422 no-valid-timestamps) surface verbatim in the UI.