diff --git a/custom_components/pyscript/manifest.json b/custom_components/pyscript/manifest.json
index 727f32d..720c9b9 100644
--- a/custom_components/pyscript/manifest.json
+++ b/custom_components/pyscript/manifest.json
@@ -12,6 +12,6 @@
   "issue_tracker": "https://github.com/custom-components/pyscript/issues",
   "requirements": ["croniter==1.3.8", "watchdog==2.3.1"],
   "ssdp": [],
-  "version": "1.4.0",
+  "version": "1.5.0",
   "zeroconf": []
 }
diff --git a/docs/conf.py b/docs/conf.py
index 4238a48..56a2a63 100644
--- a/docs/conf.py
+++ b/docs/conf.py
@@ -23,7 +23,7 @@
 author = 'Craig Barratt'
 
 # The full version, including alpha/beta/rc tags
-release = '1.4.0'
+release = '1.5.0'
 
 master_doc = 'index'
 
diff --git a/docs/new_features.rst b/docs/new_features.rst
index fe08e2f..095da44 100644
--- a/docs/new_features.rst
+++ b/docs/new_features.rst
@@ -8,8 +8,8 @@ You can also install the master (head of tree) version from GitHub, either using
 Because pyscript has quite a few unit tests, generally the master version should work ok. But it's not
 guaranteed to work at any random time, and newly-added features might change.
 
-This is 1.4.0, released on April 4, 2023.  Here is the `documentation
-<https://hacs-pyscript.readthedocs.io/en/1.4.0>`__ for that release.  Here is the
+This is 1.5.0, released on July 30, 2023.  Here is the `documentation
+<https://hacs-pyscript.readthedocs.io/en/1.5.0>`__ for that release.  Here is the
 `stable documentation <https://hacs-pyscript.readthedocs.io/en/stable>`__ for
 the latest release.
 
@@ -17,27 +17,6 @@ Over time, the master (head of tree) version in GitHub will include new features
 Here is the `latest documentation <https://hacs-pyscript.readthedocs.io/en/latest>`__ if you want
 to see the development version of the documentation.
 
-If you want to see development progress since 1.4.0, see
+If you want to see development progress since 1.5.0, see
 `new features <https://hacs-pyscript.readthedocs.io/en/latest/new_features.html>`__ in the latest
 documentation, or look at the `GitHub repository <https://github.com/custom-components/pyscript>`__.
-
-Planned new features post 1.4.0 include:
-
-- Services defined in pyscript should support entity methods if they include an ``entity_id`` keyword argument.
-- Consider supporting the built-in functions that do I/O, such as ``open``, ``read`` and ``write``, which
-  are not currently supported to avoid I/O in the main event loop, and also to avoid security issues if people
-  share pyscripts. The ``print`` function only logs a message, rather than implements the real ``print`` features,
-  such as specifying an output file handle. Support might be added in the future using an executor job, perhaps
-  enabled when ``allow_all_imports`` is set.
-
-The new features since 1.4.0 in master include:
-
-None yet.
-
-Breaking changes since 1.4.0 include:
-
-None yet.
-
-Bug fixes since 1.4.0 include:
-
-None yet.
diff --git a/info.md b/info.md
index e18146f..d6d66b5 100644
--- a/info.md
+++ b/info.md
@@ -2,18 +2,18 @@
 
 This is a custom component that adds rich Python scripting to Home Assistant.
 
-You can write Python functions and scripts that implement a wide range of automation, logic and
-triggers.  State variables are bound to Python variables and services are callable as Python
-functions, so it's easy and concise to implement high-level logic.
-
-Functions you write can be configured to be called as a service or run upon time, state-change or
-event triggers. Functions can also call any service, fire events and set state variables.
-Functions can sleep or wait for additional changes in state variables or events, without slowing or
-affecting other operations. You can think of these functions as small programs that run in
+You can write Python functions and scripts that implement a wide range of automation, logic
+and triggers.  State variables are bound to Python variables and services are callable as
+Python functions, so it's easy and concise to implement high-level logic.
+
+Functions you write can be configured to be called as a service or run upon time, state-change
+or event triggers. Functions can also call any service, fire events and set state variables.
+Functions can sleep or wait for additional changes in state variables or events, without slowing
+or affecting other operations. You can think of these functions as small programs that run in
 parallel, independently of each other, and they could be active for extended periods of time.
 
-Pyscript also interfaces with the Jupyter front-ends (eg, notebook, console and lab).  That allows
-you to develop and test pyscript functions, triggers, automation and logic interactively.
+Pyscript also interfaces with the Jupyter front-ends (eg, notebook, console, lab and VSCode).  That
+allows you to develop and test pyscript functions, triggers, automation and logic interactively.
 
 ## Installation