cljgo 0.8.7
Changelog
- 78c1d66: docs(site): a guide for dual-host .cljc projects (@muthuishere)
- c2bfa04: feat(deps): read :paths from deps.edn when a project has no build file — ADR 0119 (@muthuishere)
- 8f3fd4f: fix(nrepl): the same project-resolution gap as the REPL — #185 (@muthuishere)
- 237f0b1: fix(repl): cljgo repl resolved nothing from the project — #185 (@muthuishere)
- 4128db9: readme: AgentNexus community link (Discord) (@muthuishere)
- 92fb2f5: refactor(cli): one project resolution, before dispatch — ADR 0118 (@muthuishere)
- 95685ee: release: prepare v0.8.7 (@muthuishere)
- 48982a0: test(conformance): agent-lifecycle was racy by construction, not flaky (@muthuishere)
Install
go install github.com/muthuishere/cljgo/cmd/cljgo@v0.8.7Or download a binary above and put it on your PATH.
cljgo repl, cljgo run and Go interop work from the binary alone, with
no Go toolchain installed. cljgo build additionally needs the Go
toolchain — it emits Go and calls go build. It does NOT need a checkout
of this repo: a release binary pins the published module in the generated
go.mod and never writes a replace (ADR 0028), so binary + Go toolchain
is the whole story.
CLJGO_SRC is now only for pointing a build at a LOCAL cljgo tree on
purpose — developing cljgo itself, or testing an unreleased change.
Note for anything before v0.8.5: a binary from go install …@vX.Y.Z was
not recognised as a release and demanded a source tree anyway. That was
#177, fixed in v0.8.5 by ADR 0116.
cljgo's own code is MIT. The vendored runtime under pkg/lang/ is
EPL-1.0, from Glojure — see
NOTICE.
