@terreno/mcp 58.0.3 → 58.0.4

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.
Files changed (4) hide show
  1. package/CHANGELOG.md +6 -0
  2. package/dist/docs/versioned/next/explanation/test-sharding.md +4 -2
  3. package/package.json +4 -4
  4. package/src/docs/versioned/next/explanation/test-sharding.md +4 -2
package/CHANGELOG.md CHANGED
@@ -20,6 +20,12 @@ Upgrade notes for consumer action live in [`mcp-server/src/docs/upgrades/`](mcp-
20
20
 
21
21
  Unreleased changes live in [`changelog/unreleased/`](changelog/unreleased/). Add one Markdown file per feature (see that directory's README) instead of editing this section.
22
22
 
23
+ ## [58.0.4] - 2026-11-11
24
+
25
+ ### Fixed
26
+
27
+ - The admin consent form list loads again. `ConsentFormList` sorts by `-created` (and by its Title, Type, Version, Active, and Order columns), but `ConsentApp`'s `/consent-forms` router did not declare those as `sortFields`, so every list request returned 400 `sort-field-not-allowed`. Both `/consent-forms` and `/consent-responses` now allow sorting by the fields their admin metadata marks sortable; other fields are still rejected.
28
+
23
29
  ## [58.0.3] - 2026-11-11
24
30
 
25
31
  Upgrade note: [`mcp-server/src/docs/upgrades/58.0.3.md`](mcp-server/src/docs/upgrades/58.0.3.md).
package/dist/docs/versioned/next/explanation/test-sharding.md CHANGED
@@ -34,8 +34,10 @@ A backend shard keeps a Bun process and a `mongod` busy, about two cores. More s
34
34
  half the cores slows every shard down and makes timing-sensitive tests fail.
35
35
 
36
36
  CircleCI jobs set `TERRENO_TEST_SHARDS` themselves, because a container reports the host's
37
- cores and not its own CPU limit. Medium jobs (2 vCPU) run 1 shard. `api-ci`, the longest
38
- test job, runs on `large` (4 vCPU) with 2 shards.
37
+ cores and not its own CPU limit. Medium jobs (2 vCPU) run 1 shard. Backend jobs run 1 shard
38
+ even on `large`: CircleCI gives a job one sidecar `mongod`, and every shard connects to the
39
+ same `mongodb://127.0.0.1/terreno` database, so concurrent shards clear each other's
40
+ collections mid-test. `api-ci` ran 2 shards until that broke its tests.
39
41
 
40
42
  Root `bun run test` and `bun run test:agent` set `TERRENO_TEST_SHARDS=1`: they already run
41
43
  every package at the same time.
package/package.json CHANGED
@@ -11,8 +11,8 @@
11
11
  "@modelcontextprotocol/node": "^2.1.2",
12
12
  "@modelcontextprotocol/server": "^2.0.0",
13
13
  "@sentry/bun": "^11.0.0",
14
- "@terreno/api": "58.0.3",
15
- "@terreno/blocks": "58.0.3",
14
+ "@terreno/api": "58.0.4",
15
+ "@terreno/blocks": "58.0.4",
16
16
  "express": "^5.2.1",
17
17
  "luxon": "^3.7.2",
18
18
  "minisearch": "^7.2.0",
@@ -22,7 +22,7 @@
22
22
  "devDependencies": {
23
23
  "@biomejs/biome": "2.5.13",
24
24
  "@modelcontextprotocol/client": "^2.0.0",
25
- "@terreno/test": "58.0.3",
25
+ "@terreno/test": "58.0.4",
26
26
  "@types/bun": "^1.4.0",
27
27
  "@types/luxon": "^3.7.1",
28
28
  "@types/node": "^25.3.0",
@@ -109,5 +109,5 @@
109
109
  "typecheck": "NODE_OPTIONS=--max-old-space-size=8192 tsc -p tsconfig.typecheck.json"
110
110
  },
111
111
  "type": "module",
112
- "version": "58.0.3"
112
+ "version": "58.0.4"
113
113
  }
package/src/docs/versioned/next/explanation/test-sharding.md CHANGED
@@ -34,8 +34,10 @@ A backend shard keeps a Bun process and a `mongod` busy, about two cores. More s
34
34
  half the cores slows every shard down and makes timing-sensitive tests fail.
35
35
 
36
36
  CircleCI jobs set `TERRENO_TEST_SHARDS` themselves, because a container reports the host's
37
- cores and not its own CPU limit. Medium jobs (2 vCPU) run 1 shard. `api-ci`, the longest
38
- test job, runs on `large` (4 vCPU) with 2 shards.
37
+ cores and not its own CPU limit. Medium jobs (2 vCPU) run 1 shard. Backend jobs run 1 shard
38
+ even on `large`: CircleCI gives a job one sidecar `mongod`, and every shard connects to the
39
+ same `mongodb://127.0.0.1/terreno` database, so concurrent shards clear each other's
40
+ collections mid-test. `api-ci` ran 2 shards until that broke its tests.
39
41
 
40
42
  Root `bun run test` and `bun run test:agent` set `TERRENO_TEST_SHARDS=1`: they already run
41
43
  every package at the same time.