Skip to content

Datakrit 2.1.1

Choose a tag to compare

@JudikaM JudikaM released this 05 Nov 12:55
· 11 commits to main since this release
35c0277

Datakrit 2.1.1

Two easier ways to install Datakrit: pip install datakrit from PyPI, and on Windows an app
that needs no Python (Datakrit-2.1.1-windows-x64.zip, below). This is the first release
with both. The tag v2.1.0 was prepared first but never published (its Windows app's
checksum file ended in CRLF, which GNU coreutils 8 and macOS shasum cannot check), so 2.1.1
carries all of its changes and the fix. Commands, options, profiles, reports, and the Python
API are unchanged.

Added

  • PyPI. Datakrit is published as datakrit. The
    files there are the wheel and sdist of this release, with the same SHA-256. GitHub Actions
    uploads them through PyPI Trusted Publishing, so no upload token or password exists; before
    uploading, the workflow checks each file against the digest that GitHub publishes, runs
    twine check --strict, and checks that the version is the tag's.
  • Windows app. Download Datakrit-2.1.1-windows-x64.zip, check it (below), unzip it, and
    double-click Datakrit\Datakrit.exe: the local interface starts and opens in the browser,
    with no Python, no terminal, and no console window. It behaves like datakrit-ui and has
    no command line; for the datakrit command and the Python API, install from PyPI. Inside
    the app, update reports the new release and its zip instead of running pip, and
    shortcuts are not offered. The folder Datakrit\licenses holds the license notices of
    Datakrit and of what the app bundles (Python, tomli-w, and the Microsoft runtime files).
    The app is built by GitHub Actions from the tag and smoke-tested before it is attached.
  • NOTICE.md with the license notices of the interface's icons (Lucide, ISC; icons derived
    from Feather, MIT), included in the wheel and the sdist.
  • A smoke mode for datakrit-ui and the app, for automated checks (the environment variable
    DATAKRIT_UI_URL_FILE).

Changed

  • Package metadata: Development Status :: 5 - Production/Stable, and the local interface in
    the description. Every link and image in the README is absolute, so the PyPI page works.
  • CI runs twine check --strict, builds and smoke-tests the app on every pull request, and
    audits the app's build tools (PyInstaller, pinned with hashes) with the other dependencies.

Fixed

  • The Windows app's checksum file is one line that ends in LF, so sha256sum --check and
    shasum -a 256 --check accept it on every system.

Upgrade notes

  • Profile, CLI, report, and Python API compatibility: unchanged. Nothing changes for
    profiles, CLI, reports, or the Python API.
  • Existing installs: datakrit update (or the Update Datakrit entry), or
    python -m pip install --upgrade datakrit. Windows users without Python: replace the old
    Datakrit folder with the one from the new zip.

Files (SHA-256)

  • datakrit-2.1.1-py3-none-any.whl: 818102b64f28adc0381df2af5b6da563f9ac6927a929c0658fcf3e55ca4e8e4d
  • datakrit-2.1.1.tar.gz: 06e584babdc4a496e98ba46bf95d1b0de3c1f464c214777032bfb12da352486f
  • Datakrit-2.1.1-windows-x64.zip: e3201ed8b793bfa1ddb9a86a371ffea531951ec7d37175fd4af201011d55d666

Check the app before you run it: in PowerShell, Get-FileHash .\Datakrit-2.1.1-windows-x64.zip -Algorithm SHA256
must print the hash above (on Linux or macOS, sha256sum --check Datakrit-2.1.1-windows-x64.zip.sha256).
The app is not code-signed, so Windows SmartScreen may warn the first time: choose More
info
, then Run anyway, only for a file from this page whose hash matches.

Verification

  • CI on the tagged commit (35c0277): CI,
    CodeQL,
    Dependency audit, all green.
  • Windows app built from the tag: run.
  • Smoke tests: the wheel installed in a fresh environment on Windows (Python 3.13); the
    downloaded zip checked against its SHA-256, its .sha256 file (sha256sum and shasum),
    and its license notices, then started in smoke mode (page and files served with the
    session key, refused without it, Quit ends the app with exit code 0).
  • Not verified: a double-click on a clean Windows computer, how SmartScreen reacts to the
    unsigned app, and how antivirus programs react to it.