updates for 1.6.1 release

custom_components/pyscript/manifest.json

@@ -12,6 +12,6 @@
   "issue_tracker": "https://github.com/custom-components/pyscript/issues",
   "requirements": ["croniter==2.0.2", "watchdog==2.3.1"],
   "ssdp": [],
-  "version": "1.6.0",
+  "version": "1.6.1",
   "zeroconf": []
 }

docs/conf.py

@@ -23,7 +23,7 @@
 author = 'Craig Barratt'
 
 # The full version, including alpha/beta/rc tags
-release = '1.6.0'
+release = '1.6.1'
 
 master_doc = 'index'
 

docs/new_features.rst

@@ -8,36 +8,15 @@ 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.6.0, released on July 26, 2024.  Here is the `documentation
-<https://hacs-pyscript.readthedocs.io/en/1.6.0>`__ for that release.  Here is the
+This is 1.6.1, released on July 27, 2024.  Here is the `documentation
+<https://hacs-pyscript.readthedocs.io/en/1.6.1>`__ for that release.  Here is the
 `stable documentation <https://hacs-pyscript.readthedocs.io/en/stable>`__ for
 the latest release.
 
 Over time, the master (head of tree) version in GitHub will include new features and bug fixes.
 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.6.0, see
+If you want to see development progress since 1.6.1, 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.6.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.6.0 in master include:
-
-None yet.
-
-Breaking changes since 1.6.0 include:
-
-None yet.
-
-Bug fixes since 1.6.0 include:
-
-None yet.