Publish otel-a2a-relay-core to an index; switch deploy Dockerfile from git-dep to wheel #31
Labels
No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set.
Reference
coilyco-flight-deck/otel-a2a-relay#31
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-up from splitting the deploy surface into
otel-a2a-relay-deploy(#25).The deploy repo's Dockerfile currently installs
otel-a2a-relay-coreas a pinned git dependency from this repo'score/subdir (git+https://.../otel-a2a-relay.git@<ref>#subdirectory=core). That works but is the interim: it couples the image build back to this repo's git, needsgitin the build stage, and is only reproducible ifO2R_REFis pinned to a tag/commit.The clean end-state is publishing
otel-a2a-relay-coreto an index:uv build+ publish onv*tags, or a release workflow) forotel-a2a-relay-core.otel-a2a-relay-deploy, switch the Dockerfile from the git dependency to a versioned wheel (uv pip install otel-a2a-relay-core==X.Y.Z) and drop the git stage.This makes the dependency direction fully clean: the deploy repo consumes a published artifact instead of reaching into this repo's source tree.
Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag:
burndown-2026-06.