mesh-catalog

novox/mesh-catalog

Fork 0

...

Author	SHA1	Message	Date
mesh-tools	f469eb387a	Merge pull request 'sdk1: build modules, provisioner and checks follow ADR 0593' (#598 ) from feat/sdk1 into main	2026-11-02 20:41:46 +00:00
mesh-tools	ee75d4327c	Merge pull request 'mesh-build-go: a relative replace still resolves in the temporary modfile' (#597 ) from fix/build-go-relative-replace into main	2026-11-02 18:51:34 +00:00
jschoubben	45084af849	A relative replace of a go.mod still resolves in the temporary modfile, so a module with a sibling package builds and verifies through the pins path mesh/delivery merged: source.main moved to novox/mesh-catalog@ee75d4327ce5 Details mesh/check being carried to 45084af849fc on ee75d4327ce5 \| from c52afdf88b84 ensureModfile copied go.mod word for word into pins/<dir>/, where `go mod verify` runs, so a replace to ./x or ../x pointed nowhere (route-proxy's failure of 2026-11-02 13:53, met a second time with the release's sibling packages). Every relative replace target is now made absolute under the tree the go.mod came from. mesh-build-node installs a module's own npm packages in a scratch copy of package.json, so a file:, link: or portal: dependency on a relative path would fail the same way; it is refused naming the package and its path, as a module without a lock is. Quick fix: rewrite the one replace route-proxy had, in ensureModfile (minutes). Thorough fix: the kind, a go.mod or package.json copied away from its tree, for every replace form (single, block, with a version, ./ and ../) in the one place all copies go through (ensureModfile, which versions.go and the pins share), and the same kind in the other build module that copies a manifest. Chosen: thorough, since it was met twice and hides a failure until the delivery (quick-or-thorough, fix-a-bug-met-twice). Test: TestARelativeReplaceStillResolvesInTheTemporaryModfile runs real go mod verify in the pins directory. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-02 19:36:15 +01:00

Author

SHA1

Message

Date

mesh-tools

f469eb387a

Merge pull request 'sdk1: build modules, provisioner and checks follow ADR 0593' (#598 ) from feat/sdk1 into main

2026-11-02 20:41:46 +00:00

mesh-tools

ee75d4327c

Merge pull request 'mesh-build-go: a relative replace still resolves in the temporary modfile' (#597 ) from fix/build-go-relative-replace into main

2026-11-02 18:51:34 +00:00

jschoubben

45084af849

A relative replace of a go.mod still resolves in the temporary modfile, so a module with a sibling package builds and verifies through the pins path

mesh/delivery merged: source.main moved to novox/mesh-catalog@ee75d4327ce5

Details

mesh/check being carried to 45084af849fc on ee75d4327ce5 | from c52afdf88b84

ensureModfile copied go.mod word for word into pins/<dir>/, where `go mod verify` runs, so a replace to ./x or ../x pointed
nowhere (route-proxy's failure of 2026-11-02 13:53, met a second time with the release's sibling packages). Every relative
replace target is now made absolute under the tree the go.mod came from. mesh-build-node installs a module's own npm
packages in a scratch copy of package.json, so a file:, link: or portal: dependency on a relative path would fail the same
way; it is refused naming the package and its path, as a module without a lock is.

Quick fix: rewrite the one replace route-proxy had, in ensureModfile (minutes). Thorough fix: the kind, a go.mod or
package.json copied away from its tree, for every replace form (single, block, with a version, ./ and ../) in the one place
all copies go through (ensureModfile, which versions.go and the pins share), and the same kind in the other build module
that copies a manifest. Chosen: thorough, since it was met twice and hides a failure until the delivery (quick-or-thorough,
fix-a-bug-met-twice). Test: TestARelativeReplaceStillResolvesInTheTemporaryModfile runs real go mod verify in the pins directory.

Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL

2026-11-02 19:36:15 +01:00

Compare commits

Diff Content Not Available