hypershell 2.6.6__tar.gz → 2.7.1__tar.gz

hypershell-2.7.1/.github/FUNDING.yml

@@ -0,0 +1,12 @@
+# These are supported funding model platforms
+
+github: glentner
+patreon: # Replace with a single Patreon username
+open_collective: # Replace with a single Open Collective username
+ko_fi: # Replace with a single Ko-fi username
+tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
+community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
+liberapay: # Replace with a single Liberapay username
+issuehunt: # Replace with a single IssueHunt username
+otechie: # Replace with a single Otechie username
+custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2']

hypershell-2.7.1/.github/workflows/publish.yml

@@ -0,0 +1,19 @@
+name: Publish
+on:
+  release:
+    types: [created]
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+          cache-dependency-glob: "uv.lock"
+
+      - name: Publish to PyPI
+        run: uv build && uv publish --token ${{ secrets.PYPI_TOKEN }}

hypershell-2.7.1/.github/workflows/tests.yml

@@ -0,0 +1,24 @@
+name: Tests
+on:
+  push:
+    branches: [ master, develop ]
+  pull_request:
+    branches: [ develop ]
+
+jobs:
+  tests:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: [ '3.9', '3.10', '3.11', '3.12', '3.13' ]
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+          cache-dependency-glob: "uv.lock"
+
+      - name: Run tests
+        run: uv run --python ${{ matrix.python-version }} pytest -v

hypershell-2.7.1/Apptainer

@@ -0,0 +1,38 @@
+Bootstrap: docker
+From: python:3.13-slim
+Stage: final
+
+%labels
+  Version="2.7.0"
+  Author="glentner@purdue.edu"
+
+%files
+  ./src            /app/src
+  ./uv.lock        /app/uv.lock
+  ./LICENSE        /app/LICENSE
+  ./README.rst     /app/README.rst
+  ./pyproject.toml /app/pyproject.toml
+
+%post
+  export DEBIAN_FRONTEND=noninteractive
+  apt-get -yqq update && apt-get -yqq upgrade
+  apt-get -yqq install curl build-essential postgresql libpq-dev
+  rm -rf /var/lib/apt/lists/*
+
+  curl -LsSf https://astral.sh/uv/install.sh | env UV_INSTALL_DIR="/bin" sh
+
+  export UV_LINK_MODE=hardlink
+  export UV_CACHE_DIR=/opt/uv-cache
+  export UV_COMPILE_BYTECODE=1
+  export UV_PROJECT_ENVIRONMENT=/opt/hypershell
+
+  cd /app
+  /bin/uv sync --frozen --all-packages --python 3.13
+  ln -sf /opt/hypershell/bin/hs /bin/hs
+
+%environment
+  export HYPERSHELL_LOGGING_LEVEL=TRACE
+  export HYPERSHELL_LOGGING_STYLE=SYSTEM
+
+%runscript
+  exec /bin/hs "$@"

hypershell-2.7.1/Dockerfile

@@ -0,0 +1,34 @@
+FROM python:3.13-slim
+COPY --from=ghcr.io/astral-sh/uv:latest /uv /uvx /bin/
+
+LABEL version="2.7.0"
+LABEL authors="glentner@purdue.edu"
+LABEL org.opencontainers.image.source="https://github.com/hypershell/hypershell"
+LABEL org.opencontainers.image.description="HyperShell Base Image"
+LABEL org.opencontainers.image.licenses="Apache-2.0"
+
+RUN DEBIAN_FRONTEND=noninteractive \
+    apt-get -yqq update && apt-get -yqq upgrade && \
+    apt-get -yqq install build-essential postgresql libpq-dev && \
+    rm -rf /var/lib/apt/lists/*
+
+RUN addgroup --gid 1001 --system hypershell && \
+    adduser --no-create-home --shell /bin/false --disabled-password --uid 1001 --system --group hypershell
+
+RUN mkdir -p /var/lib/hypershell /var/log/hypershell
+
+ENV UV_CACHE_DIR=/opt/uv-cache \
+    UV_LINK_MODE=hardlink \
+    UV_COMPILE_BYTECODE=1 \
+    UV_PROJECT_ENVIRONMENT=/opt/hypershell \
+    HYPERSHELL_LOGGING_LEVEL=TRACE \
+    HYPERSHELL_LOGGING_STYLE=SYSTEM
+
+WORKDIR /app
+COPY . .
+RUN /bin/rm -rf .venv .git
+RUN uv sync --frozen --all-packages --python 3.13
+
+USER hypershell
+ENTRYPOINT ["/opt/hypershell/bin/hs", "server"]
+CMD ["--forever"]

{hypershell-2.6.6 → hypershell-2.7.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: hypershell
-Version: 2.6.6
+Version: 2.7.1
 Summary: A cross-platform, high-throughput computing utility for processing shell commands over a distributed, asynchronous queue.
 Author-email: Geoffrey Lentner <glentner@purdue.edu>
 License-Expression: Apache-2.0
@@ -16,6 +16,7 @@ Classifier: Programming Language :: Python :: 3.10
 Classifier: Programming Language :: Python :: 3.11
 Classifier: Programming Language :: Python :: 3.12
 Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
 Classifier: Topic :: Utilities
 Requires-Python: >=3.9
 Requires-Dist: cmdkit[toml]>=2.7.7
@@ -26,6 +27,8 @@ Requires-Dist: sqlalchemy>=2.0.29
 Requires-Dist: tomlkit>=0.13.2
 Provides-Extra: postgres
 Requires-Dist: psycopg2>=2.9.9; extra == 'postgres'
+Provides-Extra: uuid7
+Requires-Dist: uuid-utils>=0.10.0; extra == 'uuid7'
 Description-Content-Type: text/x-rst
 
 HyperShell v2: Distributed Task Execution for HPC
@@ -39,6 +42,10 @@ HyperShell v2: Distributed Task Execution for HPC
     :target: https://github.com/hypershell/hypershell/releases
     :alt: Github Release
 
+.. image:: https://static.pepy.tech/badge/hypershell/month
+    :target: https://pypi.org/project/hypershell/
+    :alt: PyPI Monthly Downloads
+
 .. image:: https://img.shields.io/badge/Python-3.9+-blue.svg
     :target: https://www.python.org/downloads
     :alt: Python Versions

{hypershell-2.6.6 → hypershell-2.7.1}/README.rst

@@ -9,6 +9,10 @@ HyperShell v2: Distributed Task Execution for HPC
     :target: https://github.com/hypershell/hypershell/releases
     :alt: Github Release
 
+.. image:: https://static.pepy.tech/badge/hypershell/month
+    :target: https://pypi.org/project/hypershell/
+    :alt: PyPI Monthly Downloads
+
 .. image:: https://img.shields.io/badge/Python-3.9+-blue.svg
     :target: https://www.python.org/downloads
     :alt: Python Versions

{hypershell-2.6.6 → hypershell-2.7.1}/docs/_include/cluster_desc.rst

@@ -13,3 +13,5 @@ left off.
 
 Use ``--autoscaling`` with either *fixed* or *dynamic* to run a persistent, elastically scalable
 cluster using an external ``--launcher`` to bring up clients as needed.
+
+Use ``hsx`` in place of ``hs cluster``.

{hypershell-2.6.6 → hypershell-2.7.1}/docs/_include/config_param_ref.rst

@@ -87,6 +87,10 @@
         Specify additional connection details for the underlying SQL dialect provider,
         e.g., ``sqlite3`` or ``psycopg2``.
 
+    ``[pragmas]``
+        Specify one or more pragmas to apply to database connections (SQLite only).
+        For example ``pragmas = { journal_mode = "wal" }`` to enable WAL-mode.
+
     ``*``
         Any additional arguments are forwarded to the provider, e.g., ``encoding = 'utf-8'``.
 

hypershell-2.7.1/docs/_include/initdb_desc.rst

@@ -0,0 +1,8 @@
+Initialize database.
+
+For SQLite this happens automatically.
+See also ``--initdb`` for the ``hs cluster`` command.
+
+The available special actions are mutually exclusive.
+The ``--rotate`` operation migrates completed tasks to the next database partition,
+and applies a special purpose ``part:N`` tag to the new partition and remaining tasks.

hypershell-2.7.1/docs/_include/initdb_help.rst

@@ -0,0 +1,20 @@
+Actions
+^^^^^^^
+
+``--vacuum``
+    Vacuum an existing database.
+
+``--backup`` *PATH*
+    Vacuum into backup file (SQLite only).
+
+``--rotate``
+    Rotate completed tasks to new database (SQLite only).
+
+``-t``, ``--truncate``
+    Truncate database (task metadata will be lost).
+
+Options
+^^^^^^^
+
+``-y``, ``--yes``
+    Auto-confirm action (default will prompt).

hypershell-2.7.1/docs/_include/initdb_usage.rst

@@ -0,0 +1 @@
+``hs`` ``initdb`` ``[-h]`` ``[--truncate | --vacuum | --rotate | --backup PATH]`` ``[--yes]``

hypershell-2.7.1/docs/_include/submit_desc.rst

@@ -0,0 +1,16 @@
+Submit one or more tasks.
+
+Submit one task as positional arguments.
+If a single positional argument refers to a non-executable file path,
+tasks will be read from the file, one per line (use ``-f``/``--task-file`` to be explicit).
+
+Tasks are accumulated and published in bundles to the database.
+The ``-b``/``--bundlesize`` and ``-w``/``--bundlewait`` options control the
+size of these bundles and how long to wait before flushing tasks regardless of
+how many have accumulated.
+
+Pre-format tasks at `submit`-time with template expansion using ``--template``.
+Any tags specified with ``-t``/``--tag`` are applied to all tasks submitted.
+
+Use the special comment syntax, ``# HYPERSHELL: ...``, to include tags inline.
+If the comment is alone on the line it will be applied to all tasks that follow.

{hypershell-2.6.6 → hypershell-2.7.1}/docs/_include/submit_help.rst

@@ -1,20 +1,23 @@
 Arguments
 ^^^^^^^^^
 
-FILE
-    Path to input task file (default: <stdin>).
+*ARGS*...
+    Command-line task arguments (for single task submission).
 
 Options
 ^^^^^^^
 
-``-t``, ``--template`` *CMD*
+``-f``, ``--task-file`` *FILE*
+    Input file containing one task per line.
+
+``--template`` *CMD*
     Command-line template pattern (default: "{}").
 
     This is expanded at submit-time before sending to the database.
     With the default "{}" the input command-line will be run verbatim.
     Specifying a template pattern allows for simple input arguments (e.g., file paths)
     to be transformed into some common form; such as
-    ``-t './some_command.py {} >outputs/{/-}.out'``.
+    ``--template './some_command.py {} >outputs/{/-}.out'``.
 
     See section on `templates`.
 
@@ -44,7 +47,7 @@ Options
 
     See ``hs initdb`` command.
 
-``--tag`` *TAG*...
+``-t``, ``--tag`` *TAG*...
     Assign one or more tags.
 
     Tags allow for user-defined tracking of information related to individual tasks or large

hypershell-2.7.1/docs/_include/submit_usage.rst

@@ -0,0 +1,2 @@
+``hs`` ``submit`` ``[-h]`` ``[ARGS... | -f FILE]``
+    ``[-b NUM]`` ``[-w SEC]`` ``[--template CMD]`` ``[-t TAG...]`` ``[--initdb]``

{hypershell-2.6.6 → hypershell-2.7.1}/docs/_include/task_info_usage.rst

@@ -1,2 +1,2 @@
-``hs`` ``task`` ``info`` ``[-h]``
+``hs`` ``info`` ``[-h]``
     ``ID`` ``[--stdout | --stderr | -x FIELD]`` ``[-f FORMAT]``

{hypershell-2.6.6 → hypershell-2.7.1}/docs/_include/task_run_desc.rst

@@ -4,4 +4,4 @@ A database must be configured. The task will not run until scheduled
 by the server process. The <stdout> and <stderr> are written locally
 as if run locally, requires the client to have ``--capture`` enabled.
 
-See ``task info`` and ``task wait`` commands.
+See ``info`` and ``wait`` commands.

{hypershell-2.6.6 → hypershell-2.7.1}/docs/_include/task_run_help.rst

@@ -1,7 +1,7 @@
 Arguments
 ^^^^^^^^^
 
-ARGS...
+*ARGS*...
     Command-line arguments.
 
     The full command-line for some shell task.

hypershell-2.7.1/docs/_include/task_run_usage.rst

@@ -0,0 +1 @@
+``hs`` ``run`` ``[-h]`` ``[-n SEC]`` ``[-t TAG [TAG...]]`` ``--`` ``ARGS...``

{hypershell-2.6.6 → hypershell-2.7.1}/docs/_include/task_search_desc.rst

@@ -1,4 +1,4 @@
-Search for tasks in database.
+Search tasks in the database.
 
 A database must be configured.
 Specifying *FIELD* names defines what is included in the output

{hypershell-2.6.6 → hypershell-2.7.1}/docs/_include/task_search_help.rst

@@ -60,3 +60,10 @@ Options
 
 ``-c``, ``--count``
     Show count of results.
+
+``-i``, ``--ignore-partitions``
+    Suppress auto-union feature (SQLite only).
+
+    When using the `sqlite` provider, all databases matching the numbering pattern
+    applied by ``hs initdb --rotate`` will automatically be attached as partitions
+    and used within a temporary view, making full task history searchable.

{hypershell-2.6.6 → hypershell-2.7.1}/docs/_include/task_search_usage.rst

@@ -1,5 +1,11 @@
-``hs`` ``task`` ``search`` ``[-h]``
+``hs`` ``list`` ``[-h]``
     ``[FIELD [FIELD ...]]`` ``[-w COND [COND ...]]`` ``[-t TAG [TAG...]]``
     ``[--order-by FIELD [--desc]]`` ``[--count | --limit NUM]``
     ``[-f FORMAT | --json | --csv]`` ``[-d CHAR]``
     ``[--failed | --succeeded | --completed | --remaining]``
+
+``hs`` ``list`` ``--fields``
+
+``hs`` ``list`` ``--tag-keys``
+
+``hs`` ``list`` ``--tag-values`` ``KEY``

{hypershell-2.6.6 → hypershell-2.7.1}/docs/_include/task_update_desc.rst

@@ -1,4 +1,4 @@
-Update task metadata.
+Update tasks in the database.
 
 Include any number of `FIELD=VALUE` or tag `KEY:VALUE` positional arguments.
 

{hypershell-2.6.6 → hypershell-2.7.1}/docs/_include/task_update_help.rst

@@ -1,7 +1,7 @@
 Arguments
 ^^^^^^^^^
 
-ARGS...
+*ARGS*...
     Assignment pairs for update.
 
 Options
@@ -86,5 +86,5 @@ FIELD
 VALUE
     New value.
 
-    Use ``key:value`` notation for tasks.
+    Use ``key:value`` notation for tags.
     Updating ``tag`` will add or update any pre-existing tag with that ``key``.

{hypershell-2.6.6 → hypershell-2.7.1}/docs/_include/task_update_usage.rst

@@ -1,6 +1,6 @@
-``hs`` ``task`` ``update`` ``[-h]`` ``ID`` ``FIELD`` ``VALUE``
+``hs`` ``update`` ``[-h]`` ``ID`` ``FIELD`` ``VALUE``
 
-``hs`` ``task`` ``update``
+``hs`` ``update``
     ``[ARG [ARG ...]]``
     ``[--cancel | --revert | --delete | --remove-tag KEY [KEY...]]``
     ``[-w COND [COND ...]]`` ``[-t TAG [TAG...]]``

{hypershell-2.6.6 → hypershell-2.7.1}/docs/_include/task_wait_usage.rst

@@ -1,2 +1,2 @@
-``hs`` ``task`` ``wait`` ``[-h]``
+``hs`` ``wait`` ``[-h]``
     ``ID`` ``[-n SEC]`` ``[--info [-f FORMAT] | --status | --return]``

{hypershell-2.6.6 → hypershell-2.7.1}/docs/api/data.rst

@@ -35,6 +35,14 @@ Functions
 
         This action is destructive, cannot be reversed, and proceeds without confirmation.
 
+|
+
+.. autofunction:: vacuumdb
+
+|
+
+.. autofunction:: rotatedb
+
 -------------------
 
 Constants
@@ -44,4 +52,6 @@ Constants
 
 .. autodata:: DATABASE_ENABLED
 
+.. autodata:: DATABASE_PROVIDER
+
 |

hypershell-2.7.1/docs/blog/20250504_2_7_0_release.rst

@@ -0,0 +1,228 @@
+.. _20250504_2_7_0_release:
+
+Release Notes (v2.7.0)
+======================
+
+`May 4, 2025`
+
+The v2.7.0 release includes major database features and CLI improvements.
+
+- Automatic database rotation for SQLite
+- Optional UUIDv7 mode
+- SQLite pragmas
+- SQLite optimization
+- Simplified command-line interface
+- Version info
+- Improved task submission (global tags)
+
+-----
+
+Features
+--------
+
+|
+
+Automatic database rotation for SQLite
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+When using `SQLite` as a backend for long persistent deployments the overall throughput
+can suffer due to the increased size of the database. What we would like is to keep our long task
+history while alleviating the burden of such a large database on task throughput. To accomplish
+this we've added two new admin routines, ``vacuumdb()`` and ``rotatedb()``, and exposed them via
+the command-line interface via ``hs initdb`` as ``--vacuum``, ``--backup``, and ``--rotate``.
+
+For those unfamiliar with the concept, `VACUUM` is a database operation (PostgreSQL and SQLite)
+that optimizes space and can improve performance in some cases. For SQLite, updated rows are
+written to new pages, even deleting data is only flagged as such. Performing a vacuum copies
+all active pages to a new database file and then replaces the original database file. This
+operation is safe to perform while under load. This on its own is a useful feature to have for
+long running deployments.
+
+For SQLite, the vacuum operation allows for a file path and instead of copying the new cleaned
+pages back to the original file the data is left at the given file path. This capability is what
+drives the ``--backup`` feature, and in turn enables the ``--rotate`` feature.
+
+With this release we now automatically add a ``part:0`` tag to all new tasks. This ``part``, short
+for *partition*, is used to label all completed tasks in the activate database with ``part:N`` in
+a single transaction, where *N* is the N-th partition chosen based on the path to the file. With
+this tag as a means to safely distinguish between the completed tasks in that moment, we can
+partition the activate database using a vacuum operation to a new location, essentially cloning
+the database. Afterwards, we drop any non-``part:N`` tasks from the new clone and any ``part:N``
+from the activate database. This can happen in real time without stopping the server.
+
+Immediately following one of these partition events, there will be few tasks in the activate database.
+While searching task history we want to allow for the full history without losing access because we
+split the database. Now, when invoking task search, if SQLite is in use, we automatically check for
+any/all existing partitions of the same database path and `attach` each to the session. We build a
+temporary `view` that replaces the ``task`` table with a series of ``union all`` on these partitions.
+Any and all queries are applied to this temporary view as if the entire history existed within the
+one table.
+
+.. note::
+
+    With most distributions of Python the `sqlite3` library is built with a compile-time option
+    ``SQLITE_MAX_ATTACHED=10`` by default. While ``--rotate`` can be called any number of times,
+    the automatic attachment of these partitions will be limited by this setting. While it's
+    possible to re-compile SQLite with a higher value, it cannot be increased above 125.
+
+    See `SQLite limits <https://www.sqlite.org/limits.html>`_.
+
+|
+
+Optional UUIDv7 Mode
+^^^^^^^^^^^^^^^^^^^^
+
+A new package extra, ``hypershell[uuid7]``, installs a third-party dependency,
+`uuid-utils <https://pypi.org/project/uuid-utils/>`_, which provides for
+lexicographically-sortable version 7 UUIDs. The format specification for UUID
+version 7 has essentially solidified and library support for use of this format is well supported
+and widely used.
+
+See `RFC 9562 (draft standard) <https://www.rfc-editor.org/rfc/rfc9562.html#name-uuid-version-7>`_
+for reference.
+
+In large-scale performance testing with HyperShell it is difficult to say precisely what the
+net benefit of UUIDv7 has been on overall task throughput. The increase in performance comes from
+less cache-misses in page loads due to the time ordering of task rows. It is likely the case that
+task bundles will consist of tasks submitted close in time to one another. Updating these tasks is
+more efficient when they reside within the same collection of pages, instead of being randomly
+distributed within the b-tree.
+
+Generation of UUIDs within the project has been refactored to an internal routine.
+This routine calls ``uuid.uuid4`` from the standard library and returns a string.
+If ``uuid-utils`` is available in the installation we prefer ``uuid_utils.uuid7``.
+This functionality install-time behavior and is not configurable at runtime.
+
+.. note::
+
+    On SQLite there is no real benefit to UUID v7.
+    SQLite employs a hidden ``rowid`` column when using a non-integer primary key.
+    The pages in the database are actually stored according to this hidden ``rowid``.
+    The overhead of the second lookup is minimal compared to the huge performance improvement
+    due to the page ordering.
+
+    In testing, adding the ``WITHOUT ROWID`` table modifier results in a significant reduction
+    in performance, and adding UUIDv7 on top of that entirely recovers this performance.
+    Incorporating both the table modifier and UUIDv7 is relatively insignificant.
+
+|
+
+SQLite Pragmas
+^^^^^^^^^^^^^^
+
+It has always been technically possible to enable WAL-mode for SQLite by connecting outside
+of HyperShell and applying the setting. But this is inelegant and doesn't help with settings
+that do not persist between connections. Now you can include a ``pragmas`` section in your
+configuration to automatically apply these to all database connections.
+
+The most useful change from the default behavior is to enable the Write-Ahead Log (WAL)
+``journal_mode`` for SQLite which can improve performance in high-concurrency applications.
+
+.. admonition:: Set user-level configuration option
+    :class: note
+
+    .. code-block:: shell
+
+        hs config set database.pragmas.journal_mode wal
+
+There are many other pragmas we might set.
+Not all configurations of SQLite have been tested for performance.
+
+.. admonition:: Configuration with SQLite pragmas
+    :class: note
+
+    .. code-block:: toml
+
+        [database]
+        file = "/var/lib/hypershell/main.db"
+        pragmas = {journal_mode = "wal", cache_size = 100000}
+
+|
+
+SQLite Optimization
+^^^^^^^^^^^^^^^^^^^
+
+On a related note, all ``vacuumdb()`` operations (used by ``--vacuum`` and ``--rotate``) add
+an automatic ``pragma optimize`` operation. This is mostly harmless and can be invoked safely
+on a regular basis.
+
+See `optimize <https://sqlite.org/pragma.html#pragma_optimize>`_ for details.
+
+|
+
+Simplified Command-line Interface
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+As with previous changes, backwards compatibility has been maintained for existing workflows.
+Hierarchy can be a good thing in command-line tools and is often necessary to manage complexity.
+For HyperShell though there is no naming-conflict of actions to justify the added ``task`` layer.
+The following subcommands have been remapped for simplicity and brevity:
+
+- ``hs task submit`` → ``hs submit`` *++*
+- ``hs task info`` → ``hs info``
+- ``hs task wait`` → ``hs wait``
+- ``hs task run`` → ``hs run``
+- ``hs task search`` → ``hs list``
+- ``hs task update`` → ``hs update``
+
+The exception here is ``hs submit`` and ``hs task submit`` which were distinct operations.
+The new ``hs submit`` provides both interfaces in a single command. Positional arguments are treated
+as a single command-line task. If a single positional argument is provided and it is either ``-``
+(stdin) or is a valid non-executable file path it will be read as before. This can be made explicit
+using the new ``-f``/``--task-file`` option.
+
+The new ``hs submit`` also includes better quoting behavior, properly forwarding arguments with
+quoted white space.
+
+A new entry-point, ``hsx``, is also included as shorthand for ``hs cluster``.
+
+|
+
+Version Info
+^^^^^^^^^^^^
+
+The output of ``hs --version`` now includes more detailed information.
+
+.. admonition:: Show version information
+    :class: note
+
+    .. code-block:: shell
+
+        hs --version
+
+    .. details:: Output
+
+        .. code-block:: none
+
+            HyperShell v2.7.0 (CPython 3.13.2)
+
+|
+
+Improved Task Submission
+^^^^^^^^^^^^^^^^^^^^^^^^
+
+In the :ref:`v2.6.0 release <20241115_2_6_0_release>` we added inline tag assignments.
+Any input line in a submission file which included a comment with the special ``# HYPERSHELL: ...``
+syntax allows for tags to be mapped to input arguments on an individual basis.
+
+In this release we extend this behavior to allow processing of non-task lines.
+If an input task line is empty or comment-only we skip that line and do not emit a task.
+If that comment contains the ``# HYPERSHELL: ...`` notation the tags will take effect on all
+future lines.
+
+The following example input file would be processed as 4 tasks.
+
+.. admonition:: Input task file with global tags
+    :class: note
+
+    .. code-block:: shell
+
+        # HYPERSHELL: site:b group:1
+
+        # HYPERSHELL: case:1
+        echo 1
+        echo 2
+
+        # HYPERSHELL: case:2
+        echo 3
+        echo 4