PerishLab/actions
1
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages 1 Wiki Activity Actions

Carry the image and chart projections again #45

Merged
PerishFire merged 1 commit from land/task/forge-projection-clients into main 2026-08-16 17:02:12 +00:00
Conversation 0 Commits 1 Files changed 5 +24 -14
PerishFire commented 2026-08-16 17:00:22 +00:00
Owner
Copy link

Carry the image and chart projections again

The two deeds left this lane because canonical stable read a projection's
registry identity in argument position, ahead of the early return that
answers for an attachment nobody declared, so calling them refused every
product that declared neither. Canonical stable is v0.21.0 now, which reads
a credential only after it knows it has something to project.

That was only half of why no product could declare an image or a chart. The
deeds run docker build and helm package, and the job image carried
neither client, so the medium was undeclarable rather than unconfigured. The
Forge image carries both as of 3a79a25, and this lane moves to that image
and names the endpoint they speak to. The image carries clients only; the
daemon is the host's, exactly as this repository's own image lanes already
arrange.

A product that declares neither attachment opens no endpoint and pays
nothing: each deed answers that it has none and succeeds.

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

Carry the image and chart projections again The two deeds left this lane because canonical stable read a projection's registry identity in argument position, ahead of the early return that answers for an attachment nobody declared, so calling them refused every product that declared neither. Canonical stable is v0.21.0 now, which reads a credential only after it knows it has something to project. That was only half of why no product could declare an image or a chart. The deeds run `docker build` and `helm package`, and the job image carried neither client, so the medium was undeclarable rather than unconfigured. The Forge image carries both as of `3a79a25`, and this lane moves to that image and names the endpoint they speak to. The image carries clients only; the daemon is the host's, exactly as this repository's own image lanes already arrange. A product that declares neither attachment opens no endpoint and pays nothing: each deed answers that it has none and succeeds. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Carry the image and chart projections again
All checks were successful
guard / runner-control (pull_request) Successful in 10s
Details
guard / runner-control (push) Successful in 15s
Details
guard / guard (pull_request) Successful in 26s
Details
guard / package-windows (pull_request) Successful in 1m18s
Details
guard / guard (push) Successful in 26s
Details
guard / package-windows (push) Successful in 1m14s
Details
4666d6a519 
Carry the image and chart projections again

The two deeds left this lane because canonical stable read a projection's
registry identity in argument position, ahead of the early return that
answers for an attachment nobody declared, so calling them refused every
product that declared neither. Canonical stable is v0.21.0 now, which reads
a credential only after it knows it has something to project.

That was only half of why no product could declare an image or a chart. The
deeds run `docker build` and `helm package`, and the job image carried
neither client, so the medium was undeclarable rather than unconfigured. The
Forge image carries both as of `3a79a25`, and this lane moves to that image
and names the endpoint they speak to. The image carries clients only; the
daemon is the host's, exactly as this repository's own image lanes already
arrange.

A product that declares neither attachment opens no endpoint and pays
nothing: each deed answers that it has none and succeeds.

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

Land-Source: task/forge-projection-clients@e7ec921799
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
PerishLab/actions!45
No description provided.