dsh-tender-workbench 0.4.0 → 0.4.2
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/CHANGELOG.md +26 -1
- package/README.en.md +144 -0
- package/README.md +79 -89
- package/docs/RELEASE-0.4.2.md +63 -0
- package/lib/client.js +283 -283
- package/package.json +9 -4
- package/docs/RELEASE-0.4.0.md +0 -75
package/package.json
CHANGED
|
@@ -1,14 +1,18 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "dsh-tender-workbench",
|
|
3
|
-
"version": "0.4.
|
|
4
|
-
"description": "
|
|
3
|
+
"version": "0.4.2",
|
|
4
|
+
"description": "DeepSeek Harness 招投标工作台智能体:支持招投标查询、规则初筛、智能分析、人工复核及 Excel/PDF 报告交付。",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"deepseek-harness",
|
|
7
7
|
"dsh",
|
|
8
8
|
"tender",
|
|
9
9
|
"bidding",
|
|
10
10
|
"procurement",
|
|
11
|
-
"proposed-projects"
|
|
11
|
+
"proposed-projects",
|
|
12
|
+
"招投标",
|
|
13
|
+
"标讯",
|
|
14
|
+
"拟建项目",
|
|
15
|
+
"企查查"
|
|
12
16
|
],
|
|
13
17
|
"author": "Sunhh3221",
|
|
14
18
|
"type": "module",
|
|
@@ -28,9 +32,10 @@
|
|
|
28
32
|
"files": [
|
|
29
33
|
"LICENSE",
|
|
30
34
|
"README.md",
|
|
35
|
+
"README.en.md",
|
|
31
36
|
"CHANGELOG.md",
|
|
32
37
|
"cordis.patch.yml",
|
|
33
|
-
"docs/RELEASE-0.4.
|
|
38
|
+
"docs/RELEASE-0.4.2.md",
|
|
34
39
|
"lib/index.js",
|
|
35
40
|
"lib/client.js",
|
|
36
41
|
"lib/client.js.map",
|
package/docs/RELEASE-0.4.0.md
DELETED
|
@@ -1,75 +0,0 @@
|
|
|
1
|
-
# dsh-tender-workbench 0.4.0 release checklist
|
|
2
|
-
|
|
3
|
-
- Version: **0.4.0**
|
|
4
|
-
- Release date: 2026-09-05
|
|
5
|
-
- Status: **release candidate**
|
|
6
|
-
- Release commit: pending
|
|
7
|
-
- Git tag: pending
|
|
8
|
-
- npm publication: pending
|
|
9
|
-
- GitHub Release: pending
|
|
10
|
-
|
|
11
|
-
## Scope
|
|
12
|
-
|
|
13
|
-
Version 0.4.0 promotes the complete 0.3.0 beta workflow to the stable npm channel. It includes the Session-scoped query, deterministic rule screening, bounded Agent analysis, explicit human review, and immutable Excel/PDF delivery already represented by the V2 contracts. This release adds repeatable documentation, packaging, CI, and OIDC publication gates; it does not migrate the workflow or Artifact schema used by 0.3.0-beta.1.
|
|
14
|
-
|
|
15
|
-
## Compatibility and installation
|
|
16
|
-
|
|
17
|
-
- Node.js: `^22.19.0 || >=24.0.0`
|
|
18
|
-
- Package manager: `pnpm@11.7.0`
|
|
19
|
-
- DeepSeek Harness public packages: `>=0.1.1-rc.2 || >=0.1.2-0`
|
|
20
|
-
- `dsh-mcp-connector`: `>=0.2.31`
|
|
21
|
-
- `dsh-better-sidebar`: `>=0.17.1 || >=0.18.0-0`
|
|
22
|
-
- Required MCP tools: `mcp__qcc-tender__search_tenders` and `mcp__qcc-tender__search_proposed_projects`
|
|
23
|
-
|
|
24
|
-
Install `dsh-tender-workbench@0.4.0` together with compatible Provider plugins, then fully restart the Web profile. Missing required services, incompatible Better Sidebar capabilities, unavailable MCP tools, or non-JSONL Session persistence fail explicitly.
|
|
25
|
-
|
|
26
|
-
## Release gates
|
|
27
|
-
|
|
28
|
-
- [x] Frozen pnpm install completes with the repository lockfile.
|
|
29
|
-
- [x] TypeScript type checking passes.
|
|
30
|
-
- [x] Full Vitest suite passes.
|
|
31
|
-
- [x] Host loader, Client bundle, source maps, and declarations build successfully.
|
|
32
|
-
- [x] README and release-state checks pass for 0.4.0.
|
|
33
|
-
- [x] `npm pack --dry-run --json` contains only whitelisted public files.
|
|
34
|
-
- [x] A clean temporary installation imports the packed Host entry and package metadata and registers the Client bundle.
|
|
35
|
-
- [ ] `main` CI passes on Linux Node 22/24 and Windows Node 24.
|
|
36
|
-
- [ ] Tag `v0.4.0` resolves to the reviewed release commit.
|
|
37
|
-
- [ ] npm Trusted Publishing creates `dsh-tender-workbench@0.4.0` with provenance and the `latest` dist-tag.
|
|
38
|
-
- [ ] GitHub Release `v0.4.0` is neither draft nor prerelease.
|
|
39
|
-
|
|
40
|
-
Unchecked items are pending and must not be reported as completed.
|
|
41
|
-
|
|
42
|
-
## Local validation record
|
|
43
|
-
|
|
44
|
-
Validated on 2026-09-05 with pnpm 11.7.0:
|
|
45
|
-
|
|
46
|
-
- `pnpm install --frozen-lockfile`: passed with the checked-in lockfile and `allowBuilds` policy.
|
|
47
|
-
- `pnpm run check`: passed, including 207 passing tests and 1 intentional skip across 40 test files.
|
|
48
|
-
- Package whitelist: passed with 169 public files and no source, test, script, cache, credential, or private Artifact paths.
|
|
49
|
-
- Clean-install smoke test: passed after supplying the same DSH Host peer baseline used by development; the Host entry exported `apply` and `inject`, package metadata reported 0.4.0, and the Client bundle registered with the module loader.
|
|
50
|
-
|
|
51
|
-
The ordinary npm peer auto-installer currently reports an upstream DSH peer-version conflict between the connector and UI layout packages. The production DSH plugin manager supplies the Host peer set, so the isolated smoke test installs the tarball with peer auto-installation disabled and then injects the compatible 0.1.1-rc.2 Host baseline explicitly. The build also reports an upstream missing source-map warning from `@deepseek-ai/dsh-client-ui-primitives`; generated package source maps are present and the gate passes.
|
|
52
|
-
|
|
53
|
-
## Publication procedure
|
|
54
|
-
|
|
55
|
-
1. Run `pnpm install --frozen-lockfile` using pnpm 11.7.0.
|
|
56
|
-
2. Run `pnpm run check` and the clean tarball installation/import smoke test.
|
|
57
|
-
3. Commit only the reviewed 0.4.0 release files and push `main`.
|
|
58
|
-
4. Wait for all required CI jobs to pass.
|
|
59
|
-
5. Create annotated tag `v0.4.0` on the pushed release commit and push the tag.
|
|
60
|
-
6. The tag workflow verifies `v${package.version}`, reruns the complete gates, publishes with npm OIDC Trusted Publishing and provenance, then creates the GitHub Release.
|
|
61
|
-
7. Verify npm version, dist-tags, repository, maintainers, tarball metadata/file list, clean installation/import, Git commit/tag, and GitHub Release state.
|
|
62
|
-
|
|
63
|
-
## Security
|
|
64
|
-
|
|
65
|
-
- Never store or print npm tokens, GitHub tokens, QCC credentials, source datasets, real business evidence, or Session-private Artifacts.
|
|
66
|
-
- The npm package must exclude `src`, `tests`, `scripts`, `.github`, `resources`, caches, local evidence, and environment files.
|
|
67
|
-
- Runtime QCC access remains customer-authorized through the connector; this repository does not own or proxy credentials.
|
|
68
|
-
- pnpm's `allowBuilds` policy explicitly keeps the indirect `node-pty` native build script disabled because this package does not use its binary at runtime or in the release gates.
|
|
69
|
-
|
|
70
|
-
## Rollback
|
|
71
|
-
|
|
72
|
-
- Before the tag is pushed: delete only the local tag if necessary, fix the release commit, and rerun all gates.
|
|
73
|
-
- After the tag is pushed but before npm publication: stop the failing workflow, fix forward with a new patch version and tag, and do not reuse a public tag.
|
|
74
|
-
- After npm publication: never overwrite or unpublish 0.4.0. Mark the affected version if necessary, publish a corrected patch version, and use an ordinary revert commit for source rollback.
|
|
75
|
-
- Deployment rollback target: reinstall `dsh-tender-workbench@0.3.0-beta.1` and fully restart the profile.
|