feat(convoy): include Forge mod GUIDs in catalog - #371
Merged
Conversation
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
force-pushed
the
worktree-convoy-guid
branch
from
July 30, 2026 06:37
933462a to
0176b69
Compare
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
installed_mods(migration 021) and thread through all install pathsguidfield on each mod, populated from DBpackage.jsonfrom disk when the DB value is NULL (covers manually-installed mods)Test plan
cargo checkpassescargo clippy -- -D warningscleanguidfield on each modImplemented with the help of Claude Code