You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 5c26a7e
Browse filesBrowse the repository at this point in the historyBrowse files
build: require nested modules at versions that exist
Nineteen requires named github.com/xraph/forge or a sibling extension at
v0.0.0-00010101000000-000000000000, the zero pseudo-version Go writes when
a module is only ever reached through a replace. It is valid semver, so it
reads as deliberate, and it resolves for nobody:
go get github.com/xraph/forge/extensions/hls@v1.9.13
unknown revision v0.0.0-00010101000000-000000000000
The replace hides it in every local build, so this only bites someone
outside the repo.
Pinned to v1.9.13, the current release, then tidied. Tidy moves some
forge requires from v1.9.2 up to v1.9.13 as a consequence: pinning a
sibling to v1.9.13 makes MVS pick that for the root too.
cmd/forge still fails to build. That is a pre-existing compile error in
plugins/client.go, unrelated to these files.
0 commit comments