Repository navigation
Agent Messaging Server 0.1.1
·
16 commits
to main
since this release
A patch release of the Agent Messaging Server: the server and the A2A gateway, for the core profile of Agent Messaging 0.7.0, on NATS JetStream or on RabbitMQ with Postgres.
Images
docker pull ghcr.io/jeffrschneider/agent-messaging-server:0.1.1
docker pull ghcr.io/jeffrschneider/agent-messaging-a2a-gateway:0.1.1Both are linux/amd64, built from this tag and tested by the release workflow (first-run from an empty volume, NATS on what it wrote, the server, a live revocation, the A2A gateway connecting).
What changed since 0.1.0
- The SDK the server and the gateway run (0.58.1) takes its default addresses from
AGENTMESH_API_URL,AGENTMESH_NAMING_URLandAGENTMESH_BROKER_WSSwhen they are set, so a deployment can point the server's and the gateway's default API, naming service and broker at its own mesh. Unset, nothing changes. - The server, the gateway and the SDK each declare
nkeys.js, which they import; before, it came in only through another package (in the gateway, as an optional one). - Releases are made only from this repository: images from a
server-v<version>tag, the SDK from ansdk-v<version>tag (docs/releasing.md). - A boundary check in CI: nothing imports outside the server, the gateway and the SDK, and the core reaches the broker only through its storage layer.
The TypeScript SDK
SDK 0.58.1 is its own release, sdk-v0.58.1, with its tarball and SHA-256. It is also at https://storage.googleapis.com/agentmesh-releases/agentmesh-0.58.1.tgz (SHA-256 be5efb29d116fb31fb4205709b576a572026663cf5e5030262979fdd17c0511e).