mesh-controller/modules/route-proxy/vendor/github.com/nats-io/nats.go/CODE-OF-CONDUCT.md at 499ff5c2186196431baf0ec9f43618e4fe86df77

Files

T

jschoubben 499ff5c218

mesh/delivery-group group feat/r4d rejected: a member's own check failed

Details

mesh/repo-check out of date: judged beside mesh-catalog#434 at c948f3a61c74, it is now at 7451e7edf4e5; judged again on a recheck or when it is merged

Details

mesh/merge-gate group feat/r4d: composed again for the group's new heads

Details

mesh/delivery superseded: a newer head of the same pull request

Details

mesh/check failed: unit: i3/cmd/i3-tools.TestTheMainFileAndEveryModulesContributionLoadTogether: manifest_test.go:247: expected the launcher, clipboar…

Move the route proxy into its module and run it from the trust image, on mesh-sdk's public membership (issues 1633, 1634, 1635)

A bundle is built only from its module's directory (ADR 0480 clause 4), so the proxy leaves
examples/ and the controller's internal/broker; the broker keeps no second copy of what the
proxy shares with mesh-sdk. The image and its Dockerfile go, and a test holds that only
build-agent declares one (clause 11).

2026-10-22 09:53:56 +02:00

138 B

Raw Blame History

Community Code of Conduct

NATS follows the CNCF Code of Conduct.

138 B Raw Blame History

Community Code of Conduct

138 B

Raw Blame History