Skip to content

fix: rename go module to allow go install to work#3

Open
JeremyLoy wants to merge 2 commits into
openfga:mainfrom
JeremyLoy:patch-1
Open

fix: rename go module to allow go install to work#3
JeremyLoy wants to merge 2 commits into
openfga:mainfrom
JeremyLoy:patch-1

Conversation

@JeremyLoy

Copy link
Copy Markdown

the error message is as follows:

$ GOBIN=bin go install github.com/openfga/model-visualizer/cmd@main        
go: github.com/openfga/model-visualizer/cmd@main: version constraints conflict:
        github.com/openfga/model-visualizer@v0.0.0-20250904214902-92619eb3d433: parsing go.mod:
        module declares its path as: weighted-graph-viz
                but was required as: github.com/openfga/model-visualizer

Description

What problem is being solved?

How is it being solved?

What changes are made to solve it?

References

Review Checklist

  • I have clicked on "allow edits by maintainers".
  • I have added documentation for new/changed functionality in this PR or in a PR to openfga.dev [Provide a link to any relevant PRs in the references section above]
  • The correct base branch is being used, if not main
  • I have added tests to validate that the change in functionality is working as expected

the error message is as follows:

 GOBIN=bin go install github.com/openfga/model-visualizer/cmd@main        
go: github.com/openfga/model-visualizer/cmd@main: version constraints conflict:
        github.com/openfga/model-visualizer@v0.0.0-20250904214902-92619eb3d433: parsing go.mod:
        module declares its path as: weighted-graph-viz
                but was required as: github.com/openfga/model-visualizer
@JeremyLoy JeremyLoy changed the title rename go module to allow go install to work fix: rename go module to allow go install to work Sep 17, 2025
@curfew-marathon

Copy link
Copy Markdown

This PR has had no human activity for 90 days, so it has been marked lifecycle/stale.

This is automated backlog grooming, not a judgment on the work.

What happens next, unless there is activity:

  • In 30 days, it will move to lifecycle/closing-soon
  • 30 days after that, it will be closed

To keep it open, push a commit or leave a comment, and the clock will reset. For work that should not auto-close, such as an RFC or long-running experiment, ask a maintainer to add lifecycle/frozen.

@curfew-marathon curfew-marathon added the lifecycle/stale No human activity in 90 days label Jul 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lifecycle/stale No human activity in 90 days

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants