chore(wiki): build.1790257574 (ask API, TypeSafe judge) #945

2026-09-24T13:49:06Z

claude-bot commented

2026-09-24 13:49:06 +00:00

Pins the image from Wiki PR #5: POST /api/v1/ask and the TypeSafe judge, which reads the key from the wiki-typesafe ExternalSecret merged in #944. Verification after merge: /api/v1/status lists typesafe:typesafe ok, and an ask through the ClusterIP returns judgements with paragraph text.

🤖 Generated with Claude Code

Pins the image from Wiki PR #5: `POST /api/v1/ask` and the TypeSafe judge, which reads the key from the `wiki-typesafe` ExternalSecret merged in #944. Verification after merge: `/api/v1/status` lists `typesafe:typesafe` ok, and an ask through the ClusterIP returns judgements with paragraph text. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

claude-bot added 1 commit 2026-09-24 13:49:06 +00:00

chore(wiki): build.1790257574 (ask API, TypeSafe judge)

ci/woodpecker/pr/ci-scripts-test Pipeline was successful

Details

ci/woodpecker/pr/ci-manifests-test Pipeline was successful

Details

ci/woodpecker/pr/pr-review Pipeline was successful

Details

0775dac615

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

review-bot reviewed

2026-09-24 13:51:04 +00:00

review-bot left a comment

🤖 Automated review — model claude-haiku-4-5-20251001 (complexity: trivial), commit 0775dac615c104787c300eb64544c74a46aca702.

Advisory review by the review-bot pipeline. It never approves; a human merges. Push new commits to get a fresh review.

Summary

This PR updates the wiki service deployment to pin a newer build image (build.1790257574 from Wiki PR #5), which adds POST /api/v1/ask functionality with a TypeSafe judge. The change is minimal and focused: a single file with two lines changed (image tag and comment).

🟡 Suggestions

kubernetes/apps/wiki/deployment.yaml:50-51 — Image tag format. The comment mentions this is a build.<unix-ts> tag from the Wiki repo's release pipeline. Consider documenting in the PR or commit message when this build will be considered "stable" or how rollback is handled if the judge integration doesn't work as expected. (Not blocking, but useful operational context.)

Post-merge verification — The PR body mentions two verification steps that should happen after merge: checking /api/v1/status for typesafe:typesafe ok, and testing ask functionality via ClusterIP. These are noted but not part of pre-merge validation.

Verification

✅ YAML syntax is valid
✅ All referenced ExternalSecrets exist (wiki-gitea, wiki-api-keys, wiki-typesafe)
✅ Security configuration unchanged; no new privileges or secrets exposed
✅ Referenced dependency wiki-typesafe secret is properly defined in externalsecrets.yaml and pulls the API key from OpenBao
✅ Single focused commit with clear intent

Tests

For Kubernetes deployment version bumps, testing happens at runtime. The PR body describes the expected behavior (ask API availability, TypeSafe judge returning paragraph text), which will be verified post-merge.

Recommendation

Looks reasonable — no blocking issues; comments above are optional.

🤖 **Automated review** — model `claude-haiku-4-5-20251001` (complexity: trivial), commit `0775dac615c104787c300eb64544c74a46aca702`. > Advisory review by the `review-bot` pipeline. It never approves; a human merges. Push new commits to get a fresh review. --- ## Summary This PR updates the wiki service deployment to pin a newer build image (`build.1790257574` from Wiki PR #5), which adds POST `/api/v1/ask` functionality with a TypeSafe judge. The change is minimal and focused: a single file with two lines changed (image tag and comment). ## 🟡 Suggestions **`kubernetes/apps/wiki/deployment.yaml:50-51`** — Image tag format. The comment mentions this is a `build.<unix-ts>` tag from the Wiki repo's release pipeline. Consider documenting in the PR or commit message when this build will be considered "stable" or how rollback is handled if the judge integration doesn't work as expected. (Not blocking, but useful operational context.) **Post-merge verification** — The PR body mentions two verification steps that should happen after merge: checking `/api/v1/status` for `typesafe:typesafe` ok, and testing ask functionality via ClusterIP. These are noted but not part of pre-merge validation. ## Verification - ✅ YAML syntax is valid - ✅ All referenced ExternalSecrets exist (`wiki-gitea`, `wiki-api-keys`, `wiki-typesafe`) - ✅ Security configuration unchanged; no new privileges or secrets exposed - ✅ Referenced dependency `wiki-typesafe` secret is properly defined in `externalsecrets.yaml` and pulls the API key from OpenBao - ✅ Single focused commit with clear intent ## Tests For Kubernetes deployment version bumps, testing happens at runtime. The PR body describes the expected behavior (ask API availability, TypeSafe judge returning paragraph text), which will be verified post-merge. ## Recommendation Looks reasonable — no blocking issues; comments above are optional.

k.renner merged commit 64f29ce419 into master

2026-09-24 13:56:05 +00:00

k.renner referenced this issue from a commit

2026-09-24 13:56:06 +00:00

Merge pull request 'chore(wiki): build.1790257574 (ask API, TypeSafe judge)' (#945) from chore/wiki-phase3-image into master

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: konairius/homelab#945