anuna-research/elephant
1
0
Fork 0
Code Issues 6 Pull requests Projects Packages Wiki Activity Actions

fix(ci): re-pin DID_CRDT_REF to canonical did-crdt repo #7

Merged
hugooconnor merged 0 commits from refs/pull/7/head into main 2026-07-15 06:50:55 +00:00
Conversation 0 Commits - Files changed -
hugooconnor commented 2026-07-15 06:48:35 +00:00 (Migrated from codeberg.org)
Copy link

Problem

The v0.1.1 release pipeline failed at the sibling-clone step:

Cloning into '../did-crdt'...
fatal: reference is not a tree: 06842517a9c66225f75786dd9935256c0f6ec0d4

cbcl-rs and spindle-rust checked out fine; only did-crdt failed.

Root cause — stale pin, not a wrong URL

The clone URL (codeberg.org/anuna/did-crdt) is correct and canonical. The pin was stale: DID_CRDT_REF=06842517 is a commit from the deprecated anuna/did-crdt-archive repo, which shares no history with canonical did-crdt (git merge-base between them is empty). So the commit simply doesn't exist on the repo CI clones.

This was the did-crdt path-dep skew: the local ../did-crdt sibling was still the archive checkout, so local builds/pins drifted onto archive commits while CI cloned the canonical repo.

Fix

Re-pin DID_CRDT_REF to adb5c7a — canonical did-crdt's HEAD (feat: did:crdt reference implementation).

Verification (against canonical did-crdt)

  • cargo build --locked holds — Cargo.lock unchanged (canonical did-crdt has the same dependency set).
  • Full cargo test passes: 199 tests, 0 failures.
  • All did-crdt symbols elephant uses (node_id_from_pubkey, Did, Document, DidDocument, from_bytes, …) are present in the canonical repo.

Local layout (already realigned on this machine)

../did-crdt now tracks canonical did-crdt.git @ adb5c7a; the old archive checkout was preserved as ../did-crdt-archive (its origin is did-crdt-archive.git, untracked papers/specs intact).

Note on the release

Tag v0.1.1 was already pushed and its CI failed on the old pin. After this merges, the v0.1.1 tag needs to be re-pointed at the fixed commit (or cut v0.1.2) to re-trigger the pipeline.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Q6GBsN4CfVF7QXAycnK2ip

## Problem The `v0.1.1` release pipeline failed at the sibling-clone step: ``` Cloning into '../did-crdt'... fatal: reference is not a tree: 06842517a9c66225f75786dd9935256c0f6ec0d4 ``` `cbcl-rs` and `spindle-rust` checked out fine; only `did-crdt` failed. ## Root cause — stale pin, not a wrong URL The clone URL (`codeberg.org/anuna/did-crdt`) is **correct and canonical**. The **pin** was stale: `DID_CRDT_REF=06842517` is a commit from the deprecated `anuna/did-crdt-archive` repo, which shares **no history** with canonical `did-crdt` (`git merge-base` between them is empty). So the commit simply doesn't exist on the repo CI clones. This was the did-crdt path-dep skew: the local `../did-crdt` sibling was still the archive checkout, so local builds/pins drifted onto archive commits while CI cloned the canonical repo. ## Fix Re-pin `DID_CRDT_REF` to `adb5c7a` — canonical `did-crdt`'s HEAD (`feat: did:crdt reference implementation`). ## Verification (against canonical `did-crdt`) - `cargo build --locked` holds — **`Cargo.lock` unchanged** (canonical did-crdt has the same dependency set). - Full `cargo test` passes: **199 tests, 0 failures**. - All did-crdt symbols elephant uses (`node_id_from_pubkey`, `Did`, `Document`, `DidDocument`, `from_bytes`, …) are present in the canonical repo. ## Local layout (already realigned on this machine) `../did-crdt` now tracks canonical `did-crdt.git @ adb5c7a`; the old archive checkout was preserved as `../did-crdt-archive` (its origin is `did-crdt-archive.git`, untracked papers/specs intact). ## Note on the release Tag `v0.1.1` was already pushed and its CI failed on the old pin. After this merges, the `v0.1.1` tag needs to be re-pointed at the fixed commit (or cut `v0.1.2`) to re-trigger the pipeline. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01Q6GBsN4CfVF7QXAycnK2ip
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
anuna-research/elephant!7
No description provided.