@haneinfo/background-jobs 0.1.18 → 0.1.20

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/README.md CHANGED
@@ -1,42 +1,42 @@
1
- # @haneinfo/background-jobs
2
-
3
- Database-backed jobs for internal Haneinfo Apps. No external queue is required.
4
-
5
- Install the plugin, copy `prisma/background-jobs.prisma` into the App's Prisma schema and create
6
- a migration. Register handlers during module initialization on every worker replica:
7
-
8
- ```ts
9
- jobs.register('example.batch', async (params, context) => {
10
- await context.checkpoint();
11
- // Use context.tx for database writes; check context.signal/checkpoint between batches.
12
- await context.progress(50);
13
- return { processed: 10 };
14
- });
15
- const job = await jobs.enqueue({ type: 'example.batch', params: {}, createdBy: userId });
16
- ```
17
-
18
- `BackgroundJobsModule.register(config)` exports the service, worker and MCP tools. The plugin
19
- factory is `backgroundJobs()` from `@haneinfo/background-jobs/plugin`. Apps register MCP tools
20
- explicitly with `BackgroundJobsMcpTools.registerInto(registry, { scopeNamespace })`.
21
-
22
- `GET /background-jobs/:id` uses interactive authentication. `get_job_status` requires
23
- `<namespace>:jobs:read` and a bound user. Both return 404 for another creator's job, including
24
- administrators. MCP parameters, result and error text are wrapped in `$userContent`.
25
-
26
- See [agent-guide.md](agent-guide.md) for transaction, retry and cancellation contracts.
27
-
28
-
29
- ## Instance lifecycle (draft 202610-f1a8)
30
-
31
- Implemented from draft decision 202610-f1a8; the decision remains draft. Upgrade state-machine,
32
- list-view, collaboration, attachments, import-export, assignment and timer together. No frontend,
33
- automatic archive or bulk lifecycle operations are included. Permanently purged data cannot be
34
- restored by this API: database and private file backups must cover the entire deletion retention
35
- period and be restored consistently.
36
-
37
- State-machine optionally registers state-machine.instances.purge. Its producer follows the same
38
- bootstrap/interval/disable/shutdown pattern as attachment cleanup. The job handler uses context.tx
39
- for events, garbage markers, cascade and success status; failures/cancellation roll back the entire
40
- batch before normal retry. The state-machine package owns retention, batch bounds and producer
41
- settings. Core worker enablement and runDue behavior are unchanged. Attachments.cleanup separately
42
- recycles the committed garbage markers. No change to the core job table or retry policy is needed.
1
+ # @haneinfo/background-jobs
2
+
3
+ Database-backed jobs for internal Haneinfo Apps. No external queue is required.
4
+
5
+ Install the plugin, copy `prisma/background-jobs.prisma` into the App's Prisma schema and create
6
+ a migration. Register handlers during module initialization on every worker replica:
7
+
8
+ ```ts
9
+ jobs.register('example.batch', async (params, context) => {
10
+ await context.checkpoint();
11
+ // Use context.tx for database writes; check context.signal/checkpoint between batches.
12
+ await context.progress(50);
13
+ return { processed: 10 };
14
+ });
15
+ const job = await jobs.enqueue({ type: 'example.batch', params: {}, createdBy: userId });
16
+ ```
17
+
18
+ `BackgroundJobsModule.register(config)` exports the service, worker and MCP tools. The plugin
19
+ factory is `backgroundJobs()` from `@haneinfo/background-jobs/plugin`. Apps register MCP tools
20
+ explicitly with `BackgroundJobsMcpTools.registerInto(registry, { scopeNamespace })`.
21
+
22
+ `GET /background-jobs/:id` uses interactive authentication. `get_job_status` requires
23
+ `<namespace>:jobs:read` and a bound user. Both return 404 for another creator's job, including
24
+ administrators. MCP parameters, result and error text are wrapped in `$userContent`.
25
+
26
+ See [agent-guide.md](agent-guide.md) for transaction, retry and cancellation contracts.
27
+
28
+
29
+ ## Instance lifecycle (draft 202610-f1a8)
30
+
31
+ Implemented from draft decision 202610-f1a8; the decision remains draft. Upgrade state-machine,
32
+ list-view, collaboration, attachments, import-export, assignment and timer together. No frontend,
33
+ automatic archive or bulk lifecycle operations are included. Permanently purged data cannot be
34
+ restored by this API: database and private file backups must cover the entire deletion retention
35
+ period and be restored consistently.
36
+
37
+ State-machine optionally registers state-machine.instances.purge. Its producer follows the same
38
+ bootstrap/interval/disable/shutdown pattern as attachment cleanup. The job handler uses context.tx
39
+ for events, garbage markers, cascade and success status; failures/cancellation roll back the entire
40
+ batch before normal retry. The state-machine package owns retention, batch bounds and producer
41
+ settings. Core worker enablement and runDue behavior are unchanged. Attachments.cleanup separately
42
+ recycles the committed garbage markers. No change to the core job table or retry policy is needed.
package/agent-guide.md CHANGED
@@ -1,74 +1,74 @@
1
- # Background jobs — Agent Guide
2
-
3
- Use this package for long-running, database-backed work. Import/export producers are separate
4
- packages; this package provides no file generation, import confirmation or download endpoint.
5
-
6
- ## Runtime contract
7
-
8
- Provides capability `haneinfo.background-jobs` and plugin-api token `BACKGROUND_JOBS` /
9
- `BackgroundJobsPort`. A producer plugin declares that capability in `requires`, injects the token
10
- and registers its handler at module initialization. The host imports the existing provider module
11
- along that dependency edge. Do not import/register a second BackgroundJobsModule from a producer.
12
-
13
- - Register a stable lowercase dotted/dashed type with `BackgroundJobsService.register(type, handler)`
14
- at module initialization. Duplicate types fail. All worker replicas must register the same handlers.
15
- - `enqueue({ type, params, createdBy, maxRetries? })` is an internal API. The producing package
16
- authenticates and authorizes the request and supplies the authenticated creator, never a client id.
17
- - A short committed transaction claims `(id, PENDING, attempt, cancelRequested=false)` by compare-and-set.
18
- Each attempt then runs in its own business transaction. Use `context.tx` for all database effects.
19
- Success/result and business writes commit together. Failed/cancelled attempts roll back their effects;
20
- their control-state update is committed separately. One handler failure does not block later jobs.
21
- - `maxRetries` is the number of additional attempts, not total attempts. `attempt` counts claims;
22
- `retryCount` counts failed attempts, including terminal failure. Cancellation does not consume retries.
23
- Retries are eligible after `retryDelayMs` and are not retried again in the same `runDue()` snapshot.
24
- - `cancelFor(creatorId, id)` cancels PENDING immediately and flags RUNNING cooperatively. Check
25
- `checkpoint()` between batches or use the AbortSignal. The cancellation poller aborts that signal;
26
- a final checkpoint and conditional success update also prevent a cancelled attempt from committing.
27
- Cancellation racing an already committed success leaves SUCCEEDED. Non-cooperating external calls
28
- cannot be forcefully interrupted; handlers must make external effects idempotent across retries.
29
- - `progress(0..100)` persists outside the business transaction; it can be observed while work runs.
30
- Progress describes attempted work, and may remain on failed/cancelled rows. Retrying resets it to zero.
31
- - The worker polls one batch at a time per process, waits for its current tick on graceful shutdown,
32
- and does not poll when disabled. `runDue()` is an explicit operator/test API even when disabled.
33
- - Claims are durable. A process crash can leave RUNNING work stranded. There is deliberately no
34
- automatic stale-claim stealing: restarting work without an idempotency/recovery policy could repeat
35
- external effects. Operators must investigate before a controlled repair; a lease/recovery API is
36
- a future decision. Pool capacity must allow the business transaction plus control reads/writes.
37
-
38
- ## Configuration
39
-
40
- The plugin configRef is `backgroundJobs`. Defaults: workerEnabled `true`, pollIntervalMs `1000`,
41
- batchSize `20`, maxRetries `3`, retryDelayMs `1000`, cancellationPollIntervalMs `250`, and
42
- transactionTimeoutMs `300000`. Polling starts after the first interval. The plugin validates all
43
- numeric options; direct module registration uses the same parser. Use `workerEnabled: false` for
44
- test Apps or replicas without a worker.
45
- The polling and cancellation polling intervals are capped at 2,147,483,647 milliseconds to avoid
46
- Node's timer overflow, which would otherwise turn a long interval into a one-millisecond loop.
47
-
48
- ## Persistence and access
49
-
50
- `BackgroundJob`: id, type, params, status, progress, result, lastError, attempt, retryCount,
51
- maxRetries, createdBy, cancelRequested, availableAt, createdAt, startedAt, finishedAt, updatedAt.
52
- Statuses: PENDING, RUNNING, SUCCEEDED, FAILED, CANCELLED. Indices cover due polling and creator reads.
53
- Parameters/results are JSON; future import/export packages can own their payload formats and expiry.
54
-
55
- Only the creator can read or cancel through the service. There is no administrator override.
56
- HTTP exposes only status, on the existing interactive auth boundary. MCP exposes only
57
- `get_job_status`, scope `<namespace>:jobs:read`, with a bound acting user and `$userContent` wrappers.
58
- No public MCP endpoint is created. Register tools in the App's existing internal registry.
59
-
60
-
61
- ## Instance lifecycle (draft 202610-f1a8)
62
-
63
- Implemented from draft decision 202610-f1a8; the decision remains draft. Upgrade state-machine,
64
- list-view, collaboration, attachments, import-export, assignment and timer together. No frontend,
65
- automatic archive or bulk lifecycle operations are included. Permanently purged data cannot be
66
- restored by this API: database and private file backups must cover the entire deletion retention
67
- period and be restored consistently.
68
-
69
- State-machine optionally registers state-machine.instances.purge. Its producer follows the same
70
- bootstrap/interval/disable/shutdown pattern as attachment cleanup. The job handler uses context.tx
71
- for events, garbage markers, cascade and success status; failures/cancellation roll back the entire
72
- batch before normal retry. The state-machine package owns retention, batch bounds and producer
73
- settings. Core worker enablement and runDue behavior are unchanged. Attachments.cleanup separately
74
- recycles the committed garbage markers. No change to the core job table or retry policy is needed.
1
+ # Background jobs — Agent Guide
2
+
3
+ Use this package for long-running, database-backed work. Import/export producers are separate
4
+ packages; this package provides no file generation, import confirmation or download endpoint.
5
+
6
+ ## Runtime contract
7
+
8
+ Provides capability `haneinfo.background-jobs` and plugin-api token `BACKGROUND_JOBS` /
9
+ `BackgroundJobsPort`. A producer plugin declares that capability in `requires`, injects the token
10
+ and registers its handler at module initialization. The host imports the existing provider module
11
+ along that dependency edge. Do not import/register a second BackgroundJobsModule from a producer.
12
+
13
+ - Register a stable lowercase dotted/dashed type with `BackgroundJobsService.register(type, handler)`
14
+ at module initialization. Duplicate types fail. All worker replicas must register the same handlers.
15
+ - `enqueue({ type, params, createdBy, maxRetries? })` is an internal API. The producing package
16
+ authenticates and authorizes the request and supplies the authenticated creator, never a client id.
17
+ - A short committed transaction claims `(id, PENDING, attempt, cancelRequested=false)` by compare-and-set.
18
+ Each attempt then runs in its own business transaction. Use `context.tx` for all database effects.
19
+ Success/result and business writes commit together. Failed/cancelled attempts roll back their effects;
20
+ their control-state update is committed separately. One handler failure does not block later jobs.
21
+ - `maxRetries` is the number of additional attempts, not total attempts. `attempt` counts claims;
22
+ `retryCount` counts failed attempts, including terminal failure. Cancellation does not consume retries.
23
+ Retries are eligible after `retryDelayMs` and are not retried again in the same `runDue()` snapshot.
24
+ - `cancelFor(creatorId, id)` cancels PENDING immediately and flags RUNNING cooperatively. Check
25
+ `checkpoint()` between batches or use the AbortSignal. The cancellation poller aborts that signal;
26
+ a final checkpoint and conditional success update also prevent a cancelled attempt from committing.
27
+ Cancellation racing an already committed success leaves SUCCEEDED. Non-cooperating external calls
28
+ cannot be forcefully interrupted; handlers must make external effects idempotent across retries.
29
+ - `progress(0..100)` persists outside the business transaction; it can be observed while work runs.
30
+ Progress describes attempted work, and may remain on failed/cancelled rows. Retrying resets it to zero.
31
+ - The worker polls one batch at a time per process, waits for its current tick on graceful shutdown,
32
+ and does not poll when disabled. `runDue()` is an explicit operator/test API even when disabled.
33
+ - Claims are durable. A process crash can leave RUNNING work stranded. There is deliberately no
34
+ automatic stale-claim stealing: restarting work without an idempotency/recovery policy could repeat
35
+ external effects. Operators must investigate before a controlled repair; a lease/recovery API is
36
+ a future decision. Pool capacity must allow the business transaction plus control reads/writes.
37
+
38
+ ## Configuration
39
+
40
+ The plugin configRef is `backgroundJobs`. Defaults: workerEnabled `true`, pollIntervalMs `1000`,
41
+ batchSize `20`, maxRetries `3`, retryDelayMs `1000`, cancellationPollIntervalMs `250`, and
42
+ transactionTimeoutMs `300000`. Polling starts after the first interval. The plugin validates all
43
+ numeric options; direct module registration uses the same parser. Use `workerEnabled: false` for
44
+ test Apps or replicas without a worker.
45
+ The polling and cancellation polling intervals are capped at 2,147,483,647 milliseconds to avoid
46
+ Node's timer overflow, which would otherwise turn a long interval into a one-millisecond loop.
47
+
48
+ ## Persistence and access
49
+
50
+ `BackgroundJob`: id, type, params, status, progress, result, lastError, attempt, retryCount,
51
+ maxRetries, createdBy, cancelRequested, availableAt, createdAt, startedAt, finishedAt, updatedAt.
52
+ Statuses: PENDING, RUNNING, SUCCEEDED, FAILED, CANCELLED. Indices cover due polling and creator reads.
53
+ Parameters/results are JSON; future import/export packages can own their payload formats and expiry.
54
+
55
+ Only the creator can read or cancel through the service. There is no administrator override.
56
+ HTTP exposes only status, on the existing interactive auth boundary. MCP exposes only
57
+ `get_job_status`, scope `<namespace>:jobs:read`, with a bound acting user and `$userContent` wrappers.
58
+ No public MCP endpoint is created. Register tools in the App's existing internal registry.
59
+
60
+
61
+ ## Instance lifecycle (draft 202610-f1a8)
62
+
63
+ Implemented from draft decision 202610-f1a8; the decision remains draft. Upgrade state-machine,
64
+ list-view, collaboration, attachments, import-export, assignment and timer together. No frontend,
65
+ automatic archive or bulk lifecycle operations are included. Permanently purged data cannot be
66
+ restored by this API: database and private file backups must cover the entire deletion retention
67
+ period and be restored consistently.
68
+
69
+ State-machine optionally registers state-machine.instances.purge. Its producer follows the same
70
+ bootstrap/interval/disable/shutdown pattern as attachment cleanup. The job handler uses context.tx
71
+ for events, garbage markers, cascade and success status; failures/cancellation roll back the entire
72
+ batch before normal retry. The state-machine package owns retention, batch bounds and producer
73
+ settings. Core worker enablement and runDue behavior are unchanged. Attachments.cleanup separately
74
+ recycles the committed garbage markers. No change to the core job table or retry policy is needed.
package/dist/plugin.js CHANGED
@@ -16,9 +16,9 @@ exports.backgroundJobsManifest = {
16
16
  haneinfoPluginApi: '^1.10.0',
17
17
  node: '>=22.0.0',
18
18
  frameworks: {
19
- '@nestjs/common': '^11.0.5',
20
- '@nestjs/core': '^11.0.5',
21
- '@prisma/client': '^6.2.0',
19
+ '@nestjs/common': '^11.0.5 || ^12.0.0',
20
+ '@nestjs/core': '^11.0.5 || ^12.0.0',
21
+ '@prisma/client': '^6.2.0 || ^7.10.1',
22
22
  },
23
23
  },
24
24
  provides: ['haneinfo.background-jobs'],
@@ -1 +1 @@
1
- {"version":3,"file":"plugin.js","sourceRoot":"","sources":["../src/plugin.ts"],"names":[],"mappings":";;;AAmDA,wCAEC;AArDD,qDAA2E;AAC3E,qCAAsD;AACtD,+CAAqD;AAoD5C,qGApDA,kCAAoB,OAoDA;AAnDhB,QAAA,sBAAsB,GAAqB;IACtD,aAAa,EAAE,oBAAoB;IACnC,EAAE,EAAE,iBAAiB;IACrB,WAAW,EAAE,iBAAiB;IAC9B,WAAW,EAAE,WAAW;IACxB,YAAY,EAAE,UAAU;IACxB,MAAM,EAAE;QACN,iBAAiB,EAAE,SAAS;QAC5B,IAAI,EAAE,UAAU;QAChB,UAAU,EAAE;YACV,gBAAgB,EAAE,SAAS;YAC3B,cAAc,EAAE,SAAS;YACzB,gBAAgB,EAAE,QAAQ;SAC3B;KACF;IACD,QAAQ,EAAE,CAAC,0BAA0B,CAAC;IACtC,QAAQ,EAAE,CAAC,iBAAiB,CAAC;IAC7B,gBAAgB,EAAE,EAAE;IACpB,YAAY,EAAE;QACZ,SAAS,EAAE,gBAAgB;KAC5B;IACD,MAAM,EAAE;QACN,OAAO,EAAE;YACP,UAAU,EAAE,uBAAuB;YACnC,UAAU,EAAE,sBAAsB;YAClC,cAAc,EAAE,CAAC,0BAA0B,CAAC;YAC5C,OAAO,EAAE,CAAC,iCAAiC,CAAC;YAC5C,QAAQ,EAAE;gBACR;oBACE,IAAI,EAAE,gBAAgB;oBACtB,cAAc,EAAE,CAAC,uBAAuB,CAAC;iBAC1C;aACF;YACD,UAAU,EAAE,kBAAkB;SAC/B;QACD,MAAM,EAAE;YACN,IAAI,EAAE,CAAC,eAAe,CAAC;YACvB,cAAc,EAAE,+BAA+B;YAC/C,YAAY,EAAE,yEAAyE;SACxF;KACF;CACF,CAAC;AACW,QAAA,YAAY,GAAG,mCAA0B,CAAC;AAC1C,QAAA,oBAAoB,GAAG,IAAA,yBAAY,EAAC;IAC/C,QAAQ,EAAE,8BAAsB;IAChC,YAAY,EAAZ,oBAAY;IACZ,OAAO,EAAE,CAAC,OAAO,EAAE,EAAE,CAAC,kCAAoB,CAAC,QAAQ,CAAC,OAAO,CAAC,MAAM,CAAC;CACpE,CAAC,CAAC;AACH,SAAgB,cAAc;IAC5B,OAAO,4BAAoB,CAAC;AAC9B,CAAC"}
1
+ {"version":3,"file":"plugin.js","sourceRoot":"","sources":["../src/plugin.ts"],"names":[],"mappings":";;;AAmDA,wCAEC;AArDD,qDAA2E;AAC3E,qCAAsD;AACtD,+CAAqD;AAoD5C,qGApDA,kCAAoB,OAoDA;AAnDhB,QAAA,sBAAsB,GAAqB;IACtD,aAAa,EAAE,oBAAoB;IACnC,EAAE,EAAE,iBAAiB;IACrB,WAAW,EAAE,iBAAiB;IAC9B,WAAW,EAAE,WAAW;IACxB,YAAY,EAAE,UAAU;IACxB,MAAM,EAAE;QACN,iBAAiB,EAAE,SAAS;QAC5B,IAAI,EAAE,UAAU;QAChB,UAAU,EAAE;YACV,gBAAgB,EAAE,oBAAoB;YACtC,cAAc,EAAE,oBAAoB;YACpC,gBAAgB,EAAE,mBAAmB;SACtC;KACF;IACD,QAAQ,EAAE,CAAC,0BAA0B,CAAC;IACtC,QAAQ,EAAE,CAAC,iBAAiB,CAAC;IAC7B,gBAAgB,EAAE,EAAE;IACpB,YAAY,EAAE;QACZ,SAAS,EAAE,gBAAgB;KAC5B;IACD,MAAM,EAAE;QACN,OAAO,EAAE;YACP,UAAU,EAAE,uBAAuB;YACnC,UAAU,EAAE,sBAAsB;YAClC,cAAc,EAAE,CAAC,0BAA0B,CAAC;YAC5C,OAAO,EAAE,CAAC,iCAAiC,CAAC;YAC5C,QAAQ,EAAE;gBACR;oBACE,IAAI,EAAE,gBAAgB;oBACtB,cAAc,EAAE,CAAC,uBAAuB,CAAC;iBAC1C;aACF;YACD,UAAU,EAAE,kBAAkB;SAC/B;QACD,MAAM,EAAE;YACN,IAAI,EAAE,CAAC,eAAe,CAAC;YACvB,cAAc,EAAE,+BAA+B;YAC/C,YAAY,EAAE,yEAAyE;SACxF;KACF;CACF,CAAC;AACW,QAAA,YAAY,GAAG,mCAA0B,CAAC;AAC1C,QAAA,oBAAoB,GAAG,IAAA,yBAAY,EAAC;IAC/C,QAAQ,EAAE,8BAAsB;IAChC,YAAY,EAAZ,oBAAY;IACZ,OAAO,EAAE,CAAC,OAAO,EAAE,EAAE,CAAC,kCAAoB,CAAC,QAAQ,CAAC,OAAO,CAAC,MAAM,CAAC;CACpE,CAAC,CAAC;AACH,SAAgB,cAAc;IAC5B,OAAO,4BAAoB,CAAC;AAC9B,CAAC"}
@@ -8,9 +8,9 @@
8
8
  "haneinfoPluginApi": "^1.10.0",
9
9
  "node": ">=22.0.0",
10
10
  "frameworks": {
11
- "@nestjs/common": "^11.0.5",
12
- "@nestjs/core": "^11.0.5",
13
- "@prisma/client": "^6.2.0"
11
+ "@nestjs/common": "^11.0.5 || ^12.0.0",
12
+ "@nestjs/core": "^11.0.5 || ^12.0.0",
13
+ "@prisma/client": "^6.2.0 || ^7.10.1"
14
14
  }
15
15
  },
16
16
  "provides": ["haneinfo.background-jobs"],
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@haneinfo/background-jobs",
3
- "version": "0.1.18",
3
+ "version": "0.1.20",
4
4
  "private": false,
5
5
  "description": "Database-backed background jobs with transactional handlers, retry and cooperative cancellation.",
6
6
  "files": [
@@ -29,27 +29,27 @@
29
29
  "./prisma/background-jobs.prisma": "./prisma/background-jobs.prisma"
30
30
  },
31
31
  "dependencies": {
32
- "@haneinfo/plugin-api": "1.27.0"
32
+ "@haneinfo/plugin-api": "1.28.0"
33
33
  },
34
34
  "peerDependencies": {
35
- "@haneinfo/common": "^0.3.4 || ^0.4.0 || ^0.5.0 || ^0.6.0",
35
+ "@haneinfo/common": "^0.3.4 || ^0.4.0 || ^0.5.0 || ^0.6.0 || ^0.7.0",
36
36
  "@haneinfo/plugin-host-nest": "^2.1.0",
37
- "@nestjs/common": "^11.0.0",
38
- "@nestjs/core": "^11.0.0",
39
- "@prisma/client": "^6.19.0",
37
+ "@nestjs/common": "^11.0.0 || ^12.0.0",
38
+ "@nestjs/core": "^11.0.0 || ^12.0.0",
39
+ "@prisma/client": "^6.19.0 || ^7.10.1",
40
40
  "zod": "^4.4.0"
41
41
  },
42
42
  "devDependencies": {
43
- "@nestjs/common": "^11.0.0",
44
- "@nestjs/core": "^11.0.0",
45
- "@nestjs/testing": "^11.0.0",
46
- "@prisma/client": "^6.19.0",
43
+ "@nestjs/common": "^12.3.2",
44
+ "@nestjs/core": "^12.3.2",
45
+ "@nestjs/testing": "^12.3.2",
46
+ "@prisma/client": "^7.10.1",
47
47
  "@types/node": "^24.13.0",
48
48
  "typescript": "^5.9.3",
49
49
  "vitest": "^4.1.11",
50
50
  "zod": "^4.4.0",
51
- "@haneinfo/common": "0.6.1",
52
- "@haneinfo/plugin-host-nest": "2.1.1",
51
+ "@haneinfo/common": "0.7.0",
52
+ "@haneinfo/plugin-host-nest": "2.1.2",
53
53
  "@haneinfo/plugin-testkit": "2.3.1"
54
54
  },
55
55
  "license": "UNLICENSED",