Skip to content

Releases

Gipper 0.6.0 — Serverless GPU queues

Choose a tag to compare

@lavallee lavallee released this 19 Nov 14:53

Gipper now runs Runpod Serverless queue jobs alongside its existing Pod/SSH runner. Deploy one reusable endpoint for successive jobs, or run a temporary endpoint with verified cleanup. The client remains standard-library only.

  • New gipper serverless commands for planning, deployment, submission, waiting, cancellation, inspection, deletion, and recovery of expired temporary endpoints.
  • A provider-neutral lifecycle with Runpod as the first adapter. Zero minimum workers, explicit worker and execution bounds, existing global/regional storage references, and append-only receipts.
  • Non-idempotent creates and submissions are never retried automatically. Cleanup requires matching ledger ownership and a real absence check.
  • A real CUDA worker example, development bootstrap without a local Docker builder, and a Dockerfile for installing worker dependencies during image build.

Validation includes 116 passing tests on Python 3.12–3.14, lint, package/archive checks, installed-wheel checks, and verified Artoo documentation. Live Runpod tests completed CUDA matrix multiplication, warm reuse, an intentional handler failure, and four real video-extraction requests. Every test endpoint was deleted and read back absent.

Warm extraction requests returned in about 6 seconds for an 8.5-second clip, 16 seconds for a one-minute clip, and 27 seconds for a repetitive four-minute graphics fixture. These exclude downstream model review. First requests included dependency installation and took roughly 119–263 seconds across two workers. The Dockerfile is authored but has not been built or benchmarked on the test host.

Runpod is the only implemented serverless host. Admission estimates are not provider-enforced spending caps. Serverless billing reconciliation, the Pod daily cap, automatic cross-host failover, and global-volume latency qualification are outside this release.

Serverless guide · CUDA example

gipper 0.5.0: Runpod REST v2

Choose a tag to compare

@lavallee lavallee released this 16 Nov 17:38

Runpod retired REST v1 on 2026-11-16, so every Runpod call from 0.4.3 and earlier fails. This release moves gipper's Runpod adapter to REST v2.

Changes

  • Prices and stock from /v2/catalog/gpus?include=AVAILABILITY&product=POD, per cloud and per country.
  • Pods, network volumes and bills from /v2/pods, /v2/network-volumes and /v2/billing/pods. Pod listing walks every page.
  • Job regions still hold: the pod is created in the data centers the catalog lists for those countries, and the offer is skipped when there are none.
  • The account line still uses GraphQL (no v2 route).

Validation

  • 90 unit tests, ruff, wheel and sdist checks pass.
  • Read paths (catalog, pod list, volumes, billing) were run against the live v2 API.
  • Not yet verified live: pod create and ssh readiness. These need a paid rental; the create body was checked against the v2 schema only.

Limitations

  • v2 reports no host machine id, so Runpod hosts are remembered by provider, not machine.
  • supportPublicIp has no v2 equivalent; a community host without a public IP ends as a bad host after the wait.
  • spend.billed details for Runpod are now gpu, cpu and disk dollars.

gipper 0.4.3

Choose a tag to compare

@lavallee lavallee released this 05 Nov 20:03

Fixed

  • Names that describe a secret rather than hold one no longer count from custody_secret_files. These are names ending in _PROFILE, _ID, _URL, _PATH, _FILE and similar.
  • For example, a plain-word SOMM_KEY_PROFILE would otherwise refuse any upload containing that word.

gipper 0.4.2

Choose a tag to compare

@lavallee lavallee released this 05 Nov 20:01

Fixed

  • custody_secret_files took every value in a file as a secret. A path or URL kept beside the credentials could then block an unrelated upload.
  • Only values whose names look secret count now, such as KEY, TOKEN, SECRET, PASSWORD and AUTH.
  • An entry can be { path = "...", names = [...] } to choose names exactly.
  • A missing file is reported instead of stopping every upload.

Validation

88 tests pass on Python 3.12–3.14.

gipper 0.4.1

Choose a tag to compare

@lavallee lavallee released this 05 Nov 17:22

Documentation and release-consistency patch. No runner, provider, placement, or custody behavior changes.

  • Remove the hardcoded version from the README status so the package-index description cannot lag behind the package version.
  • Refresh the PyPI README with verified uv tool install gipper and pip installation instructions.
  • Rebuild the landing page and all six guides with version 0.4.1 derived from package metadata.
  • Fail distribution validation when a numeric README status disagrees with the package version.

Validation: 87 tests, Ruff, wheel/sdist checks, Artoo build and static verification. The new README guard detects the previously published 0.3.0/0.4.0 mismatch. No paid rental was performed.

Documentation · Changelog · Changes

gipper 0.4.0

Choose a tag to compare

@lavallee lavallee released this 05 Nov 16:34

A forensic trail of what reached each rented machine. When a provider reports an incident, one command tells you what to rotate, what to review, and what the trail can't vouch for.

gipper custody report --provider runpod --since 2026-10-01 --check-providers

Changes

  • Every Remote.put records a manifest first. It lists exactly what tar will send, and a receipt is written before any byte moves. This covers jobs and client scripts alike.
  • Uploads are scanned. Provider keys and values from custody_secret_files are always refused. Other findings warn by default and can be set to refuse, with an allow list.
  • Remote.put_secrets places credentials with names and keyed fingerprints only.
  • gipper custody adds report, show, find, check and declare.

Limits

  • Commands run on a machine, and files a job downloads itself, aren't recorded.
  • Outputs brought back from a machine have no manifest yet.
  • Archives aren't opened, and files over 2 MB are hashed but not scanned.
  • Earlier rentals have no trail and show under Gaps.

See the custody guide.

Validation

87 tests pass on Python 3.12–3.14, using the real tar pipeline with a local shell standing in for ssh. Built artifacts pass check_dist, and the wheel installs cleanly. No rented machine has run this release yet, because a smoke run costs money and wasn't part of this work.

Published on PyPI. Install with uv tool install gipper or python -m pip install gipper in a virtual environment.

gipper 0.3.0

Choose a tag to compare

@lavallee lavallee released this 04 Nov 23:38

gipper runs shell-driven GPU jobs across cloud markets from a TOML file: estimate the whole job, rent and check a host, run, collect results, and verify teardown.

This first public release includes:

  • MIT licensing, a stdlib-only Python runtime, and portable CLI/Python interfaces.
  • Public installation and configuration guides, a security model, and a standalone project roadmap.
  • User-config dotenv support for packaged installs and cleanup services, preserving environment and explicit-file precedence.
  • Correct cost reports for spend receipts without a job ID.
  • GitHub Pages documentation, CI on Python 3.12–3.14, correctness linting, distribution checks, and a trusted PyPI publisher workflow.

Validation: 69 tests on Python 3.12, 3.13, and 3.14; Ruff; wheel/sdist contents and MIT metadata; fresh installed-wheel CLI/bootstrap; Artoo verification and desktop/mobile dark/light rendering. No paid rental was performed for this release.

Alpha software. Runpod and Vast.ai have prior live-run validation; Shadeform remains experimental. Client-side budgets and cleanup depend on provider APIs—review the security model.

Documentation · Changelog · Changes since the previous internal release

The wheel and source distribution are attached with SHA-256 checksums. Published on PyPI. Install this version with uv tool install gipper==0.3.0 or python -m pip install gipper==0.3.0 in a virtual environment.