service_mesh 0.4.1 → 0.4.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: fef05ef9dacd492215d76304b8f1938056e862e35c0e0450f7b120213bf7e8d7
-  data.tar.gz: 97cb3e42dc4797d618d3eacf61aa3d2ba994887aa94ee88d37d90b6b04211fb6
+  metadata.gz: 0d1c22ba40201e6531617371be60f030c23976f3a31d06a536114a388c59a9f0
+  data.tar.gz: c3e7fd9aedbc639cde6d3727e028799fa51d3222a0006826655084e9f6cb36ea
 SHA512:
-  metadata.gz: c7da5185432f80a50b73ec3942c736367455bc337918b7afba2b8393a1575353e54a9fbdb54d98aeaf03c7b0922766490a8da075c8daf4d2a58087044e1e448b
-  data.tar.gz: 4418d34275bc4dd1d532b4b84f48361967601275181c64c50c5cb7ca7177ddecd9ebdedbb773d813d07e55307efeb24b63c2753a8c6881ea66803e1e619f3127
+  metadata.gz: d9ebe5643e51f2aebb1ddb7896344b7db28ec0bced10a6cb759db597ffafea1c558dd7612daa9297d4fb4d36c413349c3b085a692770ea0c60742a892d1beffa
+  data.tar.gz: a5d57ce5d40a07b3ce478ba55dead8115c62c7f6bb678115e90fce513ef27128e851d33f71dd408d318fae5411a1eb53b086d1b539b867bec225934ed7558071

data/README.md

@@ -1,15 +1,11 @@
 # service-mesh-ruby
 
-The Ruby contract for the
-[Service Mesh API Specification](https://github.com/Paymentbox-com/service-mesh-api),
-packaged as the gem `service_mesh`. It holds what every transport and every
+service-mesh-ruby is the Ruby contract for the
+[Service Mesh API Specification](https://github.com/Paymentbox-com/service-mesh-api).
+It is packaged as the gem `service_mesh`. It holds what every transport and every
 caller must agree on, and nothing that moves bytes. Transports are separate
 gems that depend on it and implement `Client` and `Runtime`.
 
-The [gRPC Service Mesh API](https://github.com/Paymentbox-com/grpc-service-mesh-api) is a protocol layer that generates code against this contract from protobuf
-definitions, through its Ruby library [grpc-service-mesh-ruby](https://github.com/Paymentbox-com/grpc-service-mesh-ruby). Other protocol layers may be implemented 
-to do the same. 
-
 ## Install
 
 ```ruby
@@ -21,34 +17,26 @@ Requires Ruby 3.3 or newer. The gem has no runtime dependencies.
 
 ## What it Implements
 
-- The value types from the specification: `ServiceMesh::Target`, `ServiceMesh::ServiceMap`, 
-  `ServiceMesh::Message`, `ServiceMesh::Endpoint` and `ServiceMesh::Subscriber`.
+- The value types from the specification: `ServiceMesh::Target`, `ServiceMesh::ServiceMap`,
+  `ServiceMesh::Message`, `ServiceMesh::Endpoint`, and `ServiceMesh::Subscriber`.
 - Target Kinds are implemented as `:route` and `:topic`. A `Target` built with a kind outside the two
   raises `KindMismatch`.
 - `Message#payload` is always `Encoding::BINARY`.
-- `Target#same_channel?` compares segments and kind and ignores metadata. 
+- `Target#same_channel?` compares segments and kind and ignores metadata.
 - The configuration keys the specification defines: `DEPLOYMENT_GROUP_KEY`,
   `CONSUMER_GROUP_KEY`, and the value `CONSUMER_GROUP_NONE`.
 - The errors defined by the specification as `ServiceMesh::Error`: `ServiceMesh::KindMismatch`,
-  `ServiceMesh::InvalidTarget`, `ServiceMesh::NoDeploymentGroup`.
+  `ServiceMesh::InvalidTarget`, and `ServiceMesh::NoDeploymentGroup`.
 - A conformance suite a transport runs against its own `Client` and
   `Runtime`.
 
-`Client` and `Runtime` are duck types. The specification names their methods;
-a transport satisfies the contract by responding to them and by passing the
+`Client` and `Runtime` are duck types. The specification names their methods,
+and a transport satisfies the contract by responding to them and by passing the
 conformance suite.
 
-## Transports
-
-- NATS: [service-mesh-nats-ruby](https://github.com/Paymentbox-com/service-mesh-nats-ruby),
-  gem `service_mesh_nats`.
-
-The Go counterpart of this gem is
-[service-mesh-go](https://github.com/Paymentbox-com/service-mesh-go).
-
 ## Usage
 
-A transport that implements Client and Runtime according to the specification will used the
+A transport that implements `Client` and `Runtime` according to the specification uses the
 types defined here.
 
 ```ruby
@@ -84,10 +72,18 @@ RSpec.describe MyTransport do
 end
 ```
 
-The suite covers kind checks, the deployment group requirement, request and
-reply with metadata both ways, publish, the consumer-group delivery
-permutations across two runtimes, a standalone client refusing requests after
-close, the runtime's client being the one it was given and closed by stop, the lifecycle state machine, and drain completing and expiring.
+The suite covers:
+
+- kind checks
+- the deployment group requirement
+- request and reply with metadata both ways
+- publish
+- the consumer-group delivery permutations across two runtimes
+- a standalone client refusing requests after close
+- the runtime's client being the one it was given and closed by stop
+- the lifecycle state machine
+- drain completing and expiring
+
 Anything that names a transport's own errors, config keys, or address syntax
 stays in the transport's specs.
 
@@ -97,10 +93,9 @@ stays in the transport's specs.
 mise install
 just install
 just check      # lint, test, build
+just test       # tests only
 ```
 
-## Tests
-
-```
-just test
-```
+Releasing is described in [publishing.md](publishing.md). `just bump patch`,
+`just bump minor`, or `just bump major` raises the version in
+`lib/service_mesh/version.rb` and commits that file.

data/lib/service_mesh/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module ServiceMesh
-  VERSION = "0.4.1"
+  VERSION = "0.4.4"
 end

metadata

@@ -1,17 +1,19 @@
 --- !ruby/object:Gem::Specification
 name: service_mesh
 version: !ruby/object:Gem::Version
-  version: 0.4.1
+  version: 0.4.4
 platform: ruby
 authors:
+- Bryant Morrill
 - Paymentbox
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2026-09-25 00:00:00.000000000 Z
+date: 2026-09-29 00:00:00.000000000 Z
 dependencies: []
 description:
 email:
+- bryantreadmorrill@gmail.com
 executables: []
 extensions: []
 extra_rdoc_files: []