ripple-effect 0.0.1__tar.gz

ripple_effect-0.0.1/.github/workflows/release.yml

@@ -0,0 +1,27 @@
+name: Release
+
+on:
+  push:
+    tags:
+      - 'v[0-9]*'
+
+jobs:
+  publish:
+
+    runs-on: ubuntu-latest
+    environment: release
+    permissions:
+      id-token: write  # mandatory for trusted publishing
+      contents: read
+
+    steps:
+    - uses: actions/checkout@v6
+    - uses: actions/setup-python@v6
+      with:
+        python-version: "3.14"
+
+    - uses: astral-sh/setup-uv@v7
+    - run: uvx --with tox-uv tox -e py,style,typecheck
+    - run: uv build
+    - name: Publish to PyPI
+      uses: pypa/gh-action-pypi-publish@release/v1

ripple_effect-0.0.1/.github/workflows/tests.yml

@@ -0,0 +1,38 @@
+name: Tests
+
+on:
+  push:
+    branches: [ main ]
+  pull_request:
+    branches: [ main ]
+
+jobs:
+  test:
+
+    runs-on: ubuntu-latest
+
+    strategy:
+      matrix:
+        python-version: ["3.10", "3.14"]
+
+    steps:
+    - uses: actions/checkout@v6
+    - uses: actions/setup-python@v6
+      with:
+        python-version: ${{ matrix.python-version }}
+
+    - uses: astral-sh/setup-uv@v7
+    - run: uvx --with tox-uv tox -e py
+
+  linters:
+
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v6
+    - uses: actions/setup-python@v6
+      with:
+        python-version: "3.14"
+
+    - uses: astral-sh/setup-uv@v7
+    - run: uvx --with tox-uv tox -e style,typecheck,readme

ripple_effect-0.0.1/.gitignore

@@ -0,0 +1,18 @@
+# Various
+*~
+\#*#
+.\#*
+.*cache
+*.lock
+.DS_Store*
+.*version
+.idea/
+
+# Build artifacts
+__pycache__/
+*.py[cod]
+*.egg*
+.tox/
+.venv*/
+build/
+dist/

ripple_effect-0.0.1/DEVELOP.md

@@ -0,0 +1,38 @@
+## Commands
+
+```bash
+# Run all tests + coverage report + linters
+tox
+
+# Run a single test by name
+.venv/bin/pytest -k test_help
+
+# Run ruff linter (check only)
+tox -e style
+
+# Auto-fix linting/formatting with ruff
+tox -e reformat
+
+# Run type checking
+tox -e typecheck
+```
+
+## Architecture
+
+**`src/ripple_effect/cli.py`** — click CLI entry point. Accepts a YAML config file and
+top-level flags (`--dryrun`, `--verbose`).
+
+**Config format** (YAML):
+
+```yaml
+location: /tmp/ripple-workspace   # where to clone/cache downstream repos
+projects:
+  - git+https://github.com/org/project.git@main   # remote ref
+  - ~/dev/local-project                           # local folder
+```
+
+For each project ripple-effect will:
+1. Clone (or `git fetch --reset`) the repo into `location/<name>/`
+2. Create a venv, install the project + the library under test in editable mode via `uv`
+3. Run `pytest tests/` against that venv
+4. Collect and report pass/fail per project

ripple_effect-0.0.1/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Zoran Simic
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

ripple_effect-0.0.1/PKG-INFO

@@ -0,0 +1,76 @@
+Metadata-Version: 2.4
+Name: ripple-effect
+Version: 0.0.1
+Summary: Know your blast radius before you push
+Author-email: Zoran Simic <zoran@simicweb.com>
+License-Expression: MIT
+Project-URL: Source, https://github.com/zsimic/ripple-effect
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+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 :: Software Development :: Testing
+Classifier: Topic :: Utilities
+Requires-Python: >=3.10
+Description-Content-Type: text/x-rst
+License-File: LICENSE
+Requires-Dist: click
+Requires-Dist: PyYAML
+Requires-Dist: runez
+Dynamic: license-file
+
+ripple-effect
+=============
+
+Know your blast radius before you push.
+
+Test a Python library against the downstream projects that depend on it —
+before you tag a release and find out the hard way.
+
+Installation
+------------
+
+.. code-block:: bash
+
+    uvx ripple-effect config.yml
+
+Usage
+-----
+
+Create a YAML config describing your library and the downstream projects to test against:
+
+.. code-block:: yaml
+
+    proving-grounds: /tmp/ripple-effect-workspace
+    downstream-projects:
+      - git+https://github.com/example/project-b.git@main
+      - git+https://github.com/example/project-c.git@main
+
+Then run:
+
+.. code-block:: bash
+
+    ripple-effect config.yml
+
+ripple-effect will:
+
+1. Clone (or update) each downstream project into ``proving-grounds``
+2. Create a venv for each, with the downstream project + your library installed in editable mode
+3. Run each project's test suite
+4. Report which passed, which failed
+
+For local iteration (e.g. testing against a local checkout of a downstream project):
+
+.. code-block:: yaml
+
+    proving-grounds: ~/dev/my-ripple-workspace
+    downstream-projects:
+      - git+https://github.com/example/project-b.git@main
+      - ~/dev/project-c

ripple_effect-0.0.1/README.rst

@@ -0,0 +1,48 @@
+ripple-effect
+=============
+
+Know your blast radius before you push.
+
+Test a Python library against the downstream projects that depend on it —
+before you tag a release and find out the hard way.
+
+Installation
+------------
+
+.. code-block:: bash
+
+    uvx ripple-effect config.yml
+
+Usage
+-----
+
+Create a YAML config describing your library and the downstream projects to test against:
+
+.. code-block:: yaml
+
+    proving-grounds: /tmp/ripple-effect-workspace
+    downstream-projects:
+      - git+https://github.com/example/project-b.git@main
+      - git+https://github.com/example/project-c.git@main
+
+Then run:
+
+.. code-block:: bash
+
+    ripple-effect config.yml
+
+ripple-effect will:
+
+1. Clone (or update) each downstream project into ``proving-grounds``
+2. Create a venv for each, with the downstream project + your library installed in editable mode
+3. Run each project's test suite
+4. Report which passed, which failed
+
+For local iteration (e.g. testing against a local checkout of a downstream project):
+
+.. code-block:: yaml
+
+    proving-grounds: ~/dev/my-ripple-workspace
+    downstream-projects:
+      - git+https://github.com/example/project-b.git@main
+      - ~/dev/project-c

ripple_effect-0.0.1/SPEC.md

@@ -0,0 +1,236 @@
+# ripple-effect — Spec
+
+> Know your blast radius before you push.
+
+Test a Python library against its downstream dependent projects — before you tag a release and find out the hard way.
+
+---
+
+## Concept
+
+Given a library **A** and a set of downstream projects **B**, **C**, …, ripple-effect:
+
+1. Resolves and validates each project reference (library + downstream) via `uv-metadata`
+2. Clones/updates each downstream project into a local workspace (git URL) or uses it in place (local folder)
+3. Builds a venv for each project
+4. Injects library **A** in editable mode into that venv
+5. Runs the project's test suite
+6. Reports pass/fail per project
+
+The inject step is the point of the tool and is not configurable — it always runs
+`uv pip install -e <library>` after the venv is prepared.
+
+---
+
+## Invocation
+
+```bash
+uvx ripple-effect config.yml          # build venvs and run tests as described in config.yml
+ripple-effect config.yml              # same, if installed globally
+ripple-effect --dryrun config.yml     # show what would be done, without doing it
+ripple-effect --verbose config.yml    # show more output
+```
+
+---
+
+## Project references
+
+Only two forms are accepted — for both `upstream` and `downstream-projects` entries:
+
+| Form         | Example                                                          | Behaviour                                              |
+|--------------|------------------------------------------------------------------|--------------------------------------------------------|
+| Local folder | `.` or `~/github/runez` or `/path/to/project`                   | Used as-is, no git operations                          |
+| Git URL      | Any URL form accepted by `uv-metadata` (see below)              | Cloned/updated into `proving-grounds/<name>/`          |
+
+PyPI refs (`requests`, `requests<2`), wheels, and sdists are **not** accepted — ripple-effect
+needs a `tests/` folder to run against, which only local folders and git repos can provide.
+
+### Validation via `uv-metadata`
+
+Every project reference (`upstream` and each `downstream-projects` entry) is validated early via
+[`uv-metadata`](https://github.com/zsimic/uv-metadata):
+
+```bash
+uv-metadata <ref>              # full metadata as JSON
+uv-metadata <ref> --key name   # just the project name
+```
+
+ripple-effect passes the reference as-is to `uv-metadata` and uses the result:
+- If `uv-metadata` returns valid metadata — the reference is accepted, whatever form it took
+- If `uv-metadata` returns no valid metadata — fail early with a clear error
+
+`uv-metadata` accepts many URL forms (`https://`, `git+https://`, etc.) and normalises them
+internally. ripple-effect doesn't need to validate or rewrite URLs — it just hands them off.
+The `name` field from the metadata is used to name the workspace subfolder for git repos.
+
+---
+
+## Config format (YAML)
+
+```yaml
+# The upstream library under test. Accepts: local folder or git URL.
+# Default: current working directory (.).
+# Future: upstream-libs: [...] will allow multiple upstream libs in one run.
+upstream: .
+
+# Where to clone/cache downstream git repos.
+# May use ~ and env vars. Subfolders are named after each project's name (from uv-metadata).
+proving-grounds: /tmp/ripple-proving-grounds
+
+# Optional global defaults, overridable per project.
+defaults:
+  # How to build the venv. Default: auto-detected (see Three-step model below).
+  prepare: auto
+  # How to run the tests.
+  test: ".venv/bin/pytest tests/"
+
+downstream-projects:
+  # Git URL (any form accepted by uv-metadata) — cloned/updated into proving-grounds/<name>/
+  - https://github.com/codrsquad/portable-python.git@main
+  - git+https://github.com/codrsquad/pickley.git@main
+
+  # Local folder — used as-is, no git operations
+  - ~/dev/my-other-project
+
+  # Per-project overrides (mapping form)
+  - url: https://github.com/org/project.git@main
+    prepare: "hatch env create"         # project uses hatch instead of uv
+    test: ".venv/bin/pytest tests/ -x"  # stop on first failure
+```
+
+### Project entry forms
+
+A project entry can be a plain string (shorthand) or a mapping with explicit keys:
+
+| Key       | Description                                                                 |
+|-----------|-----------------------------------------------------------------------------|
+| `url`     | Any URL form accepted by `uv-metadata` — cloned/updated into `proving-grounds/<name>/` |
+| `folder`  | Local path — used as-is, no git operations                                  |
+| `prepare` | Override the global `defaults.prepare` for this project                     |
+| `test`    | Override the global `defaults.test` for this project                        |
+
+Plain string entries are tried against `uv-metadata` first; if that succeeds and the ref
+is not a local path, it is treated as a `url`. Local paths (`.`, `~`, `/`, or existing
+directories) are treated as `folder` without calling out to `uv-metadata`.
+
+---
+
+## Three-step execution model
+
+For each downstream project, ripple-effect runs three steps in order:
+
+```
+prepare  →  inject  →  test
+```
+
+### Step 1 — prepare
+
+Builds the `.venv/` for the downstream project. Configurable via `defaults.prepare` or
+per-project `prepare`. When set to `auto` (the default), ripple-effect detects:
+
+| Condition                  | Command                                                        |
+|----------------------------|----------------------------------------------------------------|
+| `uv.lock` present          | `uv sync`                                                      |
+| `requirements.txt` present | `uv venv && uv pip install -r requirements.txt`                |
+| neither                    | error — explicit `prepare` required                            |
+
+Any string is accepted as the prepare command; ripple-effect just runs it and moves on.
+This accommodates projects using other venv managers (e.g. `hatch env create`, `poetry install`,
+`pipenv install`) without ripple-effect needing to know about them.
+
+### Step 2 — inject (not configurable)
+
+```bash
+uv pip install -e <upstream>
+```
+
+Injects the upstream library in editable mode into the venv built in step 1, overriding
+whatever version was installed (pinned or otherwise).
+
+**Special case — upstream is a local folder:**
+Before running inject, ripple-effect checks `uv pip freeze` in the project's venv. If the
+upstream is already installed in editable mode pointing at the right folder, inject is
+skipped and the venv is reused as-is. If it is pinned/wrong, the venv is recreated from
+scratch (prepare re-runs) then inject proceeds.
+
+**Upstream identified by name:** `uv-metadata <upstream> --key name` gives the package name
+used to find it in `uv pip freeze` output.
+
+### Step 3 — test
+
+Runs the project's test suite against the prepared+injected venv. Configurable via
+`defaults.test` or per-project `test`.
+
+Default: `.venv/bin/pytest tests/`
+
+---
+
+## Known limitation: tox
+
+**tox is intentionally out of scope for v1.**
+
+When tox runs, it creates its own isolated envs from scratch — the `.venv/` that
+ripple-effect prepared and injected into is invisible to tox's envs. There is no clean
+universal way to inject an editable library into tox environments without file surgery
+(editing `requirements.txt`, `pyproject.toml`, or similar).
+
+Workaround for power users: write a thin wrapper script that performs the injection
+before calling tox, then point `test:` at that script. ripple-effect doesn't need to
+know it's there.
+
+A future version could add first-class tox support with explicit strategies
+(e.g. `requirements.txt` surgery + restore, or `[tool.uv.sources]` injection + restore).
+
+---
+
+## CI usage example (GitHub Actions)
+
+```yaml
+- name: Run downstream integration tests
+  run: uvx ripple-effect ci-config.yml
+```
+
+With a `ci-config.yml`:
+
+```yaml
+upstream: .
+proving-grounds: $RUNNER_TEMP/ripple-workspace
+downstream-projects:
+  - https://github.com/codrsquad/portable-python.git@main
+  - https://github.com/codrsquad/pickley.git@main
+```
+
+---
+
+## Local iteration example
+
+```yaml
+upstream: ~/github/runez
+proving-grounds: ~/dev/ripple-workspace
+
+downstream-projects:
+  - https://github.com/codrsquad/portable-python.git@main
+  - ~/github/pickley        # local checkout, no git pull
+  - folder: ~/github/some-hatch-project
+    prepare: "hatch env create"   # project uses hatch rather than uv
+```
+
+---
+
+## v1 scope
+
+- [ ] Config parsing (YAML)
+- [ ] Project reference validation via `uv-metadata` (fail early on invalid refs)
+- [ ] Project cloning/updating (`git clone` / `git fetch --reset`) for git URLs
+- [ ] Auto-detection of prepare strategy (`uv.lock` vs `requirements.txt`)
+- [ ] Editable-install check (`uv pip freeze`) before deciding to recreate venv
+- [ ] `uv pip install -e <upstream>` injection
+- [ ] Test runner (`.venv/bin/pytest tests/`)
+- [ ] Per-project `prepare` / `test` overrides
+- [ ] `--dryrun` mode
+- [ ] Pass/fail summary report
+
+Out of scope for v1:
+- tox support
+- Parallel project execution
+- Caching venvs across runs

ripple_effect-0.0.1/pyproject.toml

@@ -0,0 +1,169 @@
+[build-system]
+requires = ["setuptools", "setuptools-scm"]
+build-backend = "setuptools.build_meta"
+
+[tool.setuptools_scm]
+local_scheme = "dirty-tag"
+
+[project]
+name = "ripple-effect"
+dynamic = ["version"]
+description = "Know your blast radius before you push"
+readme = "README.rst"
+requires-python = ">=3.10"
+license = "MIT"
+license-files = ["LICENSE"]
+authors = [
+    {name = "Zoran Simic", email = "zoran@simicweb.com"},
+]
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Environment :: Console",
+    "Intended Audience :: Developers",
+    "Operating System :: OS Independent",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3 :: Only",
+    "Programming Language :: Python :: 3.10",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Programming Language :: Python :: 3.14",
+    "Topic :: Software Development :: Testing",
+    "Topic :: Utilities",
+]
+dependencies = [
+    "click",
+    "PyYAML",
+    "runez",
+]
+
+[dependency-groups]
+test = [
+    "pytest-cov",
+]
+dev = [
+    { include-group = "test" },
+]
+
+[project.scripts]
+ripple-effect = "ripple_effect:main"
+
+[project.urls]
+Source = "https://github.com/zsimic/ripple-effect"
+
+
+[tool.coverage.run]
+data_file = ".tox/.coverage"
+source = ["src"]
+patch = ["subprocess"]
+sigterm = true
+
+[tool.coverage.xml]
+output = ".tox/test-reports/coverage.xml"
+
+[tool.coverage.html]
+directory = ".tox/test-reports/htmlcov"
+
+[tool.pytest]
+cache_dir = ".tox/pytest_cache"
+testpaths = ["tests"]
+
+[tool.ruff]
+cache-dir = ".tox/.ruff_cache"
+line-length = 140
+
+[tool.ruff.lint]
+extend-select = [
+    "A",   # flake8-builtins
+    "B",   # flake8-bugbear
+    "C4",  # flake8-comprehensions
+    "C90", # mccabe
+    "DTZ", # flake8-datetimez
+    "E",   # pycodestyle errors
+    "ERA", # eradicate
+    "F",   # pyflakes
+    "FLY", # flynt
+    "G",   # flake8-logging-format
+    "I",   # isort
+    "INT", # flake8-gettext
+    "PGH", # pygrep-hooks
+    "PIE", # flake8-pie
+    "PT",  # flake8-pytest
+    "PYI", # flake8-pyi
+    "Q",   # flake8-quotes
+    "RSE", # flake8-raise
+    "RUF", # ruff-specific
+    "S",   # flake8-bandit
+    "SIM", # flake8-simplify
+    "SLOT", # flake8-slots
+    "T10", # flake8-debugger
+    "TID", # flake8-tidy-imports
+    "TCH", # flake8-type-checking
+    "TD",  # flake8-todos
+    "W",   # pycodestyle warnings
+]
+[tool.ruff.lint.per-file-ignores]
+"tests/**" = ["S101"]
+
+[tool.ruff.lint.isort]
+order-by-type = false
+
+[tool.ruff.lint.mccabe]
+max-complexity = 19
+
+[tool.ruff.lint.pydocstyle]
+convention = "numpy"
+
+[tool.tox]
+env_list = ["py310", "py314", "coverage", "style", "typecheck", "readme"]
+
+[tool.tox.env_run_base]
+use_develop = true
+dependency_groups = ["test"]
+commands = [
+    ["pytest", "-vv", "--cov=src/ripple_effect", "tests"]
+]
+
+[tool.tox.env_run_base.set_env]
+COVERAGE_FILE = "{toxworkdir}/.coverage.{envname}"
+PYTHONDONTWRITEBYTECODE = "1"
+
+[tool.tox.env.coverage]
+skip_install = true
+deps = ["coverage"]
+set_env = { COVERAGE_FILE = "{toxworkdir}/.coverage" }
+commands = [
+    ["coverage", "combine"],
+    ["coverage", "report", "-m"],
+    ["coverage", "xml"],
+    ["coverage", "html"]
+]
+
+[tool.tox.env.style]
+skip_install = true
+deps = ["ruff"]
+commands = [
+    ["ruff", "check"],
+    ["ruff", "format", "--diff"]
+]
+
+[tool.tox.env.typecheck]
+use_develop = true
+deps = ["pyright"]
+commands = [["pyright"]]
+
+[tool.tox.env.readme]
+skip_install = true
+deps = ["uv", "twine"]
+commands = [
+    ["uv", "build", "-q", "-o", "{env_dir}/dist"],
+    ["twine", "check", "{env_dir}/dist/*"]
+]
+
+[tool.tox.env.reformat]
+skip_install = true
+deps = ["ruff"]
+commands = [
+    ["ruff", "check", "--fix"],
+    ["ruff", "format"]
+]

ripple_effect-0.0.1/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

ripple_effect-0.0.1/src/ripple_effect/__init__.py

@@ -0,0 +1,5 @@
+"""ripple-effect: Know your blast radius before you push."""
+
+from ripple_effect.cli import main
+
+__all__ = ["main"]

ripple_effect-0.0.1/src/ripple_effect/cli.py

@@ -0,0 +1,16 @@
+"""CLI entry point for ripple-effect."""
+
+import click
+
+
+@click.command()
+@click.argument("config", type=click.Path(exists=True, dir_okay=False))
+@click.option("-n", "--dryrun", is_flag=True, help="Show what would be done without doing it")
+@click.option("-v", "--verbose", is_flag=True, help="Show more output")
+def main(config: str, dryrun: bool, verbose: bool) -> None:
+    """Test a Python library against its downstream dependents.
+
+    CONFIG is a YAML file describing the library under test and the downstream
+    projects to run against it.
+    """
+    click.echo("ripple-effect: not yet implemented")

ripple_effect-0.0.1/src/ripple_effect.egg-info/PKG-INFO

@@ -0,0 +1,76 @@
+Metadata-Version: 2.4
+Name: ripple-effect
+Version: 0.0.1
+Summary: Know your blast radius before you push
+Author-email: Zoran Simic <zoran@simicweb.com>
+License-Expression: MIT
+Project-URL: Source, https://github.com/zsimic/ripple-effect
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+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 :: Software Development :: Testing
+Classifier: Topic :: Utilities
+Requires-Python: >=3.10
+Description-Content-Type: text/x-rst
+License-File: LICENSE
+Requires-Dist: click
+Requires-Dist: PyYAML
+Requires-Dist: runez
+Dynamic: license-file
+
+ripple-effect
+=============
+
+Know your blast radius before you push.
+
+Test a Python library against the downstream projects that depend on it —
+before you tag a release and find out the hard way.
+
+Installation
+------------
+
+.. code-block:: bash
+
+    uvx ripple-effect config.yml
+
+Usage
+-----
+
+Create a YAML config describing your library and the downstream projects to test against:
+
+.. code-block:: yaml
+
+    proving-grounds: /tmp/ripple-effect-workspace
+    downstream-projects:
+      - git+https://github.com/example/project-b.git@main
+      - git+https://github.com/example/project-c.git@main
+
+Then run:
+
+.. code-block:: bash
+
+    ripple-effect config.yml
+
+ripple-effect will:
+
+1. Clone (or update) each downstream project into ``proving-grounds``
+2. Create a venv for each, with the downstream project + your library installed in editable mode
+3. Run each project's test suite
+4. Report which passed, which failed
+
+For local iteration (e.g. testing against a local checkout of a downstream project):
+
+.. code-block:: yaml
+
+    proving-grounds: ~/dev/my-ripple-workspace
+    downstream-projects:
+      - git+https://github.com/example/project-b.git@main
+      - ~/dev/project-c

ripple_effect-0.0.1/src/ripple_effect.egg-info/SOURCES.txt

@@ -0,0 +1,18 @@
+.gitignore
+DEVELOP.md
+LICENSE
+README.rst
+SPEC.md
+pyproject.toml
+.github/workflows/release.yml
+.github/workflows/tests.yml
+src/ripple_effect/__init__.py
+src/ripple_effect/cli.py
+src/ripple_effect.egg-info/PKG-INFO
+src/ripple_effect.egg-info/SOURCES.txt
+src/ripple_effect.egg-info/dependency_links.txt
+src/ripple_effect.egg-info/entry_points.txt
+src/ripple_effect.egg-info/requires.txt
+src/ripple_effect.egg-info/top_level.txt
+tests/conftest.py
+tests/test_cli.py

ripple_effect-0.0.1/src/ripple_effect.egg-info/dependency_links.txt

@@ -0,0 +1 @@
+

ripple_effect-0.0.1/src/ripple_effect.egg-info/entry_points.txt

@@ -0,0 +1,2 @@
+[console_scripts]
+ripple-effect = ripple_effect:main

ripple_effect-0.0.1/src/ripple_effect.egg-info/requires.txt

@@ -0,0 +1,3 @@
+click
+PyYAML
+runez

ripple_effect-0.0.1/src/ripple_effect.egg-info/top_level.txt

@@ -0,0 +1 @@
+ripple_effect

ripple_effect-0.0.1/tests/conftest.py

@@ -0,0 +1,5 @@
+from runez.conftest import cli, ClickRunner, temp_folder  # noqa: F401, fixtures
+
+from ripple_effect import main
+
+ClickRunner.default_main = main

ripple_effect-0.0.1/tests/test_cli.py

@@ -0,0 +1,19 @@
+import runez
+
+
+def test_help(cli):
+    cli.run("--help")
+    assert cli.succeeded
+    assert "downstream" in cli.logged.stdout
+
+
+def test_missing_config(cli, temp_folder):
+    cli.run("no-such-config.yml")
+    assert cli.failed
+
+
+def test_sample_config(cli, temp_folder):
+    runez.write("sample.yml", "# placeholder\n", logger=None)
+    cli.run("sample.yml")
+    assert cli.succeeded
+    assert "not yet implemented" in cli.logged.stdout