Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
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
5 changes: 3 additions & 2 deletions .opencode/skills/release-workflow/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,8 +31,9 @@ to ship in seam → adapter → leaf order.

## The exact-pin cascade

`eggup-eggpack` pins its Eggup dependencies exactly (`=0.2.0`). Every other
crate uses a caret requirement. Consequence:
The current `eggup-eggpack` workspace source pins its Eggup dependencies
exactly to `=0.2.1`; the published `eggup-eggpack 0.2.0` remains pinned to
`=0.2.0`. Every other workspace crate uses a caret requirement. Consequence:

- A fix published to a caret consumer (`eggup-curl`, `eggup-eggfetch`,
`eggup-service`) is inherited automatically on the next resolve — **within the
Expand Down
5 changes: 3 additions & 2 deletions AGENTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ Full dependency rules and per-crate boundary rationale:
- `crates/eggup-curl` — external-curl adapter, no embedded HTTP/TLS stack; depends only on `eggup-acquisition`. Must not know `eggup-eggfetch` exists. Transport composition lives in the seam, never in an adapter.
- `crates/eggup-service` — manager-neutral lifecycle; depends only on `eggup-core` (+ `windows-args`, + `windows-service` on Windows).
- `crates/eggup-archive` — bounded allowlisted local tar.gz/zip extraction; deps `tar`, `zip`, `flate2`, `fs_at`, `sha2`, dev-dep `eggup-core`. No transport, authenticity, or live-installation policy.
- `crates/eggup-eggpack` — optional leaf adapter for Eggpack ReleaseManifest v1; published (`=0.2.0`), depends on `core` + `archive` + `acquisition` (each pinned `=0.2.0`, local paths) + `eggpack-manifest = "=0.1.1"` from the registry; its exact dependency list is owned by `crates/eggup-eggpack/Cargo.toml`. Only crate allowed to touch producer types.
- `crates/eggup-eggpack` — optional leaf adapter for Eggpack ReleaseManifest v1; latest published version is `0.2.0` (its immutable package pins Eggup dependencies at `=0.2.0`). The workspace source candidate is `0.2.1` and its three local pins are `=0.2.1`; it depends on `core` + `archive` + `acquisition` (local paths) + `eggpack-manifest = "=0.1.1"` from the registry. Its exact dependency list is owned by `crates/eggup-eggpack/Cargo.toml`. Only crate allowed to touch producer types.
- `crates/eggup-transport-footprint` — non-published (`publish = false`) footprint fixtures: `curl_only` / `eggfetch_only` / `dual` binaries behind `required-features`, with a source-level linkage-discipline guard in `tests/cross_link_guard.rs`. The isolated single-adapter configurations are built by `stable` and `macos` and checked at the MSRV floor by `msrv`; `windows-check` builds none of them.

New crates must join `Cargo.toml` members, inherit the 5 shared keys (`version`, `edition`, `rust-version`, `license`, `repository`), and set `[lints] workspace = true`. The 7 library crates also carry `#![forbid(unsafe_code)]` and `#![deny(missing_docs)]`; `eggup-transport-footprint` is the sole exception (binary-only, no `lib.rs`, and no `README.md`/`CHANGELOG.md` — see §3.4 of the governance deep dive).
Expand All @@ -35,7 +35,8 @@ gaps are in [`architecture/tooling-governance.md`](architecture/tooling-governan
# + cargo clippy --workspace --all-targets --all-features --locked -- -D warnings
# + cargo test --workspace --all-targets --all-features --locked
# + cargo doc --workspace --no-deps --locked
# + cargo tree --workspace --locked # review step, not a gate
# + cargo tree --workspace --locked # executed for resolution; review boundary output manually
# + ./scripts/check-docs-truth.sh # source versions, published versions, and docs truth
```

`cargo tree` always exits 0 on a resolvable graph. Read it: the dependency-boundary rules are enforced by **human review only**.
Expand Down
17 changes: 13 additions & 4 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -403,10 +403,12 @@ claims are made by any of these crates.

## Unreleased

Nothing in this section has been published. The current published baselines
are `0.2.0` for all seven published crates; `eggup-transport-footprint` is
`publish = false` and has no registry version. This dependency refresh does
not authorize publication or consumer migration.
Nothing in this section has been published. The latest published version is
`0.2.0` for all seven publishable crates; `eggup-transport-footprint` is
`publish = false` and has no registry version. This section includes M007
dependency maintenance and M016 preparation of an `eggup-core 0.2.1` package
candidate. Neither records explicit upload authorization or a publication, and
no consumer migration has occurred.

- `eggup-archive`: update the ZIP dependency from `6.0.0` to `9.6.1`, keeping
explicit bounded extraction behavior and the public API unchanged. This
Expand All @@ -417,6 +419,13 @@ not authorize publication or consumer migration.
`eggup-eggpack 0.2.0` package.
- Refresh compatible lockfile dependencies, including the patched Rustls,
`rustls-webpki`, and `webpki-roots` versions.
- `eggup-core` M016: prepare the `0.2.1` package to include the three existing
authoritative contract documents. This is package-content-only; the Core
`0.2.0` registry artifact remains unchanged, and the candidate is not yet published.
- `eggup-eggpack`: align the three local exact pins to workspace source version
`=0.2.1`. The published `eggup-eggpack 0.2.0` archive and its `=0.2.0` pins
are unchanged; the `0.2.1` source candidate is not yet published, and no
Eggpack publication is authorized.

## 0.1.1

Expand Down
16 changes: 8 additions & 8 deletions Cargo.lock

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

2 changes: 1 addition & 1 deletion Cargo.toml
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ members = [
]

[workspace.package]
version = "0.2.0"
version = "0.2.1"
edition = "2021"
rust-version = "1.89"
license = "MIT"
Expand Down
11 changes: 7 additions & 4 deletions architecture/acquisition.md
Original file line number Diff line number Diff line change
Expand Up @@ -46,11 +46,13 @@ Crates that depend on it:
|---|---|---|
| `eggup-eggfetch` | `0.2` (caret) + path | native HTTP adapter; implements `AcquisitionTransport` |
| `eggup-curl` | `0.2` (caret) + path | external-process adapter; implements `AcquisitionTransport` |
| `eggup-eggpack` | `=0.2.0` exact pin + path | `use eggup_acquisition::{AcquisitionRequest, FetchLimits}` only (`eggup-eggpack/src/lib.rs:6`) — binds requests, never transports |
| `eggup-eggpack` | workspace source `=0.2.1` exact pin + path; published `0.2.0` retains `=0.2.0` | `use eggup_acquisition::{AcquisitionRequest, FetchLimits}` only (`eggup-eggpack/src/lib.rs:6`) — binds requests, never transports |
| `eggup-transport-footprint` | `0.2` (caret) + path | `curl_only.rs` / `eggfetch_only.rs` use `AcquisitionRequest` + `FetchLimits`; `dual.rs` uses `ComposedTransport` + `CompositionPolicy` |

The caret/exact-pin split is deliberate: adapters inherit a seam fix on the next
resolve, `eggup-eggpack` does not
resolve; the published `eggup-eggpack 0.2.0` exact pin does not. The workspace
source candidate has moved its local pin to `=0.2.1`, but that does not update
the immutable published package.
([acquisition-transport-roadmap.md](../plans/subsystems/acquisition-transport-roadmap.md#m010--eggup-acquisition-013-publication),
M010). The `0.1.0` caret became `0.2` in the `0.2.0` publication train
(Acquisition Transport M017): the seam's `0.2.0` is source-breaking
Expand Down Expand Up @@ -589,8 +591,9 @@ caller set a `User-Agent`; that is the claim, and it is what M014 delivers.
It is explicitly **not** placement parity: the two controls live in different
types and are deliberately not aligned. `eggup-eggfetch`'s control lives in
`EggfetchConfig`, whose `user_agent` is a public field of a public,
non-`#[non_exhaustive]` struct in a crate published at `0.2.0`; moving it
would be a source break for published consumers. `eggup-curl`'s control lives
non-`#[non_exhaustive]` struct in the `eggup-eggfetch 0.2.0` registry release;
moving it would be a source break for published consumers. `eggup-curl`'s
control lives
on `CurlTransport` because `CurlConfig`'s fields are public and **not**
`#[non_exhaustive]` (`curl/src/lib.rs:58-76`), so adding a field there would
be source-breaking for every external struct-literal construction. Each
Expand Down
4 changes: 2 additions & 2 deletions architecture/eggfetch-adapter.md
Original file line number Diff line number Diff line change
Expand Up @@ -466,8 +466,8 @@ here as well as in [acquisition.md](acquisition.md) §11.1.
makes. The finding is closed at the capability level.
- **Parity is capability parity, not placement parity.** This adapter's control
lives in `EggfetchConfig`, whose `user_agent` is a public field of a public,
non-`#[non_exhaustive]` struct in a crate published at `0.2.0`; moving it
would be a source break for published consumers, so it stays where it is.
non-`#[non_exhaustive]` struct in the `eggup-eggfetch 0.2.0` registry release;
moving it would be a source break for published consumers, so it stays where it is.
The curl adapter's control lives on `CurlTransport` because `CurlConfig`'s
fields are public and **not** `#[non_exhaustive]`, so adding a field there
would be source-breaking for every external struct-literal construction.
Expand Down
21 changes: 11 additions & 10 deletions architecture/eggpack-adapter.md
Original file line number Diff line number Diff line change
Expand Up @@ -70,15 +70,15 @@ Runtime dependencies ([`Cargo.toml`](../crates/eggup-eggpack/Cargo.toml)):

| Dependency | Constraint | Source |
|---|---|---|
| `eggup-core` | `=0.2.0` | local path `../eggup-core` |
| `eggup-archive` | `=0.2.0` | local path `../eggup-archive` |
| `eggup-acquisition` | `=0.2.0` | local path `../eggup-acquisition` |
| `eggup-core` | `=0.2.1` | local path `../eggup-core` |
| `eggup-archive` | `=0.2.1` | local path `../eggup-archive` |
| `eggup-acquisition` | `=0.2.1` | local path `../eggup-acquisition` |
| `eggpack-manifest` | `=0.1.1` | crates.io registry |

The three Eggup edges are exact-pinned so the published crate cannot silently
resolve a different published seam; the producer edge is registry-only so the
published crate has no VCS source requirement. Both facts are asserted as
tests, not just comments — see
The workspace-source candidate pins its three Eggup edges to `=0.2.1`; the
published `eggup-eggpack 0.2.0` artifact remains unchanged and pins `=0.2.0`.
The producer edge is registry-only so the published crate has no VCS source
requirement. Both facts are asserted as tests, not just comments — see
[Testing approach](#testing-approach).

The adapter has **no direct `sha2` runtime dependency**. The archive digest is
Expand Down Expand Up @@ -255,9 +255,10 @@ as the enforcement point:
([`tests/interoperability.rs:972`](../crates/eggup-eggpack/tests/interoperability.rs))
asserts the manifest contains `eggpack-manifest = "=0.1.1"` and that it
contains no `git =`, `rev =`, `branch =`, or `tag =` edge; asserts all three
Eggup edges stay `=0.2.0` — derived from the adapter's own
`env!("CARGO_PKG_VERSION")` rather than a hardcoded literal, so the invariant
is "pinned to *our* version" and survives the next workspace bump; and asserts
Eggup edges match the adapter's own `env!("CARGO_PKG_VERSION")` rather than a
hardcoded literal, so the invariant is "pinned to *our* version" and survives
future workspace bumps (currently `=0.2.1` in this unpublished source
candidate); and asserts
`eggpack-core`, `eggpack-contract`, and `eggpack-bootstrap` appear nowhere.
- `adapter_source_claims_no_producer_or_service_authority`
([`tests/interoperability.rs:1023`](../crates/eggup-eggpack/tests/interoperability.rs))
Expand Down
Loading
Loading