This repository was archived by the owner on Oct 5, 2026. It is now read-only.
Repository navigation
chore: depend on the published harness crates, not a git revision (#25) - #45
Merged
Merged
Conversation
The harness published to crates.io yesterday, so the three git pins
become ordinary version requirements and this repository stops
depending on a commit that could be rewritten.
cratefield-core = "0.3"
cratefield-testing = "0.1"
cratefield-adapter-sqlite = "0.1"
Ranges follow the harness's own policy in its docs/COMPATIBILITY.md: a
caret on the current minor while pre-1.0, so a core minor bump can never
be picked up silently. Resolves to core 0.3.1 — five minor versions of
new ports (Blob, Push, Payments, Realtime, Outbox, Inbox) ahead of the
pinned revision, and nothing here needed changing for them.
The crates were renamed `factory0-*` -> `cratefield-*` before that first
release (harness ADR 0011), so this also renames every reference: 237 of
them across manifests, sources and tests. **Our own `factory0-auth-*`
package names are unchanged** — this is an unpublished Factory Zero
service, not a Cratefield crate, which is what ADR 0011 says.
CI's reusable conformance workflow moves from `@main` to a commit SHA.
At `@main` an unrelated push to the harness silently changes what this
repository's CI runs, with no diff here. The harness has no release tags
(release-plz has never produced one) and a SHA cannot be moved where a
tag can.
Gates: 396 tests, clippy -D warnings, fmt, the wasm32 workspace build,
and the wasm dependency boundary (no openssl/reqwest/mio).
Closes #25.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V8K9TBtmnf29dV6uEP5oM3
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #25. The harness published to crates.io yesterday, so the three git revision pins become ordinary version requirements and this repository stops depending on a commit that could be rewritten.
Ranges follow the harness's own policy in its
docs/COMPATIBILITY.md: a caret on the current minor while pre-1.0, so"0.3"accepts 0.3.x and a core minor bump can never be picked up silently.What that upgrade actually was
The pinned revision was from before the rename. This resolves to core 0.3.1, which is a long way ahead of it — the Blob, Push, Payments, Realtime, Outbox and Inbox ports all landed in between. Nothing here needed changing for any of them, which is the ports-and-adapters design doing its job: this service asks for ports by name and never sees the ones it did not ask for.
The rename
The crates went
factory0-*→cratefield-*before that first release (harness ADR 0011), so this renames every reference — 237 across manifests, sources and tests.Our own
factory0-auth-*package names are unchanged. This is an unpublished Factory Zero service, not a Cratefield crate, which is exactly what ADR 0011 says. The only churn in the diff beyond the rename is import ordering:cratefield_sorts beforefactory0_.The reusable workflow
CI called
Cratefield/harness/.github/workflows/conformance.yml@main. At@main, an unrelated push to the harness silently changes what this repository's CI runs, with no diff here to review. Now pinned to a commit SHA — the harness has no release tags (release-plz has never produced one), and a SHA cannot be moved where a tag can. Bump deliberately.Gates
396 tests, clippy
--all-targets --all-features -D warnings, fmt, the wasm32 workspace build, and the wasm dependency boundary (no openssl/reqwest/mio in the tree).cargo treeshows zero git dependencies remaining.🤖 Generated with Claude Code
https://claude.ai/code/session_01V8K9TBtmnf29dV6uEP5oM3