Skip to content

feat(convoy): include Forge mod GUIDs in catalog - #371

Merged
cebarks merged 1 commit into
mainfrom
worktree-convoy-guid
Jul 30, 2026
Merged

feat(convoy): include Forge mod GUIDs in catalog#371
cebarks merged 1 commit into
mainfrom
worktree-convoy-guid

Conversation

@cebarks

@cebarks cebarks commented Jul 30, 2026

Copy link
Copy Markdown
Owner

Summary

  • Store Forge mod GUIDs in installed_mods (migration 021) and thread through all install paths
  • Convoy catalog JSON now includes a guid field on each mod, populated from DB
  • Falls back to reading package.json from disk when the DB value is NULL (covers manually-installed mods)

Test plan

  • cargo check passes
  • cargo clippy -- -D warnings clean
  • All 820+ tests pass
  • Dev server serves convoy catalog with guid field on each mod
  • DB-stored GUID appears correctly in catalog response

Implemented with the help of Claude Code

Store the Forge GUID in the installed_mods table (migration 021) and
thread it through all install paths. The convoy catalog now exposes each
mod's GUID, falling back to reading package.json on disk when the DB
value is NULL (covers manually-installed mods).

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@cebarks
cebarks force-pushed the worktree-convoy-guid branch from 933462a to 0176b69 Compare July 30, 2026 06:37
@cebarks cebarks changed the title feat(convoy): include Forge mod GUIDs in catalog + fix container detection feat(convoy): include Forge mod GUIDs in catalog Jul 30, 2026
@cebarks
cebarks merged commit a16f1e9 into main Jul 30, 2026
11 checks passed
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