Refactor: Rename context-guru module path kagenti → rossoctl#10
Merged
Merged
Conversation
…ssoctl/context-guru Part of the Kagenti → Rossoctl rename. context-guru was org-moved to rossoctl/context-guru, but its go.mod still declared module github.com/kagenti/context-guru — a module-path mismatch that blocks downstream importers (cortex's authlib/authbridge-envoy/authbridge-proxy import github.com/rossoctl/context-guru) from running `go mod tidy` / regenerating go.sum. - Go module + imports: github.com/kagenti/context-guru → github.com/rossoctl/context-guru - Cross-repo refs: kagenti/kagenti → rossoctl/rossoctl; kagenti-extensions → cortex (the AuthBridge plugin lives there); kagenti/.github → rossoctl/.github - Brand / prose: Kagenti → Rossoctl Verification: git grep clean of kagenti; go build ✅, go vet ✅, go test ✅ (17 pkgs, 0 fail). Once merged and a new pseudo-version publishes, cortex can `go mod tidy` to pick up the renamed module + real go.sum checksums (rossoctl/cortex#680). Related to rossoctl/rossoctl#1972 Assisted-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: IBRAHIM IBRAHIM <66755652+Ibrahim2595@users.noreply.github.com>
Ibrahim2595
changed the title
Ibrahim2595
added a commit
to Ibrahim2595/kagenti-extensions
that referenced
this pull request
Jul 20, 2026
context-guru's module path was renamed (rossoctl/context-guru#10, commit 8fc7c7b36563). This branch pinned the pre-rename commit v0.0.0-20260713113308-b624f2c3d8c2 whose go.mod still declared github.com/kagenti/context-guru, breaking `go build`/`go mod verify` with a module-path mismatch (the Go CI (authlib) failure). Bumped context-guru to v0.0.0-20260720181432-8fc7c7b36563 and regenerated real go.sum checksums via `go mod tidy` in authlib, authbridge-envoy, authbridge-proxy. Verification: all 8 modules build; authlib go vet + go test pass (43 pkgs, 0 fail); git grep clean of kagenti and rossocortex. Related to rossoctl/rossoctl#1972 Assisted-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: IBRAHIM IBRAHIM <66755652+Ibrahim2595@users.noreply.github.com>
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
2 participants
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
Part of the Kagenti → Rossoctl rename.
context-guruwas org-moved torossoctl/context-guru, but itsgo.modstill declaredmodule github.com/kagenti/context-guru— a module-path mismatch that blocks downstream importers (cortex'sauthlib/authbridge-envoy/authbridge-proxyimportgithub.com/rossoctl/context-guru) from runninggo mod tidy/ regeneratinggo.sum.github.com/kagenti/context-guru→github.com/rossoctl/context-gurukagenti/kagenti→rossoctl/rossoctl;kagenti-extensions→cortex(the AuthBridge plugin lives there);kagenti/.github→rossoctl/.githubVerification
git grepclean ofkagentigo build ./...✅ ·go vet ./...✅ ·go test ./...✅ (17 packages, 0 failures)Unblocks
Once merged and a new pseudo-version publishes, cortex can
go mod tidyto pick up the renamed module + realgo.sumchecksums — see rossoctl/cortex#680.Related issue(s)
Related to rossoctl/rossoctl#1972