prepare capnp-rpc-v0.16.1 release

dwrensha · dwrensha · commit c650d0eefb64 · 2023-01-17T09:10:51.000-05:00
diff --git a/capnp-rpc/CHANGELOG.md b/capnp-rpc/CHANGELOG.md
@@ -1,3 +1,6 @@
+## v0.16.1
+- Regenerate code, with rpc.capnp from upstream latest release, version 0.10.3.
+
 ## v0.16.0
 - Add reconnect API.
 
diff --git a/capnp-rpc/Cargo.toml b/capnp-rpc/Cargo.toml
@@ -1,7 +1,7 @@
 [package]
 
 name = "capnp-rpc"
-version = "0.16.0"
+version = "0.16.1"
 authors = [ "David Renshaw <dwrenshaw@sandstorm.io>" ]
 license = "MIT"
 description = "implementation of the Cap'n Proto remote procedure call protocol"
diff --git a/capnp-rpc/schema/rpc.capnp b/capnp-rpc/schema/rpc.capnp
@@ -316,7 +316,7 @@ struct Bootstrap {
   # A Vat may export multiple bootstrap interfaces. In this case, `deprecatedObjectId` specifies
   # which one to return. If this pointer is null, then the default bootstrap interface is returned.
   #
-  # As of verison 0.5, use of this field is deprecated. If a service wants to export multiple
+  # As of version 0.5, use of this field is deprecated. If a service wants to export multiple
   # bootstrap interfaces, it should instead define a single bootstrap interface that has methods
   # that return each of the other interfaces.
   #
@@ -352,7 +352,7 @@ struct Bootstrap {
   # - Overloading "Restore" also had a security problem: Often, "main" or "well-known"
   #   capabilities exported by a vat are in fact not public: they are intended to be accessed only
   #   by clients who are capable of forming a connection to the vat. This can lead to trouble if
-  #   the client itself has other clients and wishes to foward some `Restore` requests from those
+  #   the client itself has other clients and wishes to forward some `Restore` requests from those
   #   external clients -- it has to be very careful not to allow through `Restore` requests
   #   addressing the default capability.
   #

Original file line number	Diff line number	Diff line change
`@@ -316,7 +316,7 @@ struct Bootstrap {`
`316`	`316`	# A Vat may export multiple bootstrap interfaces. In this case, `deprecatedObjectId` specifies
`317`	`317`	`# which one to return. If this pointer is null, then the default bootstrap interface is returned.`
`318`	`318`	`#`
`319`		`- # As of verison 0.5, use of this field is deprecated. If a service wants to export multiple`
	`319`	`+ # As of version 0.5, use of this field is deprecated. If a service wants to export multiple`
`320`	`320`	`# bootstrap interfaces, it should instead define a single bootstrap interface that has methods`
`321`	`321`	`# that return each of the other interfaces.`
`322`	`322`	`#`
`@@ -352,7 +352,7 @@ struct Bootstrap {`
`352`	`352`	`# - Overloading "Restore" also had a security problem: Often, "main" or "well-known"`
`353`	`353`	`# capabilities exported by a vat are in fact not public: they are intended to be accessed only`
`354`	`354`	`# by clients who are capable of forming a connection to the vat. This can lead to trouble if`
`355`		- # the client itself has other clients and wishes to foward some `Restore` requests from those
	`355`	+ # the client itself has other clients and wishes to forward some `Restore` requests from those
`356`	`356`	# external clients -- it has to be very careful not to allow through `Restore` requests
`357`	`357`	`# addressing the default capability.`
`358`	`358`	`#`