Skip to main content

continuum

Static change impact of the git checkout in the current directory, for Python and TypeScript/JavaScript. Continuum never runs tests; it tells you which to run.

pip install party-continuum        # or: brew install maitai-inc/continuum/continuum

continuum dependents src/app/billing.py::charge   # before editing: what uses it
continuum impact                                  # after editing: how far it reaches
continuum tests --explain                         # before pushing: which tests, and why

It compares the working tree with its merge-base with the default branch (--base <ref> / --head <commit> to choose). Every command takes --json. Suites and test commands can be pinned in a continuum.toml at the checkout root.

Requirements: Python 3.11+ and git. TypeScript also needs node and the repository's typescript package installed (npm ci), or CONTINUUM_TYPESCRIPT_DIR. No network access or credentials: everything is computed from the local checkout.

Metadata

Release files for party-continuum 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for party-continuum 0.1.0
File Size Uploaded
party_continuum-0.1.0.tar.gz 78.8 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for party-continuum 0.1.0
File Interpreter ABI Platform
party_continuum-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 166.8 kB

Release files / party_continuum-0.1.0.tar.gz

Download URL party_continuum-0.1.0.tar.gz
Size 78.8 kB
Tags Source
SHA-256 checksum
How to use checksums
0dbc4c32d4aa9106944dc2ab89e8d88887a8901f35e56989d26fcb5215e15694
BLAKE2b-256 checksum
How to use checksums
de4ea24675b27fe6979b95ab8c7b7a18572b1ab72461a1f802664b04706cc7b1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 28, 2026.

Transparency log

Release files / party_continuum-0.1.0-py3-none-any.whl

Download URL party_continuum-0.1.0-py3-none-any.whl
Size 87.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
6a610e4d5d269fcf3ac42067a814f139be89e303c16a217100356bfd4fadbefa
BLAKE2b-256 checksum
How to use checksums
9fd8703438f0ed845120f7d8c053e3e309752036b4f383211e6bb9b26e39b340
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 28, 2026.

Transparency log

Release history Release notifications | RSS feed

0.4.0

2 release files

0.3.0

2 release files

0.2.1

2 release files

0.2.0

2 release files

This release

0.1.0 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page