fastws-cli 0.0.8__tar.gz → 0.0.9__tar.gz

{fastws_cli-0.0.8 → fastws_cli-0.0.9}/CHANGELOG.md

@@ -1,5 +1,17 @@
 <!-- do not remove -->
 
+## 0.0.9
+
+### New Features
+
+- Add ws-build: build sdists of all workspace projects into a dists dir, skipping unchanged projects and pruning old versions ([#23](https://github.com/AnswerDotAI/fastws/issues/23))
+- detect project from cwd, add --nodeps to skip the dependency closure, and map dir names to packages ([#22](https://github.com/AnswerDotAI/fastws/issues/22))
+- Move `dep_key`, member graph, and closure helpers to ghapi (>=2.0.6) and use `dep_key`/`local_dep_graph`/`dep_closure` in core and releases ([#21](https://github.com/AnswerDotAI/fastws/issues/21))
+- ws-sync: write content-hashed .git/fastws-cargo-key per crate, covering Cargo.lock and locally patched git deps, for uv cache-keys ([#20](https://github.com/AnswerDotAI/fastws/issues/20))
+- Run cargo update before uv sync in `ws_sync` so Rust deps refresh first ([#19](https://github.com/AnswerDotAI/fastws/issues/19))
+- Add out-of-tree repo support, auto-managed workspace excludes, and uv.sources preservation to ws-sync ([#18](https://github.com/AnswerDotAI/fastws/issues/18))
+
+
 ## 0.0.8
 
 ### New Features

{fastws_cli-0.0.8/fastws_cli.egg-info → fastws_cli-0.0.9}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: fastws-cli
-Version: 0.0.8
+Version: 0.0.9
 Summary: Fast workspace tools for multi-repo management
 Author: Jeremy Howard
 License: Apache-2.0
@@ -12,7 +12,7 @@ Description-Content-Type: text/markdown
 License-File: LICENSE
 Requires-Dist: fastcore>=1.14.3
 Requires-Dist: fastgit>=0.0.7
-Requires-Dist: ghapi>=1.0.7
+Requires-Dist: ghapi>=2.0.6
 Requires-Dist: packaging
 Requires-Dist: tomli; python_version < "3.11"
 Provides-Extra: dev
@@ -42,6 +42,17 @@ AnswerDotAI/fastship
 AnswerDotAI/fastws
 ```
 
+A line may add a checkout location after the repo, for repos that live outside
+the workspace root (`~` ok). Every command then reads and writes them there, and
+`ws-sync` editable-installs each Python project found inside (the repo root if it
+has a `pyproject.toml`, else its immediate subdirectories), so one out-of-tree
+repo can hold several small packages alongside non-Python content:
+
+```
+AnswerDotAI/fastcore
+jph00/private ~/private
+```
+
 ## Commands
 
 ### `ws-clone`
@@ -80,6 +91,18 @@ ws-branches
 ws-branches --expected develop
 ```
 
+### `ws-build`
+
+Build an sdist of each workspace project (including `repos.txt` checkouts outside the root) into a dists directory, `.dists` by default. A project is rebuilt only when a file in it is newer than its existing sdist, and older versions of a rebuilt package are pruned, so the directory always holds one current sdist per project. A failing project gets a warning without stopping the others, but the command then exits 1.
+
+Progress goes to stderr; on success the dists path prints to stdout, so `$(ws-build)` in a script both refreshes the pool and yields its location. The result suits any resolver that takes a candidate pool, e.g. `uv pip install --find-links` or a docker build context for images that must test unreleased workspace packages:
+
+```bash
+ws-build
+ws-build --force  # rebuild everything
+ws-build --out /tmp/dists
+```
+
 ### `ws-sync`
 
 Sync the workspace metadata, pull local repos, and install updates.
@@ -88,11 +111,21 @@ It respects `tool.uv.workspace.members` and `exclude` when scanning local projec
 member directory isn't a Python project yet (no `pyproject.toml`, e.g. a fresh empty clone), it
 warns and skips the `uv sync` step instead of letting uv fail on the whole workspace.
 
+The workspace `exclude` list is auto-managed: a top-level directory that isn't a valid Python
+project and isn't a `repos.txt` checkout gets excluded automatically, and is un-excluded once it
+gains a real `pyproject.toml`. Globs, entries for missing directories, and entries for `repos.txt`
+checkouts are always kept, and `exclude = [...]` under `[tool.fastws]` in the workspace
+`pyproject.toml` declares intent the scan can't infer (e.g. keeping a real project out of the
+workspace). Hand-written `[tool.uv.sources]` entries (path, git, ...) are preserved when syncing
+adds new members.
+
 At most once per day (tracked by a stamp file inside the workspace's `.git`, so git never
 sees it), the sync also floats dependencies: `uv sync -U` instead of plain `uv sync`, plus
 a parallel `cargo update` in every member with a `Cargo.toml`, printing what moved. Pass
 `--upgrade` to force that pass regardless of when it last ran.
 
+Before every uv sync, `ws-sync` writes `.git/fastws-cargo-key` for each member crate. The key hashes `Cargo.lock` contents and the workspace Cargo patch configuration. For Git dependencies redirected to local paths by `[patch."<url>"]`, it also hashes each patched crate's `Cargo.toml`, `build.rs`, and `src` tree, recursively. The file is rewritten only when that content changes, so projects can use `{ file = ".git/fastws-cargo-key" }` in `tool.uv.cache-keys` without rebuilding after a timestamp-only `Cargo.lock` write.
+
 ```bash
 ws-sync
 ws-sync --workspace ~/aai-ws
@@ -104,12 +137,15 @@ ws-sync --upgrade
 Add a repo to `repos.txt`, then run `ws-sync`. Given `owner/repo`, it clones; given the
 name of an existing local folder (e.g. one just scaffolded with `nbdev-new` or `ship-new`),
 it resolves `owner/repo` from the folder's `origin` remote instead, telling you exactly
-what's missing if the folder has no git repo, no GitHub origin, or no `pyproject.toml`:
+what's missing if the folder has no git repo, no GitHub origin, or no `pyproject.toml`.
+Given a path outside the workspace root, the repo stays where it is and its location is
+recorded in `repos.txt` (no root `pyproject.toml` needed: its packages are discovered on sync):
 
 ```bash
 ws-add AnswerDotAI/fastws
 ws-add answerdotai/fastws
 ws-add fastws  # existing local folder, resolved via its origin remote
+ws-add ~/private  # a path outside the workspace: stays where it is, recorded in repos.txt with its location
 ```
 
 ### `ws-remove`
@@ -129,11 +165,14 @@ ws-remove fastws  # bare folder name also works if the directory exists
 Report repos with commits since their newest GitHub release, so nothing reviewed sits unshipped:
 
 ```bash
-ws-releases                 # sweep every repo in repos.txt
+ws-releases                 # at the workspace root: sweep every repo in repos.txt
 ws-releases solveit         # only solveit's transitive workspace dependencies
+ws-releases --nodeps        # inside a repo: just that repo
 ws-releases --skip 'wip'    # extra start-of-message regex for commits that need no release
 ```
 
+Run from inside a workspace checkout, the sweep narrows to that repo and its transitive workspace dependencies; `--nodeps` narrows it to the repo alone (an error when no project is in play).
+
 Each pending repo lists its unreleased commit summaries; repos with no releases yet get one quiet `no releases:` line, and fully-released repos appear in `up to date:`. The newest release is picked by version number (publish timestamps can be out of order), and repos whose default branch isn't `main` are handled automatically.
 
 Commits whose message matches a start-anchored regex from the skip set need no release and aren't reported. The built-in set covers version bumps and housekeeping (`bump`, `nbdev regen`, `.gitignore`, `docs`, `CI`, ...: `DEFAULT_SKIP` in `fastws.releases`); `[tool.fastws]` in the workspace root `pyproject.toml` adds to it, and names repos that should never be swept (apps that deploy rather than release):

{fastws_cli-0.0.8 → fastws_cli-0.0.9}/README.md

@@ -19,6 +19,17 @@ AnswerDotAI/fastship
 AnswerDotAI/fastws
 ```
 
+A line may add a checkout location after the repo, for repos that live outside
+the workspace root (`~` ok). Every command then reads and writes them there, and
+`ws-sync` editable-installs each Python project found inside (the repo root if it
+has a `pyproject.toml`, else its immediate subdirectories), so one out-of-tree
+repo can hold several small packages alongside non-Python content:
+
+```
+AnswerDotAI/fastcore
+jph00/private ~/private
+```
+
 ## Commands
 
 ### `ws-clone`
@@ -57,6 +68,18 @@ ws-branches
 ws-branches --expected develop
 ```
 
+### `ws-build`
+
+Build an sdist of each workspace project (including `repos.txt` checkouts outside the root) into a dists directory, `.dists` by default. A project is rebuilt only when a file in it is newer than its existing sdist, and older versions of a rebuilt package are pruned, so the directory always holds one current sdist per project. A failing project gets a warning without stopping the others, but the command then exits 1.
+
+Progress goes to stderr; on success the dists path prints to stdout, so `$(ws-build)` in a script both refreshes the pool and yields its location. The result suits any resolver that takes a candidate pool, e.g. `uv pip install --find-links` or a docker build context for images that must test unreleased workspace packages:
+
+```bash
+ws-build
+ws-build --force  # rebuild everything
+ws-build --out /tmp/dists
+```
+
 ### `ws-sync`
 
 Sync the workspace metadata, pull local repos, and install updates.
@@ -65,11 +88,21 @@ It respects `tool.uv.workspace.members` and `exclude` when scanning local projec
 member directory isn't a Python project yet (no `pyproject.toml`, e.g. a fresh empty clone), it
 warns and skips the `uv sync` step instead of letting uv fail on the whole workspace.
 
+The workspace `exclude` list is auto-managed: a top-level directory that isn't a valid Python
+project and isn't a `repos.txt` checkout gets excluded automatically, and is un-excluded once it
+gains a real `pyproject.toml`. Globs, entries for missing directories, and entries for `repos.txt`
+checkouts are always kept, and `exclude = [...]` under `[tool.fastws]` in the workspace
+`pyproject.toml` declares intent the scan can't infer (e.g. keeping a real project out of the
+workspace). Hand-written `[tool.uv.sources]` entries (path, git, ...) are preserved when syncing
+adds new members.
+
 At most once per day (tracked by a stamp file inside the workspace's `.git`, so git never
 sees it), the sync also floats dependencies: `uv sync -U` instead of plain `uv sync`, plus
 a parallel `cargo update` in every member with a `Cargo.toml`, printing what moved. Pass
 `--upgrade` to force that pass regardless of when it last ran.
 
+Before every uv sync, `ws-sync` writes `.git/fastws-cargo-key` for each member crate. The key hashes `Cargo.lock` contents and the workspace Cargo patch configuration. For Git dependencies redirected to local paths by `[patch."<url>"]`, it also hashes each patched crate's `Cargo.toml`, `build.rs`, and `src` tree, recursively. The file is rewritten only when that content changes, so projects can use `{ file = ".git/fastws-cargo-key" }` in `tool.uv.cache-keys` without rebuilding after a timestamp-only `Cargo.lock` write.
+
 ```bash
 ws-sync
 ws-sync --workspace ~/aai-ws
@@ -81,12 +114,15 @@ ws-sync --upgrade
 Add a repo to `repos.txt`, then run `ws-sync`. Given `owner/repo`, it clones; given the
 name of an existing local folder (e.g. one just scaffolded with `nbdev-new` or `ship-new`),
 it resolves `owner/repo` from the folder's `origin` remote instead, telling you exactly
-what's missing if the folder has no git repo, no GitHub origin, or no `pyproject.toml`:
+what's missing if the folder has no git repo, no GitHub origin, or no `pyproject.toml`.
+Given a path outside the workspace root, the repo stays where it is and its location is
+recorded in `repos.txt` (no root `pyproject.toml` needed: its packages are discovered on sync):
 
 ```bash
 ws-add AnswerDotAI/fastws
 ws-add answerdotai/fastws
 ws-add fastws  # existing local folder, resolved via its origin remote
+ws-add ~/private  # a path outside the workspace: stays where it is, recorded in repos.txt with its location
 ```
 
 ### `ws-remove`
@@ -106,11 +142,14 @@ ws-remove fastws  # bare folder name also works if the directory exists
 Report repos with commits since their newest GitHub release, so nothing reviewed sits unshipped:
 
 ```bash
-ws-releases                 # sweep every repo in repos.txt
+ws-releases                 # at the workspace root: sweep every repo in repos.txt
 ws-releases solveit         # only solveit's transitive workspace dependencies
+ws-releases --nodeps        # inside a repo: just that repo
 ws-releases --skip 'wip'    # extra start-of-message regex for commits that need no release
 ```
 
+Run from inside a workspace checkout, the sweep narrows to that repo and its transitive workspace dependencies; `--nodeps` narrows it to the repo alone (an error when no project is in play).
+
 Each pending repo lists its unreleased commit summaries; repos with no releases yet get one quiet `no releases:` line, and fully-released repos appear in `up to date:`. The newest release is picked by version number (publish timestamps can be out of order), and repos whose default branch isn't `main` are handled automatically.
 
 Commits whose message matches a start-anchored regex from the skip set need no release and aren't reported. The built-in set covers version bumps and housekeeping (`bump`, `nbdev regen`, `.gitignore`, `docs`, `CI`, ...: `DEFAULT_SKIP` in `fastws.releases`); `[tool.fastws]` in the workspace root `pyproject.toml` adds to it, and names repos that should never be swept (apps that deploy rather than release):

{fastws_cli-0.0.8 → fastws_cli-0.0.9}/fastws/__init__.py

@@ -1,4 +1,5 @@
-__version__ = "0.0.8"
+__version__ = "0.0.9"
+