glidepath 1.0.2__tar.gz → 1.1.0__tar.gz

{glidepath-1.0.2 → glidepath-1.1.0}/LICENSE-DATA

@@ -1,8 +1,8 @@
 Data licence notice
 ===================
 
-Everything in this repository is MIT-licensed (see LICENSE) EXCEPT the
-following bundled data file:
+Glidepath's own code is MIT-licensed (see LICENSE). The following bundled
+data file has a separate licence:
 
     src/glidepath/regions/uk/data/returns_history.toml
 
@@ -26,3 +26,6 @@ The MIT licence grant does not extend to that file. To obtain a
 distribution free of CC BY-NC-SA material, delete the file and
 regenerate a replacement from a source of your choosing with
 scripts/build_returns_history.py as a starting point.
+
+Third-party runtime licences and notices in third-party-licences/ retain
+their original terms; Glidepath's MIT licence does not replace them.

{glidepath-1.0.2 → glidepath-1.1.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: glidepath
-Version: 1.0.2
+Version: 1.1.0
 Summary: Desktop retirement and investment planner (UK-first, region-extensible).
 Keywords: retirement,pension,financial-planning,investment,uk,sipp,isa,monte-carlo
 Author: James Williams
@@ -132,7 +132,32 @@ based solely on this tool.
 
 ## Install
 
-Glidepath is installed from [PyPI](https://pypi.org/project/glidepath/)
+### Windows download
+
+From **v1.1.0**, Windows x64 users can run Glidepath without Python, uv
+or terminal commands:
+
+1. Open the [latest GitHub Release](https://github.com/williajm/glidepath/releases/latest).
+2. Under **Assets**, download `glidepath-X.Y.Z-windows-x64.exe`.
+3. Keep it in a folder of your choice and double-click it to launch.
+
+This is a runnable app, not an installer; it does not add shortcuts or
+update itself. For a newer version, close Glidepath and download the new
+executable. Your saved `.glidepath.json` plans stay where you put them.
+
+The executable is **not yet signed with a Windows publisher certificate**.
+Windows may show “Windows protected your PC” or “unrecognised app”. Check
+that the file came from this repository's release before deciding whether
+to proceed. GitHub build provenance does not remove that warning.
+If the latest release has no `.exe` yet, use the uv installation below.
+
+Runtime licences and attribution notices are included in the executable
+and in the release's `glidepath-X.Y.Z-third-party-licences.zip` download.
+That archive also lists the corresponding upstream sources.
+
+### Install with uv
+
+Alternatively, install Glidepath from [PyPI](https://pypi.org/project/glidepath/)
 with [uv](https://docs.astral.sh/uv/), which also fetches the Python it
 needs — you do not need Python installed first.
 
@@ -238,14 +263,24 @@ Releases are `vX.Y.Z` tags on `main`. Each one is published to
 trusted publishing with PEP 740 attestations, and as a GitHub Release
 carrying its notes from
 [`CHANGELOG.md`](https://github.com/williajm/glidepath/blob/main/CHANGELOG.md)
-with the same artifacts attached, each carrying signed build
+with the same Python artifacts and a tested Windows x64 executable attached,
+each carrying signed build
 provenance — verify a downloaded file with
 `gh attestation verify <file> -R williajm/glidepath`. The signed
 provenance bundle is attached to each release too
 (`glidepath-X.Y.Z-provenance.intoto.jsonl`), so verification also
-works offline with `--bundle`. There are no
-packaged binary builds (installer/exe) yet — install from PyPI as
-above.
+works offline with `--bundle`.
+
+From v1.1.0, the tag-triggered workflow also builds
+`glidepath-X.Y.Z-windows-x64.exe` with Nuitka. Download it from the
+GitHub Release and double-click to run; Python and uv are not required.
+The Windows build runs only for release tags, after tag validation, and
+must pass its compiled-app checks before publication. Ordinary branch
+pushes and PRs run the normal CI checks without compiling an executable.
+The executable is not yet Authenticode-signed, so Windows may show a
+SmartScreen warning; the build provenance above is a separate mechanism.
+See [`docs/packaging.md`](https://github.com/williajm/glidepath/blob/main/docs/packaging.md)
+for local builds and the release workflow.
 
 ## Data licences
 

{glidepath-1.0.2 → glidepath-1.1.0}/README.md

@@ -104,7 +104,32 @@ based solely on this tool.
 
 ## Install
 
-Glidepath is installed from [PyPI](https://pypi.org/project/glidepath/)
+### Windows download
+
+From **v1.1.0**, Windows x64 users can run Glidepath without Python, uv
+or terminal commands:
+
+1. Open the [latest GitHub Release](https://github.com/williajm/glidepath/releases/latest).
+2. Under **Assets**, download `glidepath-X.Y.Z-windows-x64.exe`.
+3. Keep it in a folder of your choice and double-click it to launch.
+
+This is a runnable app, not an installer; it does not add shortcuts or
+update itself. For a newer version, close Glidepath and download the new
+executable. Your saved `.glidepath.json` plans stay where you put them.
+
+The executable is **not yet signed with a Windows publisher certificate**.
+Windows may show “Windows protected your PC” or “unrecognised app”. Check
+that the file came from this repository's release before deciding whether
+to proceed. GitHub build provenance does not remove that warning.
+If the latest release has no `.exe` yet, use the uv installation below.
+
+Runtime licences and attribution notices are included in the executable
+and in the release's `glidepath-X.Y.Z-third-party-licences.zip` download.
+That archive also lists the corresponding upstream sources.
+
+### Install with uv
+
+Alternatively, install Glidepath from [PyPI](https://pypi.org/project/glidepath/)
 with [uv](https://docs.astral.sh/uv/), which also fetches the Python it
 needs — you do not need Python installed first.
 
@@ -210,14 +235,24 @@ Releases are `vX.Y.Z` tags on `main`. Each one is published to
 trusted publishing with PEP 740 attestations, and as a GitHub Release
 carrying its notes from
 [`CHANGELOG.md`](https://github.com/williajm/glidepath/blob/main/CHANGELOG.md)
-with the same artifacts attached, each carrying signed build
+with the same Python artifacts and a tested Windows x64 executable attached,
+each carrying signed build
 provenance — verify a downloaded file with
 `gh attestation verify <file> -R williajm/glidepath`. The signed
 provenance bundle is attached to each release too
 (`glidepath-X.Y.Z-provenance.intoto.jsonl`), so verification also
-works offline with `--bundle`. There are no
-packaged binary builds (installer/exe) yet — install from PyPI as
-above.
+works offline with `--bundle`.
+
+From v1.1.0, the tag-triggered workflow also builds
+`glidepath-X.Y.Z-windows-x64.exe` with Nuitka. Download it from the
+GitHub Release and double-click to run; Python and uv are not required.
+The Windows build runs only for release tags, after tag validation, and
+must pass its compiled-app checks before publication. Ordinary branch
+pushes and PRs run the normal CI checks without compiling an executable.
+The executable is not yet Authenticode-signed, so Windows may show a
+SmartScreen warning; the build provenance above is a separate mechanism.
+See [`docs/packaging.md`](https://github.com/williajm/glidepath/blob/main/docs/packaging.md)
+for local builds and the release workflow.
 
 ## Data licences
 

{glidepath-1.0.2 → glidepath-1.1.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "glidepath"
-version = "1.0.2"
+version = "1.1.0"
 description = "Desktop retirement and investment planner (UK-first, region-extensible)."
 readme = "README.md"
 # MIT code plus one CC BY-NC-SA 4.0 data file (returns_history.toml —
@@ -54,6 +54,12 @@ Issues = "https://github.com/williajm/glidepath/issues"
 glidepath = "glidepath.gui.main:main"
 
 [dependency-groups]
+binary = [
+    "nuitka>=4.2",
+    "setuptools>=84",
+    "wheel>=0.48",
+    "zstandard",
+]
 dev = [
     "hypothesis",
     "mypy",
@@ -70,11 +76,36 @@ dev = [
 requires = ["uv_build>=0.11,<0.13"]
 build-backend = "uv_build"
 
+# Shared by the local build command and the tagged release workflow.
+[tool.glidepath.binary]
+windows-icon = "src/glidepath/gui/assets/glidepath.ico"
+# Dependency Walker 2.2.6000 (2006), required by Nuitka on Windows x64.
+# Build tool only: never included in the distributed application.
+dependency-walker-url = "https://dependencywalker.com/depends22_x64.zip"
+dependency-walker-sha256 = "35db68a613874a2e8c1422eb0ea7861f825fc71717d46dabf1f249ce9634b4f1"
+nuitka-options = [
+    "--update-check=never",
+    "--enable-plugin=pyside6",
+    "--include-qt-plugins=platforms,imageformats",
+    "--include-package-data=glidepath",
+    "--include-distribution-metadata=glidepath",
+    "--include-data-files=LICENSE=LICENSE",
+    "--include-data-files=LICENSE-DATA=LICENSE-DATA",
+    "--include-data-dir=third-party-licences=third-party-licences",
+    "--product-name=Glidepath",
+    "--file-description=Glidepath retirement planner",
+    "--company-name=James Williams",
+]
+
 # --- uv ---------------------------------------------------------------------
 [tool.uv]
 # Supply-chain cooldown: resolution ignores anything published to PyPI after
 # this timestamp (now minus 7 days). Updated ONLY by `make deps`.
-exclude-newer = "2026-08-19T15:28:17Z"
+exclude-newer = "2026-08-29T16:19:47Z"
+# Nuitka is source-only. uv installs its build requirements from the binary
+# group first, then builds it in that environment: the lockfile hashes, age
+# check and all-groups audit cover the exact setuptools/wheel versions used.
+no-build-isolation-package = ["nuitka"]
 
 # PyPI is the ONLY permitted index (supply-chain policy; see CLAUDE.md).
 [[tool.uv.index]]