Repository navigation
riverproui not go installable #479
Description
Similar to issues we've run into in the past with the river migration CLI, this install fails due to a replace directive:
➜ ~ go install riverqueue.com/riverui/riverproui/cmd/riverproui@latest
go: riverqueue.com/riverui/riverproui/cmd/riverproui@latest (in riverqueue.com/riverui/riverproui@v0.13.0):
The go.mod file for the module providing named packages contains one or
more replace directives. It must not contain directives that would cause
it to be interpreted differently than if it were the main module.
We probably need to use a more complex multi-step release flow to make this work 😞 cc @brandur
Activity
brandur commentedon Jan 2, 2026
Ah dang, yeah these are easy to forget.
Just a reminder too that the other plausible route here is to make the project a Go workspace (requires fixing the proxy). With the workspace, you don't need the replaces, and you therefore take the errors in that area down to zero as I think has been shown pretty well so far in the main project. Workspaces have a few issues of their own, but IMO still an overall improvement.
bgentry commentedon Jan 2, 2026
I thought the issues we ran into here were with the
gotool and that there was nothing we could do at the proxy level to fix it? Definitely possible I'm misremembering this though so let's sync on that one :)brandur commentedon Jan 3, 2026
My memory is that we could get it working, but it'd require that the proxy be able to pass through arbitrary tag names (i.e. ones not seen yet) as opposed to just the ones it's already been built with. The exact reason for that has gotten pretty hazy though.