morluto/rea

Fork 0

mirror of https://github.com/morluto/rea.git synced 2026-11-05 06:45:22 +00:00

[GH-ISSUE #2149] [Feature] Publish npm release with DeepSeek Harness (dsh) support #704

New issue

Closed

opened 2026-10-15 18:27:33 +00:00 by bsakaguchi · 2 comments

bsakaguchi commented

2026-10-15 18:27:33 +00:00

Owner

Originally created by @Cjy-CN on GitHub (Oct 12, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/2149

Before submitting

I searched the open and closed issues and pull requests for a related proposal.
I removed credentials, tokens, private paths, and sensitive target data.

Area

Setup, packaging, or upgrade

Current limitation

DeepSeek Harness (dsh) support is already implemented on main in merged PR #1929, following #1839. However, the npm latest release is still 6.4.0, which does not include automatic DSH setup.

Checked on 2026-10-12:

npm view rea-agents dist-tags.latest gitHead --json

{
  "dist-tags.latest": "6.4.0",
  "gitHead": "a56f7bb668ab23fec8d33f7af353ac7ed2fe1895"
}

The installation guide explicitly states that dsh is main-only and that the published release rejects this client. This is a release availability request, rather than another request to implement DSH support.

Use cases

DSH users want to install REA through npm and use the documented setup --client dsh and doctor --client dsh workflows, without cloning and maintaining a source build or manually editing Cordis YAML configuration.

Desired outcome and success criteria

Could you prioritize publishing an npm release that includes the merged DSH integration? The open 6.5.0 release PR #1693 already lists #1929 in its release notes, so making that release available on npm would address this gap.

After publication, users should be able to run:

npx rea-agents@latest setup --client dsh --dry-run --json
npx rea-agents@latest doctor --client dsh --json

The first command should accept dsh and produce a setup plan. The second should accept dsh and diagnose the registration, even if setup has not yet been applied.

If publication is currently blocked, an update on the blocker or expected release timing would help users decide whether to wait or build from source.

Alternatives considered

Building main or configuring DSH manually are available workarounds, but they add installation and maintenance steps for users who prefer the npm release workflow.

References

#1839 — original DSH client support request
#1929 — merged setup, doctor, and uninstall integration
#1693 — open npm 6.5.0 release PR
Release/main boundary
DeepSeek Harness installation documentation

Originally created by @Cjy-CN on GitHub (Oct 12, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/2149 ### Before submitting - [x] I searched the open and closed issues and pull requests for a related proposal. - [x] I removed credentials, tokens, private paths, and sensitive target data. ### Area Setup, packaging, or upgrade ### Current limitation DeepSeek Harness (`dsh`) support is already implemented on `main` in merged PR #1929, following #1839. However, the npm `latest` release is still `6.4.0`, which does not include automatic DSH setup. Checked on 2026-10-12: ```sh npm view rea-agents dist-tags.latest gitHead --json ``` ```json { "dist-tags.latest": "6.4.0", "gitHead": "a56f7bb668ab23fec8d33f7af353ac7ed2fe1895" } ``` The installation guide explicitly states that `dsh` is main-only and that the published release rejects this client. This is a release availability request, rather than another request to implement DSH support. ### Use cases DSH users want to install REA through npm and use the documented `setup --client dsh` and `doctor --client dsh` workflows, without cloning and maintaining a source build or manually editing Cordis YAML configuration. ### Desired outcome and success criteria Could you prioritize publishing an npm release that includes the merged DSH integration? The open 6.5.0 release PR #1693 already lists #1929 in its release notes, so making that release available on npm would address this gap. After publication, users should be able to run: ```sh npx rea-agents@latest setup --client dsh --dry-run --json npx rea-agents@latest doctor --client dsh --json ``` The first command should accept `dsh` and produce a setup plan. The second should accept `dsh` and diagnose the registration, even if setup has not yet been applied. If publication is currently blocked, an update on the blocker or expected release timing would help users decide whether to wait or build from source. ### Alternatives considered Building `main` or configuring DSH manually are available workarounds, but they add installation and maintenance steps for users who prefer the npm release workflow. ### References - #1839 — original DSH client support request - #1929 — merged setup, doctor, and uninstall integration - #1693 — open npm 6.5.0 release PR - [Release/main boundary](https://github.com/morluto/rea/blob/main/docs/installation.md#released-package-and-main) - [DeepSeek Harness installation documentation](https://github.com/morluto/rea/blob/main/docs/installation.md#deepseek-harness)

bsakaguchi added the

area: build

enhancement

P2: medium

labels

2026-10-15 18:27:33 +00:00

bsakaguchi commented

2026-10-15 18:27:34 +00:00

Author

Owner

@matbrgz commented on GitHub (Oct 12, 2026):

Release Triage Notes

PR #1929 introduced DeepSeek Harness (dsh) client integration to main. It will become available on npm with the next minor release (v6.5.0). In the meantime, users requiring dsh integration can build from main via npm run build:cached.

@matbrgz commented on GitHub (Oct 12, 2026): ### Release Triage Notes PR #1929 introduced DeepSeek Harness (`dsh`) client integration to `main`. It will become available on npm with the next minor release (v6.5.0). In the meantime, users requiring `dsh` integration can build from `main` via `npm run build:cached`.

bsakaguchi referenced this issue

2026-10-15 18:28:32 +00:00

[GH-ISSUE #2383] [Tracker] Audit analysis and debugging coverage for the TIOBE top 100 languages (October 2026) #794

bsakaguchi referenced this issue

2026-10-16 21:15:21 +00:00

[PR #704] [MERGED] fix(native): select concrete arm64e Mach-O slices #2183

bsakaguchi

2026-10-31 00:29:28 +00:00

closed this issue
added
enhancement
and removed
enhancement
labels

bsakaguchi commented

2026-10-31 00:29:29 +00:00

Author

Owner

@morluto commented on GitHub (Oct 18, 2026):

Closing as completed: the published npm release now includes the merged DeepSeek Harness integration (#1929). The public npm registry currently reports rea-agents@6.7.0 as latest, and the immutable 6.7 tag contains the DSH setup/doctor integration and installation guide.

Release: https://github.com/morluto/rea/releases/tag/rea-agents-6.7.0

This pass verified registry metadata and release source. It did not run a new native DSH client session or apply configuration changes.

@morluto commented on GitHub (Oct 18, 2026):  Closing as completed: the published npm release now includes the merged DeepSeek Harness integration (#1929). The public npm registry currently reports `rea-agents@6.7.0` as `latest`, and the immutable 6.7 tag contains the DSH setup/doctor integration and installation guide. Release: https://github.com/morluto/rea/releases/tag/rea-agents-6.7.0 This pass verified registry metadata and release source. It did not run a new native DSH client session or apply configuration changes.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

morluto/rea#704

No description provided.

Rows
Columns