diff --git a/packages/rfw/CHANGELOG.md b/packages/rfw/CHANGELOG.md
index 7ee59b2d0b5d..938b77083f72 100644
--- a/packages/rfw/CHANGELOG.md
+++ b/packages/rfw/CHANGELOG.md
@@ -1,3 +1,7 @@
+## 1.1.1
+
+* Removes obsolete scripting language integration section in README.md.
+
 ## 1.1.0
 
 * Adds support for the `Flexible` core widget.
diff --git a/packages/rfw/README.md b/packages/rfw/README.md
index da88dbb69eff..b45f8e74a0e2 100644
--- a/packages/rfw/README.md
+++ b/packages/rfw/README.md
@@ -936,36 +936,6 @@ This example also shows how an application can implement custom local
 code for events; in this case, incrementing a counter (both of the
 "remote" widgets are just different ways of implementing a counter).
 
-### Integrating with scripting language runtimes
-
-The example in `example/wasm` shows how a program could fetch logic in
-addition to UI, in this case using Wasm compiled from C (and let us
-briefly appreciate the absurdity of using C as a scripting language
-for an application written in Dart).
-
-In this example, as written, the Dart client could support any
-application whose data model consisted of a single integer and whose
-logic could be expressed in C without external dependencies.
-
-This example could be extended to have the C program export data in
-the Remote Flutter Widgets binary data blob format which could be
-parsed using `decodeDataBlob` and passed to `DynamicContent.update`
-(thus allowing any structured data supported by RFW), and similarly
-arguments could be passed to the Wasm code using the same format
-(encoding using `encodeDataBlob`) to allow arbitrary structured data
-to be communicated from the interface to the Wasm logic. In addition,
-the Wasm logic could be provided with WASI interface bindings or with
-custom bindings that expose platform capabilities (e.g. from Flutter
-plugins), greatly extending the scope of what could be implemented in
-the Wasm logic.
-
-As of the time of writing, `package:wasm` does not support Android,
-iOS, or web, so this demo is limited to desktop environments. The
-underlying Wasmer runtime supports Android and iOS already, and
-obviously Wasm in general is supported by web browsers, so it is
-expected that these limitations are only temporary (modulo policy
-concerns on iOS, anyway).
-
 ## Contributing
 
 See [CONTRIBUTING.md](https://github.com/flutter/packages/blob/main/packages/rfw/CONTRIBUTING.md)
diff --git a/packages/rfw/pubspec.yaml b/packages/rfw/pubspec.yaml
index 475eb126d125..3f9cf954dcb3 100644
--- a/packages/rfw/pubspec.yaml
+++ b/packages/rfw/pubspec.yaml
@@ -2,7 +2,7 @@ name: rfw
 description: "Remote Flutter widgets: a library for rendering declarative widget description files at runtime."
 repository: https://github.com/flutter/packages/tree/main/packages/rfw
 issue_tracker: https://github.com/flutter/flutter/issues?q=is%3Aissue+is%3Aopen+label%3A%22p%3A+rfw%22
-version: 1.1.0
+version: 1.1.1
 
 environment:
   sdk: ^3.9.0