No functional change from v0.14.0. This release exists only because the module's declared path changed when the repository moved to the lightgatehq organization, and a path change is a new module identity to the Go toolchain.
go get github.com/lightgatehq/lidapters@v0.15.0Why v0.15.0 and not v0.14.1
The two paths are distinct modules rather than a patch lineage, so a fresh minor makes the discontinuity legible and leaves the old path's patch range free. The repository follows semantic versioning and carries no policy requiring otherwise.
Why a new tag was needed at all
The v0.5.x-v0.14.0 tags remain resolvable only under github.com/daccred/lidapters. They are reachable under the new path — same commits, same repository, so proxy.golang.org lists them — but they do not resolve there:
go: github.com/lightgatehq/lidapters@v0.14.0: parsing go.mod:
module declares its path as: github.com/daccred/lidapters
but was required as: github.com/lightgatehq/lidapters
Those tags predate the rename, so their go.mod still declares the old path and the toolchain rejects the mismatch. v0.15.0 is the lowest tag that actually carries the new module path.
Neither retract nor replace can express a path change, so neither was added.
Contents
Diffing v0.14.0 against this tag yields only the import-path rewrite — 90 string replacements across 58 files (#46) — with build, vet, and the full test suite green on both sides. #45 is test-only work that landed before the rename.
Note for consumers
The old path keeps resolving indefinitely, because the module proxy's cache of it is permanent. That makes a stale import fail silently rather than loudly: it will build green while linking a different module. Move deliberately, and assert that no references to the old path survive.
What's Changed
- test(blend): close two V1-09 review gaps (share-stage floor vector, pre-Comet checkpoint gate) by @raybaann in #45
- chore: rename the module path to github.com/lightgatehq/lidapters by @raybaann in #46
Full Changelog: v0.14.0...v0.15.0
