Skip to content

feat: a plan under the wrong scope is refused by name, and status can be asked about a scope #86

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rldyourmnd merged 1 commit into from
Sep 2, 2026
Merged

feat: a plan under the wrong scope is refused by name, and status can be asked about a scope #86

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,25 @@ sibling project the same week this note was added.

## [Unreleased]

## [0.0.55] - 2026-09-02

A plan whose scope contradicts the target's record is refused by
name. A target managed under `project` used to accept a plan naming the
global profile, measure the global inventory at a workspace where those
namespaces are simply absent, and — had it been applied — rewrite the record
with the wrong ownership. The consumer met the first half as a bare
`expected_target_digest` mismatch when their remove plan carried no scope;
the refusal now says which scope to send (`unsupported_operation`). One
direction only: a home managed globally may still be asked about a scope.

`status --target-scope <scope>` is honoured: asked, `status` measures the
inventory the plan will, instead of the global namespaces at a workspace
root that a repository may spell for its own reasons. Absent the flag,
`status` is exactly what it was. The `provider-info` member that lets a
consumer send it, `status_request_fields`, is present in the build and
empty until the kit names it and a released consumer accepts it; this
release publishes the same thirteen names 0.0.54 did.

## [0.0.54] - 2026-09-02

`remove` reads a bundle, and the plan says per path what stays.
Expand Down
8 changes: 4 additions & 4 deletions Cargo.lock
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

8 changes: 4 additions & 4 deletions Cargo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ members = [
]

[workspace.package]
version = "0.0.54"
version = "0.0.55"
edition = "2024"
rust-version = "1.89"
license = "AGPL-3.0-or-later"
Expand All @@ -23,9 +23,9 @@ sha2 = "0.11"
# `setup-core::archive`); an inflate loop is not, because its bugs are
# memory-safety bugs and it is not improved by being hand-written here.
miniz_oxide = "0.9"
setup-core = { path = "crates/setup-core", version = "0.0.54" }
provider-v3 = { path = "crates/provider-v3", version = "0.0.54" }
harness-runtime = { path = "crates/harness-runtime", version = "0.0.54" }
setup-core = { path = "crates/setup-core", version = "0.0.55" }
provider-v3 = { path = "crates/provider-v3", version = "0.0.55" }
harness-runtime = { path = "crates/harness-runtime", version = "0.0.55" }

[workspace.lints.rust]
unsafe_code = "forbid"
Expand Down
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -179,7 +179,7 @@ release is a convenience, not the authorised copy.

```bash
docker run --rm -v "$HOME/.config:/config" \
ghcr.io/nddev-opennetwork/opencode-setup-system:0.0.54 \
ghcr.io/nddev-opennetwork/opencode-setup-system:0.0.55 \
status --target /config/<dir> --json
```

Expand Down
Loading
Loading