mesh-build-node: narrow the fetch to the named paths, build members against the SDK their lock names, and build, pack and publish a package (issues 1758, 1587 S15-S19; ADR 0499 §4, ADR 0498 §5, ADR 0500 §4-§6; lead decision L10)

build_node_fetch takes buildstep.FetchRequest (dir and paths narrow the workspace) and an
optional package {repository, commit, ref}: the group's package member, built and packed
shut off and published nowhere. Each member's lock decides its SDK: the group's packed
file when the version and integrity are the lock's, else the registry's (integrity
checked); a version the registry lacks fails waits for: @novox/mesh-sdk@<version>. A
package artifact is built by its own script and packed with npm pack, shut off; only a
trunk build publishes it, from this process with the write credential (never in a
workspace): absent is published, the same file is done, another is version taken:. The
registry configuration file now lies outside every workspace.

This commit is contained in:

jschoubben

2026-10-22 18:38:22 +02:00

parent fde561075d

commit b9cdca78b0

13 changed files with 1217 additions and 29 deletions

									
										modules/mesh-build-node/module.json
									
		+1
		-1
	
												View File
												
				@@ -38,7 +38,7 @@

				  ],

				  "contributes": {

				    "npm-package-registry": {

				      "access": "read"

				      "access": "write"

				    }

				  },

				  "binds": {