@mesh-tech/mesh-cli 0.31.0 → 0.31.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/build-info.json
CHANGED
|
@@ -162,8 +162,12 @@ export function assembleHubEnv(session, sessionEnv, opts) {
|
|
|
162
162
|
PORT: String(opts.uiPort),
|
|
163
163
|
API_URL: `http://localhost:${opts.apiPort}`,
|
|
164
164
|
HUB_TENANT: hubTenant,
|
|
165
|
+
HUB_SCOPE_ENV: scopeEnv,
|
|
165
166
|
DEFAULT_ORG: scopeTenants[0],
|
|
166
167
|
DEFAULT_ENV: scopeEnv,
|
|
168
|
+
...(process.env.HUB_PEER_ENVIRONMENTS
|
|
169
|
+
? { HUB_PEER_ENVIRONMENTS: process.env.HUB_PEER_ENVIRONMENTS }
|
|
170
|
+
: {}),
|
|
167
171
|
...audienceEnv,
|
|
168
172
|
};
|
|
169
173
|
return { apiEnv, uiEnv, scope: { hubTenant, scopeEnv, scopeTenants }, temporalAddress, warnings, notes };
|
|
@@ -7,3 +7,18 @@ locally with `mesh dev`, deploy it with `mesh deploy up`.
|
|
|
7
7
|
The API's reference site is built by the platform from `api/openapi.json` and
|
|
8
8
|
the guides in `docs/pages/` — this README is its landing page.
|
|
9
9
|
{{/if}}
|
|
10
|
+
|
|
11
|
+
## The version this app reports
|
|
12
|
+
|
|
13
|
+
`"version": "0.0.1"` in `package.json` is a STARTING POINT, not the number the
|
|
14
|
+
Hub shows. Every deploy derives the app's version from the conventional commits
|
|
15
|
+
that have landed on this directory since that version was last committed: a
|
|
16
|
+
`fix:` moves the patch, a `feat:` moves the minor, a `feat!:`/`BREAKING CHANGE:`
|
|
17
|
+
moves the major. Redeploying unchanged code stamps the same number, so a
|
|
18
|
+
redeploy is not recorded as a new deploy.
|
|
19
|
+
|
|
20
|
+
Nothing to run and nothing to remember — the version simply grows with the app,
|
|
21
|
+
and the Hub's Activity tab shows each deploy with the version it shipped. To
|
|
22
|
+
take the number over yourself, commit the version you want into `package.json`
|
|
23
|
+
(the derivation restarts from it) or pass `versioning: "package"` to
|
|
24
|
+
`AppEnvironment`.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@mesh-tech/mesh-cli",
|
|
3
|
-
"version": "0.31.
|
|
3
|
+
"version": "0.31.1",
|
|
4
4
|
"description": "CLI for Mesh platform development utilities",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"license": "UNLICENSED",
|
|
@@ -42,7 +42,7 @@
|
|
|
42
42
|
},
|
|
43
43
|
"devDependencies": {
|
|
44
44
|
"@mesh-tech/agent-contracts": "0.2.0",
|
|
45
|
-
"@mesh-tech/tsconfig": "2.
|
|
45
|
+
"@mesh-tech/tsconfig": "2.26.0",
|
|
46
46
|
"@mesh-tech/workflow-viz": "0.3.0",
|
|
47
47
|
"@tanstack/intent": "^0.3.6",
|
|
48
48
|
"@types/node": "^20.0.0",
|
|
@@ -22,3 +22,11 @@ pnpm install
|
|
|
22
22
|
mesh dev # run locally
|
|
23
23
|
mesh deploy up # deploy via the stack's deployer role
|
|
24
24
|
```
|
|
25
|
+
|
|
26
|
+
## App versions
|
|
27
|
+
|
|
28
|
+
An app's deployed version is derived from its own change set — the conventional
|
|
29
|
+
commits touching `apps/<app>/` since the version in its `package.json` was last
|
|
30
|
+
committed — so it grows on its own and the Hub can show which version each
|
|
31
|
+
deploy shipped. Conventional-commit subjects (`feat:`, `fix:`, `feat!:`) are
|
|
32
|
+
what make the bump meaningful; a subject with no type counts as a patch.
|