• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

stacklok / toolhive / 24718401480
66%

Build:
DEFAULT BRANCH: main
Ran 21 Apr 2026 10:57AM UTC
Jobs 1
Files 653
Run time 2min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

21 Apr 2026 10:52AM UTC coverage: 66.451% (+0.04%) from 66.414%
24718401480

push

github

web-flow
Add registry-aware workload creation (#4872)

* Add registry-aware workload creation

Add optional registry and server fields to POST /api/v1beta/workloads
so clients can create workloads by referencing a registry server:

  {"registry": "default", "server": "io.github.stacklok/fetch"}

thv resolves the server from the registry, extracts image/transport/
env vars/permissions/etc from metadata, and builds the RunConfig
server-side. User-provided fields always override registry defaults.

This eliminates client-side field extraction — Studio goes from
GET+extract+POST to just POST.

Ref: #4199

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* Regenerate OpenAPI spec for registry-aware workload fields

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* Address review findings for registry-aware workload creation

- Fix handler validation: accept registry+server as alternative to
  image/url (was rejecting before resolution could run)
- Fix validation ordering: check registry+server pairing before
  attempting resolution
- Validate registry name: only "default" is currently supported,
  reject unknown values with clear error
- Regenerate OpenAPI spec

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* Preserve registry metadata through BuildFullRunConfig

Return ServerMetadata from resolveRegistryServer and assign it to
the local serverMetadata/imageMetadata variables so downstream code
(registry info on RunConfig, tool validation, remote auth config,
proxy port) has access to it.

Skip the imageRetriever re-lookup when metadata was already resolved
from a registry reference — re-looking up by bare image ref would
fail since the image ref doesn't match any server name.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* Complete remote server metadata handling and address review feedback

Fix remote server path to get the same treatment as image servers:
- Extract ProxyP... (continued)

104 of 158 new or added lines in 3 files covered. (65.82%)

8 existing lines in 3 files now uncovered.

58403 of 87889 relevant lines covered (66.45%)

62.55 hits per line

Uncovered Changes

Lines Coverage ∆ File
48
78.78
1.47% pkg/api/v1/workload_service.go
6
21.97
-0.09% pkg/api/v1/workloads.go

Coverage Regressions

Lines Coverage ∆ File
4
89.77
0.0% pkg/api/v1/skills.go
2
73.63
-0.64% pkg/runner/config.go
2
94.77
-1.31% pkg/vmcp/composer/dag_executor.go
Jobs
ID Job ID Ran Files Coverage
1 24718401480.1 21 Apr 2026 10:57AM UTC 653
66.45
GitHub Action Run
Source Files on build 24718401480
  • Tree
  • List 653
  • Changed 13
  • Source Changed 6
  • Coverage Changed 13
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #24718401480
  • 829c4bd0 on github
  • Prev Build on main (#24717970862)
  • Next Build on main (#24718682366)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc