diff --git a/custom_components/pyscript/manifest.json b/custom_components/pyscript/manifest.json index 4125574..8a13484 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==2.0.2", "watchdog==2.3.1"], "ssdp": [], - "version": "1.5.0", + "version": "1.6.0", "zeroconf": [] } diff --git a/docs/conf.py b/docs/conf.py index 56a2a63..49e8cd4 100644 --- a/docs/conf.py +++ b/docs/conf.py @@ -19,11 +19,11 @@ # -- Project information ----------------------------------------------------- project = 'hacs-pyscript' -copyright = '2020-2023, Craig Barratt' +copyright = '2020-2024, Craig Barratt' author = 'Craig Barratt' # The full version, including alpha/beta/rc tags -release = '1.5.0' +release = '1.6.0' master_doc = 'index' diff --git a/docs/new_features.rst b/docs/new_features.rst index f7538a1..605ac09 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.5.0, released on July 30, 2023. Here is the `documentation -`__ for that release. Here is the +This is 1.6.0, released on July 26, 2024. Here is the `documentation +`__ for that release. Here is the `stable documentation `__ 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 `__ if you want to see the development version of the documentation. -If you want to see development progress since 1.5.0, see +If you want to see development progress since 1.6.0, see `new features `__ in the latest documentation, or look at the `GitHub repository `__. - -Planned new features post 1.5.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.5.0 in master include: - -None yet. - -Breaking changes since 1.5.0 include: - -None yet. - -Bug fixes since 1.5.0 include: - -None yet.