{"_id":"@burgan-tech/vnext-workflow-cli","_rev":"15-39263f3c7a0429387bed87f2fc5cb8d6","name":"@burgan-tech/vnext-workflow-cli","dist-tags":{"latest":"1.0.14"},"versions":{"1.0.0":{"name":"@burgan-tech/vnext-workflow-cli","version":"1.0.0","keywords":["workflow","vnext","cli","automation"],"author":{"name":"Burgan Tech"},"license":"MIT","_id":"@burgan-tech/vnext-workflow-cli@1.0.0","maintainers":[{"name":"seal707","email":"mehmet.tosun@gmail.com"},{"name":"yilmaztayfun","email":"tayfun.yilmaz2@hotmail.com"}],"homepage":"https://github.com/burgan-tech/vnext-workflow-cli#readme","bugs":{"url":"https://github.com/burgan-tech/vnext-workflow-cli/issues"},"bin":{"wf":"bin/workflow.js","workflow":"bin/workflow.js"},"dist":{"shasum":"3256bf237ecc5a0d626d4a77367170c2c95559b6","tarball":"https://registry.npmjs.org/@burgan-tech/vnext-workflow-cli/-/vnext-workflow-cli-1.0.0.tgz","fileCount":17,"integrity":"sha512-wmZ8QiM91mzz85sz2dSmq5/H4dCx/TSioMjV3oTmj4PDlegx5f2To9QNb8E2weMR9p9gIkGy/Xg/AtCqZyPkBw==","signatures":[{"sig":"MEQCIChbr2ayqPex0m+vlupcPJ6mz0O3qCcIyXwPFokbdmp1AiBwv5SX/BiDm/1eYRXTRyi4WZGytQN8jFgBo5yaor1LuQ==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"unpackedSize":83453},"main":"dist/index.js","engines":{"node":">=14.0.0"},"gitHead":"1c7f7f0ac8d0fe42ad91ad05316c8898d3864858","scripts":{"dev":"node bin/workflow.js","build":"echo 'Build not needed for now'","start":"node bin/workflow.js"},"_npmUser":{"name":"seal707","email":"mehmet.tosun@gmail.com"},"repository":{"url":"git+https://github.com/burgan-tech/vnext-workflow-cli.git","type":"git"},"_npmVersion":"10.8.2","description":"vNext Workflow Manager - CLI tool for managing workflows, tasks, schemas and more","directories":{},"_nodeVersion":"20.19.5","dependencies":{"pg":"^8.11.3","ora":"^5.4.1","conf":"^10.2.0","glob":"^10.3.10","axios":"^1.6.2","chalk":"^4.1.2","inquirer":"^8.2.6","commander":"^11.1.0"},"_hasShrinkwrap":false,"_npmOperationalInternal":{"tmp":"tmp/vnext-workflow-cli_1.0.0_1762524012125_0.8379156945060473","host":"s3://npm-registry-packages-npm-production"}},"1.0.1":{"name":"@burgan-tech/vnext-workflow-cli","version":"1.0.1","keywords":["workflow","vnext","cli","automation"],"author":{"name":"Burgan Tech"},"license":"MIT","_id":"@burgan-tech/vnext-workflow-cli@1.0.1","maintainers":[{"name":"seal707","email":"mehmet.tosun@gmail.com"},{"name":"yilmaztayfun","email":"tayfun.yilmaz2@hotmail.com"}],"homepage":"https://github.com/burgan-tech/vnext-workflow-cli#readme","bugs":{"url":"https://github.com/burgan-tech/vnext-workflow-cli/issues"},"bin":{"wf":"bin/workflow.js","workflow":"bin/workflow.js"},"dist":{"shasum":"089f65168ebb7b6b78a83ff80e82c94361c3cc59","tarball":"https://registry.npmjs.org/@burgan-tech/vnext-workflow-cli/-/vnext-workflow-cli-1.0.1.tgz","fileCount":18,"integrity":"sha512-tZx87P+x/SZWebtGtN7vOpszGE7B416/azY50DL3VojqiZllgPIcfc2r9KaQygUKe9FrblLzzdC7grEx16kA5Q==","signatures":[{"sig":"MEUCIHH62CtFxKDqkQc2Lp7K4R+Ne2GMd4p9fR5aFIYkrFBNAiEAxjsWwr048yv/OAkgw80WP5DeTUxPvraZ8aRy5stHCfA=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"unpackedSize":83496},"main":"dist/index.js","engines":{"node":">=14.0.0"},"gitHead":"bff1461785a1a1c06c899125a43cdb1a980cea72","scripts":{"dev":"node bin/workflow.js","build":"echo 'Build not needed for now'","start":"node bin/workflow.js"},"_npmUser":{"name":"seal707","email":"mehmet.tosun@gmail.com"},"repository":{"url":"git+https://github.com/burgan-tech/vnext-workflow-cli.git","type":"git"},"_npmVersion":"10.8.2","description":"vNext Workflow Manager - CLI tool for managing workflows, tasks, schemas and more","directories":{},"_nodeVersion":"20.19.5","dependencies":{"pg":"^8.11.3","ora":"^5.4.1","conf":"^10.2.0","glob":"^10.3.10","axios":"^1.6.2","chalk":"^4.1.2","inquirer":"^8.2.6","commander":"^11.1.0"},"_hasShrinkwrap":false,"_npmOperationalInternal":{"tmp":"tmp/vnext-workflow-cli_1.0.1_1762524243242_0.40360060744015236","host":"s3://npm-registry-packages-npm-production"}},"1.0.2":{"name":"@burgan-tech/vnext-workflow-cli","version":"1.0.2","keywords":["workflow","vnext","cli","automation"],"author":{"name":"Burgan Tech"},"license":"MIT","_id":"@burgan-tech/vnext-workflow-cli@1.0.2","maintainers":[{"name":"seal707","email":"mehmet.tosun@gmail.com"},{"name":"yilmaztayfun","email":"tayfun.yilmaz2@hotmail.com"}],"homepage":"https://github.com/burgan-tech/vnext-workflow-cli#readme","bugs":{"url":"https://github.com/burgan-tech/vnext-workflow-cli/issues"},"bin":{"wf":"bin/workflow.js","workflow":"bin/workflow.js"},"dist":{"shasum":"4f8b6d32be662bf6dbe45fe7714c4c7a47faeabc","tarball":"https://registry.npmjs.org/@burgan-tech/vnext-workflow-cli/-/vnext-workflow-cli-1.0.2.tgz","fileCount":19,"integrity":"sha512-3htfolXqHRc/omEc12gslz+icv7UTlWZiBgKsV4TFassRR4oubJ3TPsDXcB7NapIhP3P3XsnnC0LDOAoRoGfYA==","signatures":[{"sig":"MEYCIQCGslBr115x/Swf1yvb/VhfQ5zS/8FUZVmcNaeCWvL0tQIhAK382y4dE63sJ3J5tx9v4laVrESs35g7zYKsyDLhleFh","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"unpackedSize":116609},"main":"dist/index.js","engines":{"node":">=14.0.0"},"gitHead":"4737f556af5799162d99af77f5796f006115c963","scripts":{"dev":"node bin/workflow.js","build":"echo 'Build not needed for now'","start":"node bin/workflow.js"},"_npmUser":{"name":"yilmaztayfun","email":"tayfun.yilmaz2@hotmail.com"},"repository":{"url":"git+https://github.com/burgan-tech/vnext-workflow-cli.git","type":"git"},"_npmVersion":"10.8.2","description":"vNext Workflow Manager - CLI tool for managing workflows, tasks, schemas and more","directories":{},"_nodeVersion":"20.19.6","dependencies":{"pg":"^8.11.3","ora":"^5.4.1","conf":"^10.2.0","glob":"^10.3.10","axios":"^1.6.2","chalk":"^4.1.2","inquirer":"^8.2.6","commander":"^11.1.0"},"_hasShrinkwrap":false,"_npmOperationalInternal":{"tmp":"tmp/vnext-workflow-cli_1.0.2_1765837106802_0.6563787810996087","host":"s3://npm-registry-packages-npm-production"}},"1.0.3":{"name":"@burgan-tech/vnext-workflow-cli","version":"1.0.3","keywords":["workflow","vnext","cli","automation"],"author":{"name":"Burgan Tech"},"license":"MIT","_id":"@burgan-tech/vnext-workflow-cli@1.0.3","maintainers":[{"name":"seal707","email":"mehmet.tosun@gmail.com"},{"name":"yilmaztayfun","email":"tayfun.yilmaz2@hotmail.com"}],"homepage":"https://github.com/burgan-tech/vnext-workflow-cli#readme","bugs":{"url":"https://github.com/burgan-tech/vnext-workflow-cli/issues"},"bin":{"wf":"bin/workflow.js","workflow":"bin/workflow.js"},"dist":{"shasum":"11980395b070818f7c7fcea1605abc048a8d4c4b","tarball":"https://registry.npmjs.org/@burgan-tech/vnext-workflow-cli/-/vnext-workflow-cli-1.0.3.tgz","fileCount":20,"integrity":"sha512-8rCUJXg66gGisr5pZN4RpJWvZDsQUWsRP1Lw+Staois794zfoo81W4K907sNm3jXgWLcHbN9sOsImGWz2KtBWQ==","signatures":[{"sig":"MEUCIQDFOsQ28O8DS0iE2r3D7dQz6IX4wPZdsj8yhXLnWxZ1MgIgf4H/j0oT9P8Avw+32MyndJT+bQUPe9/UAYuDMMtGEnE=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"unpackedSize":132612},"main":"dist/index.js","engines":{"node":">=14.0.0"},"gitHead":"c710e380c3f77dfc36e704430cdc8fe776c55ff8","scripts":{"dev":"node bin/workflow.js","build":"echo 'Build not needed for now'","start":"node bin/workflow.js"},"_npmUser":{"name":"yilmaztayfun","email":"tayfun.yilmaz2@hotmail.com"},"repository":{"url":"git+https://github.com/burgan-tech/vnext-workflow-cli.git","type":"git"},"_npmVersion":"10.8.2","description":"vNext Workflow Manager - CLI tool for managing workflows, tasks, schemas and more","directories":{},"_nodeVersion":"20.20.0","dependencies":{"pg":"^8.11.3","ora":"^5.4.1","conf":"^10.2.0","glob":"^10.3.10","axios":"^1.6.2","chalk":"^4.1.2","inquirer":"^8.2.6","commander":"^11.1.0"},"_hasShrinkwrap":false,"_npmOperationalInternal":{"tmp":"tmp/vnext-workflow-cli_1.0.3_1771976656554_0.04491203381956543","host":"s3://npm-registry-packages-npm-production"}},"1.0.4":{"name":"@burgan-tech/vnext-workflow-cli","version":"1.0.4","keywords":["workflow","vnext","cli","automation"],"author":{"name":"Burgan Tech"},"license":"MIT","_id":"@burgan-tech/vnext-workflow-cli@1.0.4","maintainers":[{"name":"seal707","email":"mehmet.tosun@gmail.com"},{"name":"yilmaztayfun","email":"tayfun.yilmaz2@hotmail.com"}],"homepage":"https://github.com/burgan-tech/vnext-workflow-cli#readme","bugs":{"url":"https://github.com/burgan-tech/vnext-workflow-cli/issues"},"bin":{"wf":"bin/workflow.js","workflow":"bin/workflow.js"},"dist":{"shasum":"bb42185bcea55555c86521e1d35b9c17d4d05906","tarball":"https://registry.npmjs.org/@burgan-tech/vnext-workflow-cli/-/vnext-workflow-cli-1.0.4.tgz","fileCount":20,"integrity":"sha512-ISc9SuaoUV1sUuQefZSr2te5g7SALeyPDT6Q1dN4JS9NP3ooNHYLSOfHJXYJ64/QDGsxmeoqyYgSwoL4toCc6w==","signatures":[{"sig":"MEUCIGWGpOeWyAdgZPijXehcc8SFUsbX5H3GJhkIUsl8jxivAiEAwgDCjqOy8HCEdOuOvLLRwCiZPOE4lctqQOkp6yxTAWI=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@burgan-tech%2fvnext-workflow-cli@1.0.4","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":126832},"main":"dist/index.js","engines":{"node":">=14.0.0"},"gitHead":"367f337a75770d62b3c698eb4d660b40c9ea4bec","scripts":{"dev":"node bin/workflow.js","build":"echo 'Build not needed for now'","start":"node bin/workflow.js"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:7fe2209c-4744-404b-9e99-81d447293136"}},"repository":{"url":"git+https://github.com/burgan-tech/vnext-workflow-cli.git","type":"git"},"_npmVersion":"11.9.0","description":"vNext Workflow Manager - CLI tool for managing workflows, tasks, schemas and more","directories":{},"_nodeVersion":"24.14.0","dependencies":{"pg":"^8.11.3","ora":"^5.4.1","conf":"^10.2.0","glob":"^10.3.10","axios":"^1.6.2","chalk":"^4.1.2","inquirer":"^8.2.6","commander":"^11.1.0"},"_hasShrinkwrap":false,"_npmOperationalInternal":{"tmp":"tmp/vnext-workflow-cli_1.0.4_1774385623789_0.8016383308165798","host":"s3://npm-registry-packages-npm-production"}},"1.0.5":{"name":"@burgan-tech/vnext-workflow-cli","version":"1.0.5","keywords":["workflow","vnext","cli","automation"],"author":{"name":"Burgan Tech"},"license":"MIT","_id":"@burgan-tech/vnext-workflow-cli@1.0.5","maintainers":[{"name":"seal707","email":"mehmet.tosun@gmail.com"},{"name":"yilmaztayfun","email":"tayfun.yilmaz2@hotmail.com"}],"homepage":"https://github.com/burgan-tech/vnext-workflow-cli#readme","bugs":{"url":"https://github.com/burgan-tech/vnext-workflow-cli/issues"},"bin":{"wf":"bin/workflow.js","workflow":"bin/workflow.js"},"dist":{"shasum":"9509c25db9108cc1f24af47da93c4e2c72a39f41","tarball":"https://registry.npmjs.org/@burgan-tech/vnext-workflow-cli/-/vnext-workflow-cli-1.0.5.tgz","fileCount":20,"integrity":"sha512-uGWjPsXMziVArnsIzXxVLQWU0Xdy6owC/rzdZ5dNSLcmkR/RHnSX8kiMopclqBeDC6yTLbXyuYGwO8zrCnL1mg==","signatures":[{"sig":"MEQCIFs2qlcx8cJyJH7i2Gs6HbsRRGzMZG285j7J9CJoFzsyAiAmg5kk+cWPqFmWMIhhsHHn2Hzg9p5AEB1ALe6hv7qSTg==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@burgan-tech%2fvnext-workflow-cli@1.0.5","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":126832},"main":"dist/index.js","engines":{"node":">=14.0.0"},"gitHead":"367f337a75770d62b3c698eb4d660b40c9ea4bec","scripts":{"dev":"node bin/workflow.js","build":"echo 'Build not needed for now'","start":"node bin/workflow.js"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:7fe2209c-4744-404b-9e99-81d447293136"}},"repository":{"url":"git+https://github.com/burgan-tech/vnext-workflow-cli.git","type":"git"},"_npmVersion":"11.9.0","description":"vNext Workflow Manager - CLI tool for managing workflows, tasks, schemas and more","directories":{},"_nodeVersion":"24.14.0","dependencies":{"pg":"^8.11.3","ora":"^5.4.1","conf":"^10.2.0","glob":"^10.3.10","axios":"^1.6.2","chalk":"^4.1.2","inquirer":"^8.2.6","commander":"^11.1.0"},"_hasShrinkwrap":false,"_npmOperationalInternal":{"tmp":"tmp/vnext-workflow-cli_1.0.5_1774385943395_0.7470226418754495","host":"s3://npm-registry-packages-npm-production"}},"1.0.6":{"name":"@burgan-tech/vnext-workflow-cli","version":"1.0.6","keywords":["workflow","vnext","cli","automation"],"author":{"name":"Burgan Tech"},"license":"MIT","_id":"@burgan-tech/vnext-workflow-cli@1.0.6","maintainers":[{"name":"seal707","email":"mehmet.tosun@gmail.com"},{"name":"yilmaztayfun","email":"tayfun.yilmaz2@hotmail.com"}],"homepage":"https://github.com/burgan-tech/vnext-workflow-cli#readme","bugs":{"url":"https://github.com/burgan-tech/vnext-workflow-cli/issues"},"bin":{"wf":"bin/workflow.js","workflow":"bin/workflow.js"},"dist":{"shasum":"7f24ec4e62fe9e3c11777b7a680b24dfd4229281","tarball":"https://registry.npmjs.org/@burgan-tech/vnext-workflow-cli/-/vnext-workflow-cli-1.0.6.tgz","fileCount":20,"integrity":"sha512-VQJ5wvA3qphzqY9Uc8Ci/S/X7oPDW83/L9weQLh3B2JqZi+9tWCdPi75K0Uwquf5o670c9G3oHhIVTj5mMtVXw==","signatures":[{"sig":"MEQCIEMu+djSWFQivwFt92HPUrvGvX8cPeR3ayY8r3uP3/X8AiARVBbVR8d6VXU0kPOlU/YMC+hifvAw0lcfNHBtAMQcEw==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@burgan-tech%2fvnext-workflow-cli@1.0.6","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":126969},"main":"dist/index.js","engines":{"node":">=14.0.0"},"gitHead":"439c5b46dba009fb01eab0eb07d02c005f877880","scripts":{"dev":"node bin/workflow.js","build":"echo 'Build not needed for now'","start":"node bin/workflow.js"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:7fe2209c-4744-404b-9e99-81d447293136"}},"repository":{"url":"git+https://github.com/burgan-tech/vnext-workflow-cli.git","type":"git"},"_npmVersion":"11.9.0","description":"vNext Workflow Manager - CLI tool for managing workflows, tasks, schemas and more","directories":{},"_nodeVersion":"24.14.0","dependencies":{"pg":"^8.11.3","ora":"^5.4.1","conf":"^10.2.0","glob":"^10.3.10","axios":"^1.6.2","chalk":"^4.1.2","inquirer":"^8.2.6","commander":"^11.1.0"},"_hasShrinkwrap":false,"_npmOperationalInternal":{"tmp":"tmp/vnext-workflow-cli_1.0.6_1774386422491_0.7418884028691775","host":"s3://npm-registry-packages-npm-production"}},"1.0.7":{"name":"@burgan-tech/vnext-workflow-cli","version":"1.0.7","keywords":["workflow","vnext","cli","automation"],"author":{"name":"Burgan Tech"},"license":"MIT","_id":"@burgan-tech/vnext-workflow-cli@1.0.7","maintainers":[{"name":"seal707","email":"mehmet.tosun@gmail.com"},{"name":"yilmaztayfun","email":"tayfun.yilmaz2@hotmail.com"}],"homepage":"https://github.com/burgan-tech/vnext-workflow-cli#readme","bugs":{"url":"https://github.com/burgan-tech/vnext-workflow-cli/issues"},"bin":{"wf":"bin/workflow.js","vnext":"bin/workflow.js","workflow":"bin/workflow.js"},"dist":{"shasum":"9202d1ffefb880c9b84a0ad47fad50bc9a1b1df3","tarball":"https://registry.npmjs.org/@burgan-tech/vnext-workflow-cli/-/vnext-workflow-cli-1.0.7.tgz","fileCount":21,"integrity":"sha512-un+lkz2LN9spDS5WLSuJQ7RDwUW6e9lWY3gqhf5cc1DAWQMxgwUrJ74vSFjwWV9YL4+XbIk38HFIzNma/KlUZQ==","signatures":[{"sig":"MEYCIQDjq5XdqR58xCR7nb4HcrJ1F/qlSctpQfgCO/rYeUOG7AIhAOGPtZmHdM7Hp0kUpB9v4TN3RHhba9d3V5vzWqycrQMF","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@burgan-tech%2fvnext-workflow-cli@1.0.7","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":132437},"main":"dist/index.js","engines":{"node":">=14.0.0"},"gitHead":"e1147687494d94470ab3678170508a076053c624","scripts":{"dev":"node bin/workflow.js","build":"echo 'Build not needed for now'","start":"node bin/workflow.js"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:7fe2209c-4744-404b-9e99-81d447293136"}},"repository":{"url":"git+https://github.com/burgan-tech/vnext-workflow-cli.git","type":"git"},"_npmVersion":"11.11.0","description":"vNext Workflow Manager - CLI tool for managing workflows, tasks, schemas and more","directories":{},"_nodeVersion":"24.14.1","dependencies":{"pg":"^8.11.3","ora":"^5.4.1","conf":"^10.2.0","glob":"^10.3.10","axios":"^1.6.2","chalk":"^4.1.2","inquirer":"^8.2.6","commander":"^11.1.0"},"_hasShrinkwrap":false,"_npmOperationalInternal":{"tmp":"tmp/vnext-workflow-cli_1.0.7_1778186209807_0.8091569154757421","host":"s3://npm-registry-packages-npm-production"}},"1.0.8":{"name":"@burgan-tech/vnext-workflow-cli","version":"1.0.8","keywords":["workflow","vnext","cli","automation"],"author":{"name":"Burgan Tech"},"license":"MIT","_id":"@burgan-tech/vnext-workflow-cli@1.0.8","maintainers":[{"name":"seal707","email":"mehmet.tosun@gmail.com"},{"name":"yilmaztayfun","email":"tayfun.yilmaz2@hotmail.com"}],"homepage":"https://github.com/burgan-tech/vnext-workflow-cli#readme","bugs":{"url":"https://github.com/burgan-tech/vnext-workflow-cli/issues"},"bin":{"wf":"bin/workflow.js","vnext":"bin/workflow.js","workflow":"bin/workflow.js"},"dist":{"shasum":"c60f313327a3b069e40beb24732db73e5cd50414","tarball":"https://registry.npmjs.org/@burgan-tech/vnext-workflow-cli/-/vnext-workflow-cli-1.0.8.tgz","fileCount":22,"integrity":"sha512-F38fa1o4tqYNR5lvC5oDagYMegTN4s+o9rob8zBz+HM0vs75r94Uu9a11qPhYmKbTE0VcPjRmLsofQio7CfSrA==","signatures":[{"sig":"MEUCIQCI4ZbsT8kMMnamTBeHO5u/6qL32nxtTuRHRzU79ZbYKgIgAQyjjSMVMXm7c/6CJmzg5b/gMLm/YvYCUvm0WHAY0WM=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@burgan-tech%2fvnext-workflow-cli@1.0.8","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":139075},"main":"dist/index.js","engines":{"node":">=14.0.0"},"gitHead":"0f696f62fbc9f152a3ffb77275c2f848aaddf3fe","scripts":{"dev":"node bin/workflow.js","build":"echo 'Build not needed for now'","start":"node bin/workflow.js"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:7fe2209c-4744-404b-9e99-81d447293136"}},"repository":{"url":"git+https://github.com/burgan-tech/vnext-workflow-cli.git","type":"git"},"_npmVersion":"11.13.0","description":"vNext Workflow Manager - CLI tool for managing workflows, tasks, schemas and more","directories":{},"_nodeVersion":"24.16.0","dependencies":{"pg":"^8.11.3","ora":"^5.4.1","conf":"^10.2.0","glob":"^10.3.10","axios":"^1.6.2","chalk":"^4.1.2","inquirer":"^8.2.6","commander":"^11.1.0"},"_hasShrinkwrap":false,"_npmOperationalInternal":{"tmp":"tmp/vnext-workflow-cli_1.0.8_1780950298704_0.995625848060756","host":"s3://npm-registry-packages-npm-production"}},"1.0.9":{"name":"@burgan-tech/vnext-workflow-cli","version":"1.0.9","keywords":["workflow","vnext","cli","automation"],"author":{"name":"Burgan Tech"},"license":"MIT","_id":"@burgan-tech/vnext-workflow-cli@1.0.9","maintainers":[{"name":"seal707","email":"mehmet.tosun@gmail.com"},{"name":"yilmaztayfun","email":"tayfun.yilmaz2@hotmail.com"}],"homepage":"https://github.com/burgan-tech/vnext-workflow-cli#readme","bugs":{"url":"https://github.com/burgan-tech/vnext-workflow-cli/issues"},"bin":{"wf":"bin/workflow.js","vnext":"bin/workflow.js","workflow":"bin/workflow.js"},"dist":{"shasum":"c6e2eeb963ad3a78134d993d5863b6b5e0f260d7","tarball":"https://registry.npmjs.org/@burgan-tech/vnext-workflow-cli/-/vnext-workflow-cli-1.0.9.tgz","fileCount":22,"integrity":"sha512-xpVFKq7NOoaJtZEm4dQeYzpwLpwDBkNSmHwnnwYWAZm79vO80mYWZgcbm+ZMJV8TpwctDWnOPicwVYYmhijIIg==","signatures":[{"sig":"MEQCIE6XgxvYFTmAUJYF4oJsuBYQ7Suhi95RWqk1OaklteKfAiAFd5qD6eFcZYE1ZNe8bcB4llFRJZN33Pym4cK2m/20FQ==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@burgan-tech%2fvnext-workflow-cli@1.0.9","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":140027},"main":"dist/index.js","engines":{"node":">=14.0.0"},"gitHead":"e82e3a38e8545d14d295e84966583c9f4e63d63d","scripts":{"dev":"node bin/workflow.js","build":"echo 'Build not needed for now'","start":"node bin/workflow.js"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:7fe2209c-4744-404b-9e99-81d447293136"}},"repository":{"url":"git+https://github.com/burgan-tech/vnext-workflow-cli.git","type":"git"},"_npmVersion":"11.13.0","description":"vNext Workflow Manager - CLI tool for managing workflows, tasks, schemas and more","directories":{},"_nodeVersion":"24.16.0","dependencies":{"pg":"^8.11.3","ora":"^5.4.1","conf":"^10.2.0","glob":"^10.3.10","axios":"^1.6.2","chalk":"^4.1.2","inquirer":"^8.2.6","commander":"^11.1.0"},"_hasShrinkwrap":false,"_npmOperationalInternal":{"tmp":"tmp/vnext-workflow-cli_1.0.9_1781121492115_0.4992426555249989","host":"s3://npm-registry-packages-npm-production"}},"1.0.10":{"name":"@burgan-tech/vnext-workflow-cli","version":"1.0.10","keywords":["workflow","vnext","cli","automation"],"author":{"name":"Burgan Tech"},"license":"MIT","_id":"@burgan-tech/vnext-workflow-cli@1.0.10","maintainers":[{"name":"seal707","email":"mehmet.tosun@gmail.com"},{"name":"yilmaztayfun","email":"tayfun.yilmaz2@hotmail.com"}],"homepage":"https://github.com/burgan-tech/vnext-workflow-cli#readme","bugs":{"url":"https://github.com/burgan-tech/vnext-workflow-cli/issues"},"bin":{"wf":"bin/workflow.js","vnext":"bin/workflow.js","workflow":"bin/workflow.js"},"dist":{"shasum":"54b714df9348dbc0dc4a9f19546d5d8870968a5a","tarball":"https://registry.npmjs.org/@burgan-tech/vnext-workflow-cli/-/vnext-workflow-cli-1.0.10.tgz","fileCount":22,"integrity":"sha512-DU2iQUpTJdLRUBaW5//c3rwBEz3VtIty1qJI6BNJVsL5Ns6WLCVR5c/xDU107XNwmYLdgv+s8vQwaO1tRHfkVA==","signatures":[{"sig":"MEQCICh1MQWAOG0A38Xvjo1HI7rVhFz+AOQaeDND/N619CQhAiAOjqzDTGV2O7gPG1iwRqVCeYKMwGkpr6xOskyZhwtJIw==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@burgan-tech%2fvnext-workflow-cli@1.0.10","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":147063},"main":"dist/index.js","engines":{"node":">=14.0.0"},"gitHead":"81f2210446cb6438c28012dfcfba295c687dd673","scripts":{"dev":"node bin/workflow.js","build":"echo 'Build not needed for now'","start":"node bin/workflow.js"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:7fe2209c-4744-404b-9e99-81d447293136"}},"repository":{"url":"git+https://github.com/burgan-tech/vnext-workflow-cli.git","type":"git"},"_npmVersion":"11.16.0","description":"vNext Workflow Manager - CLI tool for managing workflows, tasks, schemas and more","directories":{},"_nodeVersion":"24.18.0","dependencies":{"pg":"^8.11.3","ora":"^5.4.1","conf":"^10.2.0","glob":"^10.3.10","axios":"^1.6.2","chalk":"^4.1.2","inquirer":"^8.2.6","commander":"^11.1.0"},"_hasShrinkwrap":false,"_npmOperationalInternal":{"tmp":"tmp/vnext-workflow-cli_1.0.10_1784010892360_0.4803282762384484","host":"s3://npm-registry-packages-npm-production"}},"1.0.11":{"name":"@burgan-tech/vnext-workflow-cli","version":"1.0.11","keywords":["workflow","vnext","cli","automation"],"author":{"name":"Burgan Tech"},"license":"MIT","_id":"@burgan-tech/vnext-workflow-cli@1.0.11","maintainers":[{"name":"seal707","email":"mehmet.tosun@gmail.com"},{"name":"yilmaztayfun","email":"tayfun.yilmaz2@hotmail.com"}],"homepage":"https://github.com/burgan-tech/vnext-workflow-cli#readme","bugs":{"url":"https://github.com/burgan-tech/vnext-workflow-cli/issues"},"bin":{"wf":"bin/workflow.js","vnext":"bin/workflow.js","workflow":"bin/workflow.js"},"dist":{"shasum":"9eb49b0d696c17266e368c11c5dff68344e6681c","tarball":"https://registry.npmjs.org/@burgan-tech/vnext-workflow-cli/-/vnext-workflow-cli-1.0.11.tgz","fileCount":22,"integrity":"sha512-e0yQWvqz0XR9MGb/Vba4DLxt9nxW40G9nB2ibAfZFrtzJGaXuCjIzzLq477r8Y6g4NRZQXYQM1xWskQdIqoWGw==","signatures":[{"sig":"MEQCIBZrX/TQnCEPum83Nql0Va/IZPywYEwfQkZ6PXdIxVDnAiAyGDAYj+E1sL/X8+U8rDBfSFSPKLI14xkNQnCCnWa2vA==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@burgan-tech%2fvnext-workflow-cli@1.0.11","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":147238},"main":"dist/index.js","engines":{"node":">=14.0.0"},"gitHead":"b54292c3daa9658c1f1cff26fd85335646101f39","scripts":{"dev":"node bin/workflow.js","build":"echo 'Build not needed for now'","start":"node bin/workflow.js"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:7fe2209c-4744-404b-9e99-81d447293136"}},"repository":{"url":"git+https://github.com/burgan-tech/vnext-workflow-cli.git","type":"git"},"_npmVersion":"11.16.0","description":"vNext Workflow Manager - CLI tool for managing workflows, tasks, schemas and more","directories":{},"_nodeVersion":"24.18.0","dependencies":{"pg":"^8.11.3","ora":"^5.4.1","conf":"^10.2.0","glob":"^10.3.10","axios":"^1.6.2","chalk":"^4.1.2","inquirer":"^8.2.6","commander":"^11.1.0"},"_hasShrinkwrap":false,"_npmOperationalInternal":{"tmp":"tmp/vnext-workflow-cli_1.0.11_1785737876786_0.3670710239346828","host":"s3://npm-registry-packages-npm-production"}},"1.0.12":{"name":"@burgan-tech/vnext-workflow-cli","version":"1.0.12","keywords":["workflow","vnext","cli","automation"],"author":{"name":"Burgan Tech"},"license":"MIT","_id":"@burgan-tech/vnext-workflow-cli@1.0.12","maintainers":[{"name":"seal707","email":"mehmet.tosun@gmail.com"},{"name":"yilmaztayfun","email":"tayfun.yilmaz2@hotmail.com"}],"homepage":"https://github.com/burgan-tech/vnext-workflow-cli#readme","bugs":{"url":"https://github.com/burgan-tech/vnext-workflow-cli/issues"},"bin":{"wf":"bin/workflow.js","vnext":"bin/workflow.js","workflow":"bin/workflow.js"},"dist":{"shasum":"4d846834e88f7457c6c8845502233ec3ab727ac6","tarball":"https://registry.npmjs.org/@burgan-tech/vnext-workflow-cli/-/vnext-workflow-cli-1.0.12.tgz","fileCount":22,"integrity":"sha512-xZRhNeQiKo7Mw2rBsy9G6PbukhbY06rK7zxdrt9trt3m1Eb5KtIkDnA1EWLUWsXRIvtfwxLWoHAwsGdICw0i+w==","signatures":[{"sig":"MEUCIBRaAGSJY77fEpK9YhdUDyoDM6uUrGEYSkj3DBDo2j71AiEAsfp6PuilX0v9c01q+3FdZTdIAYcIgUidtKl3EC4eSK0=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@burgan-tech%2fvnext-workflow-cli@1.0.12","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":147309},"main":"dist/index.js","engines":{"node":">=14.0.0"},"gitHead":"742eb44d690ec3d1cc23d1fdf75a34727bf21172","scripts":{"dev":"node bin/workflow.js","build":"echo 'Build not needed for now'","start":"node bin/workflow.js"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:7fe2209c-4744-404b-9e99-81d447293136"}},"repository":{"url":"git+https://github.com/burgan-tech/vnext-workflow-cli.git","type":"git"},"_npmVersion":"11.17.0","description":"vNext Workflow Manager - CLI tool for managing workflows, tasks, schemas and more","directories":{},"_nodeVersion":"24.19.0","dependencies":{"pg":"^8.11.3","ora":"^5.4.1","conf":"^10.2.0","glob":"^10.3.10","axios":"^1.6.2","chalk":"^4.1.2","inquirer":"^8.2.6","commander":"^11.1.0"},"_hasShrinkwrap":false,"_npmOperationalInternal":{"tmp":"tmp/vnext-workflow-cli_1.0.12_1786568235567_0.15487575501165463","host":"s3://npm-registry-packages-npm-production"}},"1.0.13":{"name":"@burgan-tech/vnext-workflow-cli","version":"1.0.13","keywords":["workflow","vnext","cli","automation"],"author":{"name":"Burgan Tech"},"license":"MIT","_id":"@burgan-tech/vnext-workflow-cli@1.0.13","maintainers":[{"name":"seal707","email":"mehmet.tosun@gmail.com"},{"name":"yilmaztayfun","email":"tayfun.yilmaz2@hotmail.com"}],"homepage":"https://github.com/burgan-tech/vnext-workflow-cli#readme","bugs":{"url":"https://github.com/burgan-tech/vnext-workflow-cli/issues"},"bin":{"wf":"bin/workflow.js","vnext":"bin/workflow.js","workflow":"bin/workflow.js"},"dist":{"shasum":"df2dae93f8d2255161ea36bb58d56b2c16b8be14","tarball":"https://registry.npmjs.org/@burgan-tech/vnext-workflow-cli/-/vnext-workflow-cli-1.0.13.tgz","fileCount":23,"integrity":"sha512-DmPvH3Ik0K06RizgFgAuwBs0yQEde4noHMqD9aoOG546ofi6f9TeWhJuF6zZ1yny5V3633VjWry3gGlnAg9p0w==","signatures":[{"sig":"MEUCIQCm76MaQIdBGOYalHlhug8wJ3bTWc5XBvUVAIOTiwRwaAIgDMuH2eH7SqcxGBFpjYo8Yl+kzJIz9Ev6upiA/4dPM8I=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@burgan-tech%2fvnext-workflow-cli@1.0.13","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":169515},"main":"dist/index.js","engines":{"node":">=14.0.0"},"gitHead":"cedb8909f0bf15fad3b3678839049ad09a5c0e15","scripts":{"dev":"node bin/workflow.js","build":"echo 'Build not needed for now'","start":"node bin/workflow.js"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:7fe2209c-4744-404b-9e99-81d447293136"}},"repository":{"url":"git+https://github.com/burgan-tech/vnext-workflow-cli.git","type":"git"},"_npmVersion":"11.19.0","description":"vNext Workflow Manager - CLI tool for managing workflows, tasks, schemas and more","directories":{},"_nodeVersion":"24.20.0","dependencies":{"pg":"^8.11.3","ora":"^5.4.1","conf":"^10.2.0","glob":"^10.3.10","axios":"^1.6.2","chalk":"^4.1.2","inquirer":"^8.2.6","commander":"^11.1.0"},"_hasShrinkwrap":false,"_npmOperationalInternal":{"tmp":"tmp/vnext-workflow-cli_1.0.13_1788639859272_0.6757777884226888","host":"s3://npm-registry-packages-npm-production"}},"1.0.14":{"_id":"@burgan-tech/vnext-workflow-cli@1.0.14","bin":{"wf":"bin/workflow.js","vnext":"bin/workflow.js","workflow":"bin/workflow.js"},"bugs":{"url":"https://github.com/burgan-tech/vnext-workflow-cli/issues"},"dist":{"shasum":"9560477b144a3231cccfcc8d1d09d4dd015dea03","tarball":"https://registry.npmjs.org/@burgan-tech/vnext-workflow-cli/-/vnext-workflow-cli-1.0.14.tgz","fileCount":29,"integrity":"sha512-wQv6FqpaUSLiA33RKcfN7GdQl8PoxvHhxri0xTHpuMucG5cqijec6c8EZ9CckoaTcHIaH84ggWE3aSyhnEtmpg==","signatures":[{"sig":"MEYCIQCukkBmSRz6T3xMcERCfzjT18FdJrU4TQ/hO/MBOWRTmQIhALqfR9SSP8VLtGV4ID3XzpyUfPYxvnmXSxUIzBc/LPlE","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U","sig":"MEUCIQCOaJuw/DEUqp6HCX+3RukJoyrRNcGGwt+rIxkNxEbKrQIgJ3vFVNSIoIL0Syl/5p1TYQlsCKszFajwlYLrH8RkQwI="}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@burgan-tech%2fvnext-workflow-cli@1.0.14","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":229461},"main":"dist/index.js","name":"@burgan-tech/vnext-workflow-cli","author":{"name":"Burgan Tech"},"engines":{"node":">=14.0.0"},"gitHead":"7283021e91cd1ce83d37978e6421ab53be970ef7","license":"MIT","scripts":{"dev":"node bin/workflow.js","build":"echo 'Build not needed for now'","start":"node bin/workflow.js"},"version":"1.0.14","_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:7fe2209c-4744-404b-9e99-81d447293136"}},"homepage":"https://github.com/burgan-tech/vnext-workflow-cli#readme","keywords":["workflow","vnext","cli","automation"],"repository":{"url":"git+https://github.com/burgan-tech/vnext-workflow-cli.git","type":"git"},"_npmVersion":"11.19.0","description":"vNext Workflow Manager - CLI tool for managing workflows, tasks, schemas and more","directories":{},"maintainers":[{"name":"seal707","email":"mehmet.tosun@gmail.com"},{"name":"yilmaztayfun","email":"tayfun.yilmaz2@hotmail.com"}],"_nodeVersion":"24.21.0","dependencies":{"pg":"^8.11.3","ora":"^5.4.1","conf":"^10.2.0","glob":"^10.3.10","axios":"^1.6.2","chalk":"^4.1.2","inquirer":"^8.2.6","commander":"^11.1.0"},"_hasShrinkwrap":false,"_npmOperationalInternal":{"host":"s3://npm-registry-packages-npm-production","tmp":"tmp/vnext-workflow-cli_1.0.14_1790272602728_0.24208206442979052"}}},"time":{"created":"2025-11-07T14:00:12.034Z","modified":"2026-09-24T17:56:43.184Z","1.0.0":"2025-11-07T14:00:12.347Z","1.0.1":"2025-11-07T14:04:03.426Z","1.0.2":"2025-12-15T22:18:26.934Z","1.0.3":"2026-02-24T23:44:16.742Z","1.0.4":"2026-03-24T20:53:43.959Z","1.0.5":"2026-03-24T20:59:03.604Z","1.0.6":"2026-03-24T21:07:02.663Z","1.0.7":"2026-05-07T20:36:50.038Z","1.0.8":"2026-06-08T20:24:58.857Z","1.0.9":"2026-06-10T19:58:12.247Z","1.0.10":"2026-07-14T06:34:52.506Z","1.0.11":"2026-08-03T06:17:56.938Z","1.0.12":"2026-08-12T20:57:15.702Z","1.0.13":"2026-09-05T20:24:19.409Z","1.0.14":"2026-09-24T17:56:42.822Z"},"bugs":{"url":"https://github.com/burgan-tech/vnext-workflow-cli/issues"},"author":{"name":"Burgan Tech"},"license":"MIT","homepage":"https://github.com/burgan-tech/vnext-workflow-cli#readme","keywords":["workflow","vnext","cli","automation"],"repository":{"url":"git+https://github.com/burgan-tech/vnext-workflow-cli.git","type":"git"},"description":"vNext Workflow Manager - CLI tool for managing workflows, tasks, schemas and more","maintainers":[{"name":"seal707","email":"mehmet.tosun@gmail.com"},{"name":"yilmaztayfun","email":"tayfun.yilmaz2@hotmail.com"}],"readme":"# 🚀 vNext Workflow CLI\n\nCross-platform modern workflow management tool.\n\n[![npm version](https://img.shields.io/npm/v/@burgan-tech/vnext-workflow-cli.svg)](https://www.npmjs.com/package/@burgan-tech/vnext-workflow-cli)\n[![npm downloads](https://img.shields.io/npm/dm/@burgan-tech/vnext-workflow-cli.svg)](https://www.npmjs.com/package/@burgan-tech/vnext-workflow-cli)\n[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)\n\nA command-line interface (CLI) tool for managing vNext workflows, tasks, schemas, views, functions, extensions, and mappings. This tool helps you synchronize your local workflow definitions with the vNext API and database.\n\n**Package**: `@burgan-tech/vnext-workflow-cli`  \n**NPM**: https://www.npmjs.com/package/@burgan-tech/vnext-workflow-cli  \n**GitHub**: https://github.com/burgan-tech/vnext-workflow-cli\n\n## 📦 Installation\n\n### Install from NPM (Recommended)\n\n```bash\n# Install globally\nnpm install -g @burgan-tech/vnext-workflow-cli\n\n# Or install as a project dependency\nnpm install @burgan-tech/vnext-workflow-cli\n```\n\nAfter installation, you can use the CLI with any of these aliases:\n```bash\nwf --version       # short alias\nvnext --version    # alternative alias (recommended for Windows)\nworkflow --version # full name\n```\n\n### Install from Source\n\n```bash\n# Clone the repository\ngit clone https://github.com/burgan-tech/vnext-workflow-cli.git\ncd vnext-workflow-cli\n\n# Install dependencies\nnpm install\n\n# Link globally (for development)\nnpm link\n```\n\n### Requirements\n\n- Node.js >= 14.0.0\n- npm or yarn\n- PostgreSQL (for database operations)\n- Docker (optional, for PostgreSQL container)\n\n---\n\n## 📄 vnext.config.json (Required)\n\nEvery vNext workspace must have at least one **solution file** in the **project root**. The default solution file is `vnext.config.json`; a workspace that hosts several domains adds one `vnext.{domain}.config.json` per extra domain (see [Multiple solutions in one workspace](#multiple-solutions-in-one-workspace)). A solution file defines the domain and component paths.\n\n### Example Configuration\n\n```json\n{\n  \"version\": \"1.0.0\",\n  \"domain\": \"core\",\n  \"paths\": {\n    \"componentsRoot\": \"core\",\n    \"tasks\": \"Tasks\",\n    \"views\": \"Views\",\n    \"functions\": \"Functions\",\n    \"extensions\": \"Extensions\",\n    \"workflows\": \"Workflows\",\n    \"schemas\": \"Schemas\",\n    \"mappings\": \"Mappings\"\n  }\n}\n```\n\n### Key Properties\n\n| Property | Description |\n|----------|-------------|\n| `domain` | Domain name of this solution. Must match a CLI domain profile (`wf domain add <name>`) and the `domain` field of every component under this solution |\n| `paths.componentsRoot` | Root folder where all components are located |\n| `paths.tasks` | Tasks folder name under componentsRoot |\n| `paths.workflows` | Workflows folder name under componentsRoot |\n| `paths.schemas` | Schemas folder name under componentsRoot |\n| `paths.views` | Views folder name under componentsRoot |\n| `paths.functions` | Functions folder name under componentsRoot |\n| `paths.extensions` | Extensions folder name under componentsRoot |\n| `paths.mappings` | Mappings folder name under componentsRoot |\n\n### Component Discovery\n\nThe CLI scans `componentsRoot` recursively and:\n- Includes all `.json` files in subfolders\n- Ignores `.meta` folders\n- Ignores `*.diagram.json` files\n- Ignores `package*.json` and `*config*.json` files\n\n### Multiple solutions in one workspace\n\nA single workspace can hold several domains side by side. Each domain gets its own solution file in the project root and its own `componentsRoot`:\n\n```\nmy-workspace/\n├── vnext.config.json            # domain \"core\"     → componentsRoot \"core\"\n├── vnext.partner.config.json    # domain \"partner\"  → componentsRoot \"partner\"\n├── core/\n│   ├── Workflows/ …\n│   └── Tasks/ …\n└── partner/\n    ├── Workflows/ …\n    └── Views/ …\n```\n\nRules:\n\n- **File name:** `vnext.config.json` (default) or `vnext.{domain}.config.json`. The `{domain}` part is only used to find the file; the **`domain` field inside the file is authoritative**. If the two differ, a warning is printed and the field wins.\n- **Separate folders:** every solution points at its own `paths.componentsRoot`. Discovery, `--file`, `--folder` and Git-changed detection are all scoped to that folder.\n- **Profiles:** each solution's `domain` is looked up in the CLI domain profiles (`wf domain list`). A solution with no matching profile is **skipped with a warning** by `check`/`sync`/`update`/`reset` (`csx` needs no profile and always runs).\n- **Component domain check:** every component JSON must carry a `domain` equal to its solution's `domain`. A missing or different value fails that component with `DOMAIN_MISMATCH`; the rest of the batch continues.\n- **Sequential processing:** with no `--domain` option, every workspace command runs once per solution, in order, each under its own banner, followed by a `WORKSPACE SUMMARY` and a combined error table with a `Domain` column.\n- **`--domain <name>`:** global option that restricts any command to one solution. Works before or after the command name (`wf update --domain partner`, `wf --domain partner update`).\n- **Duplicate domains:** two solution files declaring the same `domain` are both rejected.\n\n---\n\n## ⚡ Quick Start\n\n### Initial Configuration\n\nAfter installation, navigate to your vNext project and run:\n\n```bash\n# Go to your vNext project directory\ncd /path/to/your/vnext-project\n\n# Database settings (if using Docker)\nwf config set USE_DOCKER true\nwf config set DOCKER_POSTGRES_CONTAINER vnext-postgres\n\n# Verify configuration\nwf check\n```\n\n**Note:** The CLI automatically uses the current working directory as the project root. Just `cd` into your project folder before running commands.\n\n> **Tip:** All examples use `wf` but you can also use `vnext` or `workflow` interchangeably. The `vnext` alias is recommended on Windows where `wf` may conflict with existing system commands.\n\n### Basic Usage\n\n```bash\n# System status check\nwf check\n\n# Update CSX + JSON files (automatically finds changed files)\nwf update\n\n# Add missing workflows to database\nwf sync\n\n# Reset workflows (delete from DB and re-add)\nwf reset\n```\n\n---\n\n## 📖 Commands\n\nAll workspace commands (`check`, `csx`, `sync`, `update`, `reset`) accept the global `--domain <name>` option. Without it they run once per solution file found in the project root.\n\n### `wf indexes generate`\n\n**Purpose**: Generate offline attribute-index SQL for planned execution by your DBA team.\n\nFrom a domain workspace containing `vnext.config.json`:\n\n```bash\nwf indexes generate --output ./index-sql\nwf indexes generate --flow money-transfer --output ./index-sql\n```\n\nEach invocation writes a **new batch folder** containing one `.sql` per workflow, a `manifest.json`\n(source paths, versions, SHA-256 checksums, physical index definitions), and execution notes. Earlier\nbatches are preserved. The command never connects to API/DB and never executes SQL; `sync`, `update`\nand Master publication do not invoke it.\n\nThe generator resolves local workflow → Master references from the configured component directories.\nAll local versions of a workflow contribute requirements. Full `-pkg.` revisions remain pinned; `latest`,\nartifact, minor and major selectors use runtime version ordering. Build metadata is ignored. Referenced\nschemas must exist locally; incomplete references, duplicate versions and incompatible types fail.\n\nIndexed fields use `x-indexed: true`. Nested scalar string/number/integer/boolean fields are supported;\ndates use `format: \"date-time\"`. Filtering/sorting permissions remain `x-filterOperators`/`x-sortable`.\nThe generator preserves the runtime `v1:latest` column/key contract; readable index names include a hash\nof their physical definition.\n\nThe DBA reviews and executes each SQL file in a maintenance window:\n\n```bash\npsql -X -v ON_ERROR_STOP=1 --dbname=vNext_MyDomainDb --file=index-sql/<batch>/money_transfer.sql\n```\n\nSQL takes an advisory lock plus an **ACCESS EXCLUSIVE table lock**.\nIt validates current/history data, adds stored generated columns in one table rewrite, reuses structurally\nmatching indexes (including legacy names), rebuilds changed owned indexes, and updates the runtime ready\ncatalog atomically. Index comparison covers keys, includes, ordering, collation, access method, operator\nclasses and partial predicates. Unmanaged collisions abort; no `CASCADE` is issued. Replaying an unchanged\nbatch preserves index OIDs and skips data validation, rewrites and ANALYZE. Missing/invalid values are not\nsilently coerced; conversion errors identify the field and roll back all changes.\n\nThis is **not concurrent DDL**. Plan disk/WAL/replica capacity for generated-column rewrites; the script's\n5-second lock timeout may be adjusted during DBA review. Text-search indexes require `pg_trgm` in `public`\nand `tr-TR-x-icu`. Runtime routing uses `AttributeIndexes:Enabled`; catalog refresh defaults to 30 seconds.\n\nObsolete projections are retained by default for other deployed versions. To explicitly retire them:\n\n```bash\nwf indexes generate --flow money-transfer --retire-obsolete\n```\n\nInclude **every still-active workflow version** locally and drain readers/writers for this maintenance.\nRetirement removes obsolete expressions/owned indexes and marks catalog entries not ready; columns and\nstored values remain. This is required when an old numeric/date cast would reject values after a type\nchange. The offline tool cannot verify deployed versions: compare the source manifest before execution.\nRoll back query routing through the runtime's `AttributeIndexes:DisabledFlows`; schedule physical cleanup\nseparately. See the runtime [maintenance runbook](https://github.com/burgan-tech/vnext/blob/main/docs/runtime/manual-attribute-index-maintenance.md).\n\n**Tests (Node 18+ test runner):**\n\n```bash\nnode --test test/indexes.test.js\n# Use only a disposable PostgreSQL database; the test owns uniquely named fixture schemas.\nVNEXT_INDEX_TEST_URL=postgresql://user:password@localhost:5432/disposable_test \\\n  node --test test/indexes.postgres.test.js\n```\n\n---\n\n### `wf check`\n\n**Purpose**: System health check\n\nFor every solution, checks and displays:\n- Solution file status, domain and components root\n- API connection status (skipped with a `wf domain add` hint when the domain has no CLI profile)\n- Database connection status\n- Component folders found\n\n```bash\nwf check                   # every solution in the workspace\nwf check --domain partner  # one solution\n```\n\n---\n\n### `wf sync`\n\n**Purpose**: Add missing components to database (skip existing)\n\n**What it does**:\n1. Scans all CSX files and updates JSON files with base64 encoded content\n2. For each component JSON file:\n   - Checks if it exists in DB (by key)\n   - If **exists** → Skip (already synced)\n   - If **not exists** → Publish to API\n3. Signals `definitions/publish/completed` once — the runtime's post-deployment hook\n\n**Use when**: Initial setup, adding new components without affecting existing ones\n\n```bash\nwf sync\n```\n\n---\n\n### Publish-completed\n\n`sync`, `update` and `reset` each end with one call to the runtime:\n\n```\nPOST {baseUrl}/api/{version}/definitions/publish/completed\n```\n\nIt runs the runtime's post-deployment hooks once per command. Today that means forcing a re-read of\nthe domain discovery registry — and that matters more than it looks: the runtime's discovery endpoint\ncache carries **no TTL**, so this call is its only automatic invalidation. Without it a runtime keeps\nresolving cross-domain calls by whatever it learned at startup, until its pod restarts.\n\nThe response is always HTTP 200; a failed hook is reported in the body, and the CLI prints each\nhook's outcome:\n\n```\n✔ Publish-completed ran 1 hook(s)\n    discovery-cache: Refreshed\n```\n\n`Refreshed` is the normal outcome. `SkippedNotOwner` is also fine — another replica is reading the\nregistry and its result applies cluster-wide. `Disabled` means that runtime has no discovery cache\n(`ServiceDiscovery:Provider=dapr`, or the cache switched off). `Failed` means the registry could not\nbe read and nothing else will retry it.\n\n> **Requires a runtime that exposes `definitions/publish/completed`.** It replaces\n> `definitions/re-initialize`, which older runtimes served as a no-op and current ones have removed.\n> Against an older runtime this call 404s and the CLI prints the warning above without failing the\n> command.\n\n---\n\n### `wf update [options]`\n\n**Purpose**: Update changed components (delete + re-add)\n\n**What it does**:\n1. Finds changed CSX files (Git) and updates JSON files\n2. For each component JSON file:\n   - Checks if it exists in DB (by key)\n   - If **exists** → Delete from DB, then publish to API\n   - If **not exists** → Publish to API\n3. Signals `definitions/publish/completed` once — the runtime's post-deployment hook\n\n**Use when**: You modified existing components and want to update them\n\n```bash\nwf update                          # Process changed files in Git (CSX + JSON), every solution\nwf update --all                    # Update all (asks for confirmation once, for all domains)\nwf update --file x.json            # Process a single file (its solution is derived from the path)\nwf update --folder person          # Process every component under a feature folder, ignoring Git\nwf update --domain partner --all   # Only the \"partner\" solution\n```\n\nIn a multi-solution workspace `--file` is routed to the solution whose `componentsRoot` contains the file; combining it with a different `--domain` is an error. `--folder` is resolved inside each solution separately (an exact path is only accepted inside that solution's `componentsRoot`).\n\n**`--folder <name>` (`-d`)**: Updates every component belonging to a feature, across all component types, regardless of Git status. It resolves `<name>` in two ways:\n- **Feature name** (e.g. `person`): matches `<name>` under every component-type root (`Workflows/person`, `Tasks/person`, `Views/person`, `Schemas/person`, …) and updates all of them together.\n- **Exact path** (e.g. `Workflows/person` or an absolute path): updates only that specific folder.\n\nIf nothing matches, the command lists the feature folder names it did find so you can correct a typo. `--file` takes precedence over `--folder`, which takes precedence over `--all`.\n\n```bash\nwf update --folder person          # Every \"person\" folder across all component types\nwf update -d Workflows/person      # Only Workflows/person\n```\n\n---\n\n### `wf reset`\n\n**Purpose**: Force reset components (always delete + re-add)\n\n**What it does**:\n1. Shows interactive menu to select component type\n2. For each component JSON file:\n   - Checks if it exists in DB (by key)\n   - If **exists** → Delete from DB, then publish to API\n   - If **not exists** → Publish to API\n3. Signals `definitions/publish/completed` once — the runtime's post-deployment hook\n\n**Use when**: You need to force reset components regardless of changes\n\n```bash\nwf reset                 # Select folder from interactive menu\nwf reset --domain core   # Skip the domain picker in a multi-solution workspace\n```\n\nIn a workspace with several solution files, `wf reset` first asks **which domain** to reset (unless `--domain` is given), then shows the folder menu for that solution.\n\n**Menu Options**:\n```\n? Which folder should be reset?\n❯ tasks (Tasks/)\n  views (Views/)\n  functions (Functions/)\n  extensions (Extensions/)\n  workflows (Workflows/)\n  schemas (Schemas/)\n  mappings (Mappings/)\n  ──────────────\n  TUMU (All folders)\n```\n\n---\n\n### `wf csx [options]`\n\n**Purpose**: Convert CSX files to Base64 and embed in JSON files\n\n**What it does**:\n1. Finds CSX files (changed or all)\n2. Converts to Base64\n3. Updates ALL JSON files that reference the CSX file\n4. Updates ALL matching `location` references in each JSON\n\n**Use when**: You only want to update CSX content in JSONs without publishing to API\n\n```bash\nwf csx                       # Process changed files in Git, every solution\nwf csx --all                 # Process all CSX files\nwf csx --file x.csx          # Process a single file\nwf csx --domain partner      # Only the \"partner\" solution\n```\n\n`csx` does not need a CLI domain profile, so it also runs for solutions whose domain has no profile yet.\n\n---\n\n### `wf config <action> [key] [value]`\n\n**Purpose**: Configuration management\n\n```bash\nwf config get              # Show all settings (active domain)\nwf config get PROJECT_ROOT # Show a specific setting\nwf config set DB_PASSWORD pass # Change a setting (on active domain)\n```\n\n**Note:** `config get` and `config set` always operate on the **active domain**. Use `wf domain use <name>` to switch domains.\n\n---\n\n### `wf domain [action] [name] [options]`\n\n**Purpose**: Multidomain management\n\nManage multiple domain configurations (API/DB connection profiles). Workspace commands pick the profile whose name equals each solution's `domain`; `wf config get/set` operate on the **active** domain (`wf domain use`).\n\n```bash\n# Show active domain name\nwf domain active\n\n# List all domains\nwf domain list\nwf domain --list\n\n# Add a new domain\nwf domain add staging --API_BASE_URL http://staging.example.com:4201 --DB_NAME vNext_StagingDb\n\n# Add a domain with multiple settings\nwf domain add production \\\n  --API_BASE_URL http://prod.example.com:4201 \\\n  --DB_NAME vNext_ProdDb \\\n  --DB_HOST prod-db.example.com \\\n  --DB_USER prod_user \\\n  --DB_PASSWORD prod_pass\n\n# Switch active domain\nwf domain use staging\n\n# Remove a domain\nwf domain remove staging\n```\n\n**Notes:**\n- When adding a domain, any unspecified settings are inherited from the `default` domain.\n- The `default` domain cannot be removed.\n- If the active domain is removed, the CLI automatically switches to `default`.\n\n---\n\n## ⚙️ Configuration Variables\n\nConfig file location: `~/.config/vnext-workflow-cli/config.json`\n\n### Config File Format\n\nThe config file uses a domain-aware structure. Each domain has its own set of configuration values:\n\n```json\n{\n  \"ACTIVE_DOMAIN\": \"default\",\n  \"DOMAINS\": [\n    {\n      \"DOMAIN_NAME\": \"default\",\n      \"AUTO_DISCOVER\": true,\n      \"API_BASE_URL\": \"http://localhost:4201\",\n      \"API_VERSION\": \"v1\",\n      \"DB_HOST\": \"localhost\",\n      \"DB_PORT\": 5432,\n      \"DB_NAME\": \"vNext_WorkflowDb\",\n      \"DB_USER\": \"postgres\",\n      \"DB_PASSWORD\": \"postgres\",\n      \"USE_DOCKER\": false,\n      \"DOCKER_POSTGRES_CONTAINER\": \"vnext-postgres\",\n      \"DEBUG_MODE\": false\n    }\n  ]\n}\n```\n\n### All Available Settings (Per Domain)\n\n| Variable | Default | Description |\n|----------|---------|-------------|\n| `PROJECT_ROOT` | `process.cwd()` | **Auto.** Always uses current working directory (cannot be changed) |\n| `AUTO_DISCOVER` | `true` | Enable automatic component folder discovery |\n| `API_BASE_URL` | `http://localhost:4201` | vNext API base URL |\n| `API_VERSION` | `v1` | API version |\n| `DB_HOST` | `localhost` | PostgreSQL host |\n| `DB_PORT` | `5432` | PostgreSQL port |\n| `DB_NAME` | `vNext_WorkflowDb` | PostgreSQL database name |\n| `DB_USER` | `postgres` | PostgreSQL username |\n| `DB_PASSWORD` | `postgres` | PostgreSQL password |\n| `USE_DOCKER` | `false` | Use Docker for PostgreSQL connection |\n| `DOCKER_POSTGRES_CONTAINER` | `vnext-postgres` | Docker container name for PostgreSQL |\n| `DEBUG_MODE` | `false` | Enable debug logging |\n\n**Note:** `PROJECT_ROOT` is always the current working directory (`process.cwd()`). Simply `cd` into your project folder before running any command.\n\n### Quick Setup Examples\n\n```bash\n# API settings (applied to active domain)\nwf config set API_BASE_URL http://localhost:4201\nwf config set API_VERSION v1\n\n# Database settings (direct connection)\nwf config set DB_HOST localhost\nwf config set DB_PORT 5432\nwf config set DB_NAME vNext_WorkflowDb\nwf config set DB_USER postgres\nwf config set DB_PASSWORD your_password\nwf config set USE_DOCKER false\n\n# Database settings (Docker)\nwf config set USE_DOCKER true\nwf config set DOCKER_POSTGRES_CONTAINER vnext-postgres\n\n# Other settings\nwf config set AUTO_DISCOVER true\nwf config set DEBUG_MODE false\n```\n\n---\n\n## 💡 Usage Scenarios\n\n### 1. First Time Setup\n```bash\n# Go to your vNext project\ncd /path/to/project\n\n# Check system status\nwf check\n\n# Sync all components (add missing ones)\nwf sync\n```\n\n### 2. Daily Development - Changed Files\n```bash\n# Edit CSX or JSON files\nvim MyTask.csx\n\n# Update only changed components\nwf update\n```\n\n### 3. Update All Components\n```bash\n# Force update all components\nwf update --all\n```\n\n### 4. Reset Specific Component Type\n```bash\n# Interactive menu\nwf reset\n```\n\n### 5. Only Update CSX in JSONs (No API)\n```bash\n# Update CSX content in JSON files without publishing\nwf csx\n```\n\n### 5b. Update a Whole Feature Folder (No Git Needed)\n```bash\n# Update every \"person\" component across Workflows/, Tasks/, Views/, Schemas/, ...\nwf update --folder person\n\n# Or target one exact folder\nwf update --folder Workflows/person\n```\n\n### 6. Multidomain Workflow\n```bash\n# Add domain profiles (one-time setup)\nwf domain add core    --API_BASE_URL http://localhost:4201 --DB_NAME vNext_Core\nwf domain add partner --API_BASE_URL http://localhost:4221 --DB_NAME vNext_Partner\n\n# One workspace, two solution files\ncd ~/projects/my-workspace   # vnext.config.json (\"core\") + vnext.partner.config.json (\"partner\")\nwf check                     # both domains, each with its own banner\nwf update                    # git-changed files of core, then of partner\nwf update --domain partner   # only partner\n\n# Separate workspaces still work exactly as before\ncd ~/projects/core-app       # vnext.config.json has \"domain\": \"core\"\nwf update                    # uses the \"core\" profile\n\n# See all profiles\nwf domain list\n```\n\n---\n\n## 🔄 Command Comparison\n\n| Command | DB Check | Existing Action | New Action | Use Case |\n|---------|----------|-----------------|------------|----------|\n| `sync` | Yes | Skip | Publish | Add missing components |\n| `update` | Yes | Delete + Publish | Publish | Update changed components |\n| `update --folder <name>` | Yes | Delete + Publish | Publish | Update every component in a feature folder (ignores Git) |\n| `reset` | Yes | Delete + Publish | Publish | Force reset components |\n| `csx` | No | N/A | N/A | Only update CSX in JSONs |\n\n---\n\n## 🔀 Multidomain Support\n\n### Overview\n\nThe CLI supports managing multiple domain configurations. Each domain has its own `API_BASE_URL`, `DB_NAME`, and other settings, stored as a **domain profile**. A workspace may contain one or many solution files, and each solution is processed with the profile that matches its `domain`.\n\n### Solution → Profile Resolution\n\nBefore a workspace command runs, the CLI:\n\n1. Lists the solution files in the current directory: `vnext.config.json` plus every `vnext.{domain}.config.json`.\n2. Reads the `domain` field of each one.\n3. Looks up a CLI domain profile with the same name (`DOMAINS[].DOMAIN_NAME`).\n4. Runs the command once per solution, sequentially, with that profile's API/DB settings. A solution without a profile is skipped with a hint:\n   ```\n   ⚠ No CLI domain profile for \"partner\" — skipped.\n       Run: wf domain add partner --API_BASE_URL <url> --DB_NAME <db>\n   ```\n\n`ACTIVE_DOMAIN` is **not** changed by running commands in a workspace. It only affects `wf domain active` and `wf config get/set`. Use `--domain <name>` to restrict a command to a single solution.\n\n> **Upgrading from 1.x:** earlier versions rewrote `ACTIVE_DOMAIN` to the workspace's domain on every command (\"auto domain resolution\"). That side effect is gone; `wf config get` now always shows the domain you last selected with `wf domain use`.\n\n**Example:** two profiles, two solutions in one workspace:\n```bash\nwf domain add core    --DB_NAME vNext_Core\nwf domain add partner --DB_NAME vNext_Partner\n\ncd ~/projects/my-workspace    # vnext.config.json (core) + vnext.partner.config.json (partner)\nwf update                     # core with the \"core\" profile, then partner with the \"partner\" profile\n```\n\n### Backward Compatibility\n\n- Existing single-domain configurations are automatically migrated to the new format.\n- A `default` domain is created with your existing settings.\n- If you don't use multidomain features, everything works exactly as before.\n- All `wf config get/set` commands continue to work (they operate on the active domain).\n\n### Migration\n\nWhen upgrading from an older version, the CLI automatically migrates the config file:\n\n**Before (old flat format):**\n```json\n{\n  \"API_BASE_URL\": \"http://localhost:4201\",\n  \"DB_NAME\": \"vNext_WorkflowDb\"\n}\n```\n\n**After (new domain-aware format):**\n```json\n{\n  \"ACTIVE_DOMAIN\": \"default\",\n  \"DOMAINS\": [\n    {\n      \"DOMAIN_NAME\": \"default\",\n      \"AUTO_DISCOVER\": true,\n      \"API_BASE_URL\": \"http://localhost:4201\",\n      \"API_VERSION\": \"v1\",\n      \"DB_HOST\": \"localhost\",\n      \"DB_PORT\": 5432,\n      \"DB_NAME\": \"vNext_WorkflowDb\",\n      \"DB_USER\": \"postgres\",\n      \"DB_PASSWORD\": \"postgres\",\n      \"USE_DOCKER\": false,\n      \"DOCKER_POSTGRES_CONTAINER\": \"vnext-postgres\",\n      \"DEBUG_MODE\": false\n    }\n  ]\n}\n```\n\nYour existing values are preserved. Any missing keys are filled in from defaults (11 keys total).\n\nNo manual action is required. The migration happens automatically on first run.\n\n### Domain Commands\n\n| Command | Description |\n|---------|-------------|\n| `wf domain active` | Show active domain name |\n| `wf domain list` | List all domains with active indicator |\n| `wf domain --list` | List all domains (shorthand) |\n| `wf domain add <name> [options]` | Add a new domain |\n| `wf domain use <name>` | Switch active domain |\n| `wf domain remove <name>` | Remove a domain |\n\n### Available Options for `wf domain add`\n\n| Option | Description |\n|--------|-------------|\n| `--API_BASE_URL <url>` | API base URL |\n| `--API_VERSION <version>` | API version |\n| `--DB_HOST <host>` | Database host |\n| `--DB_PORT <port>` | Database port |\n| `--DB_NAME <name>` | Database name |\n| `--DB_USER <user>` | Database user |\n| `--DB_PASSWORD <password>` | Database password |\n| `--AUTO_DISCOVER <true/false>` | Auto discover components |\n| `--USE_DOCKER <true/false>` | Use Docker for DB |\n| `--DOCKER_POSTGRES_CONTAINER <name>` | Docker container name |\n| `--DEBUG_MODE <true/false>` | Debug mode |\n\nUnspecified options inherit from the `default` domain.\n\n---\n\n## 🆘 Troubleshooting\n\n### \"vnext.config.json not found\"\n```bash\n# Make sure you're in the correct directory\npwd\n\n# Check if vnext.config.json exists\nls -la vnext.config.json\n\n# Check current working directory\nwf config get PROJECT_ROOT\n```\n\n### \"Files not found\" (When using on another PC)\n```bash\n# Just cd into the project directory\ncd /Users/NewUser/path/to/project\n\n# Verify\nwf check\n```\n\n**Note:** No need to set PROJECT_ROOT - just `cd` into your project folder.\n\n### \"No CLI domain profile for … — skipped\"\nThe solution's `domain` has no matching profile. Create one:\n```bash\nwf domain add <domain> --API_BASE_URL http://localhost:4201 --DB_NAME <db>\nwf domain list\n```\n\n### \"DOMAIN_MISMATCH\" in the error table\nA component's `domain` field is missing or differs from the `domain` of the solution file whose `componentsRoot` contains it. Fix the component's `domain` (or move the file to the right solution folder) and re-run.\n\n### \"Domain \"x\" not found in this workspace\"\n`--domain` names a domain that no solution file in the current directory declares. The message lists the available domains.\n\n### \"Cannot connect to API\"\n```bash\n# Check API\ncurl http://localhost:4201/api/v1/health\n\n# Check config\nwf config get API_BASE_URL\n```\n\n### \"Database connection failed\"\n```bash\n# Check Docker container\ndocker ps | grep postgres\n\n# Start container\ndocker start vnext-postgres\n\n# Check config\nwf config get USE_DOCKER\nwf config get DOCKER_POSTGRES_CONTAINER\n```\n\n### \"npm link not working\"\n```bash\n# Use alias (wf or vnext)\necho 'alias wf=\"node $(pwd)/bin/workflow.js\"' >> ~/.bashrc\necho 'alias vnext=\"node $(pwd)/bin/workflow.js\"' >> ~/.bashrc\nsource ~/.bashrc\n```\n\n---\n\n## 🚀 Creating a New Version\n\nThe project uses automated versioning and publishing via GitHub Actions. Follow these steps to create and publish a new version:\n\n### Method 1: Using Release Branches (Recommended)\n\n1. **Create a release branch** following the pattern `release-vX.Y`:\n   ```bash\n   git checkout -b release-v1.0\n   git push origin release-v1.0\n   ```\n\n2. **Push to the release branch** - The workflow will automatically:\n   - Calculate the next patch version (e.g., `1.0.0`, `1.0.1`, `1.0.2`)\n   - Build and validate the package\n   - Publish to NPM and/or GitHub Packages\n   - Create a Git tag (e.g., `v1.0.0`)\n   - Create a GitHub release\n\n### Method 2: Manual Workflow Dispatch\n\n1. **Go to GitHub Actions** in your repository\n2. **Select \"Build and Publish to NPM\"** workflow\n3. **Click \"Run workflow\"**\n4. **Configure options**:\n   - **Version Override**: Optional. Leave empty for auto-calculation (e.g., `1.0.6`)\n   - **Force Publish**: Set to `true` if you want to republish an existing version\n   - **Target Registry**: Choose `npmjs`, `github`, or `both`\n5. **Click \"Run workflow\"**\n\n### Version Calculation\n\nThe workflow automatically calculates versions:\n\n- **From branch name**: If branch is `release-v1.0`, it will find the next available patch version (e.g., `1.0.0`, `1.0.1`, `1.0.2`)\n- **From package.json**: If branch doesn't match the pattern, it increments the patch version from `package.json`\n\n### After Publishing\n\nOnce published, the new version will be:\n- ✅ Available on NPM: `npm install -g @burgan-tech/vnext-workflow-cli@1.0.0`\n- ✅ Tagged in Git: `v1.0.0`\n- ✅ Released on GitHub with release notes\n\n### Workflow Requirements\n\nThe workflow requires these secrets to be configured in GitHub repository settings:\n\n- **NPM_TOKEN** (optional): For publishing to NPM. If not set, only GitHub Packages will be used.\n- **SONAR_TOKEN** (optional): For code quality analysis\n- **SONAR_HOST_URL** (optional): SonarQube server URL\n\n### Workflow Steps\n\nThe build and publish workflow performs these steps:\n\n1. ✅ **Checkout code** with full Git history\n2. ✅ **Calculate version** from branch or package.json\n3. ✅ **Validate syntax** - Checks all JavaScript files\n4. ✅ **Run linting** (if available)\n5. ✅ **Run tests** (if available)\n6. ✅ **Build package** (if build script exists)\n7. ✅ **Publish to registry** (NPM and/or GitHub Packages)\n8. ✅ **Create Git tag** (e.g., `v1.0.0`)\n9. ✅ **Create GitHub release** with release notes\n\n---\n\n## 📋 Development\n\n### Project Structure\n\n```\nvnext-workflow-cli/\n├── bin/\n│   └── workflow.js          # CLI entry point\n├── src/\n│   ├── commands/            # Command implementations\n│   │   ├── check.js\n│   │   ├── config.js\n│   │   ├── csx.js\n│   │   ├── domain.js        # Multidomain management\n│   │   ├── reset.js\n│   │   ├── sync.js\n│   │   └── update.js\n│   └── lib/                 # Library modules\n│       ├── api.js           # API client (publish, publish-completed)\n│       ├── config.js        # CLI configuration\n│       ├── csx.js           # CSX processing\n│       ├── db.js            # Database operations\n│       ├── discover.js      # Component discovery\n│       ├── solutions.js     # Solution-file discovery + per-domain runner\n│       ├── vnextConfig.js   # Solution file (vnext*.config.json) parser\n│       └── workflow.js      # Workflow processing\n├── .github/\n│   └── workflows/           # GitHub Actions workflows\n│       ├── build-and-publish.yml\n│       └── check-sonar.yml\n├── package.json\n└── README.md\n```\n\n### Local Development\n\n```bash\n# Clone and install\ngit clone https://github.com/burgan-tech/vnext-workflow-cli.git\ncd vnext-workflow-cli\nnpm install\nnpm link\n\n# Test the CLI\nwf --version\nwf check\n\n# Run development\nnpm run dev\n```\n\n---\n\n## 📝 License\n\nMIT License - see [LICENSE](LICENSE) for details.\n\n### Schema purpose for index generation\n\nSchema components use the existing `attributes.type` string. Its values are not restricted to an enum;\nlegacy and custom types remain valid. Only the exact value `master` permits `x-indexed` metadata\n(including `false`) and contributes index SQL. Missing, null, blank or other values never mean master.\nThe existing publication requirement for a non-empty schema type is unchanged. JSON Schema `type`\nkeywords within `attributes.schema` retain their existing meaning.\nA latest reference resolving to a non-master schema does not fall back to an older master version.\nNo matching masters means no SQL batch. There is no separate component root `type` field.\n\n```json\n{\n  \"key\": \"order-master\",\n  \"domain\": \"sales\",\n  \"flow\": \"sys-schemas\",\n  \"version\": \"1.0.0\",\n  \"flowVersion\": \"1.0.0\",\n  \"tags\": [\"orders\"],\n  \"attributes\": {\n    \"type\": \"master\",\n    \"schema\": {\n      \"type\": \"object\",\n      \"properties\": {\n        \"amount\": { \"type\": \"number\", \"x-indexed\": true, \"x-filterOperators\": [\"gt\"] }\n      }\n    }\n  }\n}\n```\n\nThe schema validator reads `SchemaDefinition.Type` (`attributes.type`) during publication, including\nschema seed items. No extra envelope metadata is required.\n","readmeFilename":"README.md"}