Skip to content

chore(gnome): use local path for lnxdrive-ipc dep (FU-009 / RD-2)#58

Merged
montfort merged 2 commits into
mainfrom
chore/gnome-ipc-path-dep
Jul 4, 2026
Merged

chore(gnome): use local path for lnxdrive-ipc dep (FU-009 / RD-2)#58
montfort merged 2 commits into
mainfrom
chore/gnome-ipc-path-dep

Conversation

@montfort

@montfort montfort commented Jul 4, 2026

Copy link
Copy Markdown
Contributor

Contexto

Cierra FU-009 / RD-2 del backlog de follow-ups (heredado del round de auditoría externa Fases 4–5, AILOG-2026-07-03-001).

Problema

lnxdrive-gnome declaraba su dependencia lnxdrive-ipc vía git remoto:

lnxdrive-ipc = { git = "https://github.com/strangedaystech/lnxdrive.git" }

…cuando el crate vive en el mismo monorepo (lnxdrive-engine/crates/lnxdrive-ipc/). Sin rev/branch, el git dep resolvía a la rama por defecto del remoto y quedó pineado en el Cargo.lock a un commit viejo (d3a6b0c2: lnxdrive-core 0.1.0, serde_yaml), desalineado del estado local del monorepo (0.1.0-alpha.1, serde_norway).

Cambio

lnxdrive-ipc = { path = "../lnxdrive-engine/crates/lnxdrive-ipc" }

El path local hace que la dep siga el working tree — comportamiento correcto para una dependencia in-repo — y elimina el lockfile stale. Bajo impacto: el crate es un stub que no entra al bundle Flatpak.

Verificación

  • cargo metadata resuelve lnxdrive-ipc a source=None con manifest_path apuntando al crate local del monorepo.
  • El grafo de dependencias completo resuelve limpio (exit=0).
  • Cargo.lock regenerado sin entradas git+… para lnxdrive-ipc / lnxdrive-core.

Gobernanza

  • AILOG: .straymark/07-ai-audit/agent-logs/gnome/AILOG-2026-07-03-005-gnome-ipc-local-path-dep.md
  • Registro de follow-ups: FU-009 → closed; de paso se cierra FU-012 (copy overstatement, ya mitigado en su AILOG de origen antes del tag). Contadores: 6 open / 9 closed.

🤖 Generated with Claude Code

montfort and others added 2 commits July 3, 2026 21:53
The gnome crate pulled lnxdrive-ipc via a remote git URL pinned to a stale
commit (lnxdrive-core 0.1.0 / serde_yaml), diverging from the monorepo's
current 0.1.0-alpha.1 (serde_norway). Point it at the local crate path so it
tracks the working tree, as intended for an in-repo dependency.

Verified: cargo metadata resolves lnxdrive-ipc to the local manifest
(source=None) and the full graph resolves cleanly.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…tement)

- FU-009: closed by e8c4a00 (git dep -> local path).
- FU-012: closed in triage — already mitigated in its source AILOG before tag.
- Add AILOG-2026-07-03-005 documenting the FU-009 chore.
- Recount: 6 open / 9 closed (total 15).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@montfort montfort merged commit a1650c5 into main Jul 4, 2026
5 checks passed
@montfort montfort deleted the chore/gnome-ipc-path-dep branch July 4, 2026 03:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant