@casys/mcp-erpnext 3.1.0-beta.5 → 3.1.0-beta.7

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
@@ -10,12 +10,13 @@ English | [繁體中文](README.zh-TW.md)
10
10
  [![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
11
11
 
12
12
  > [!IMPORTANT]
13
- > **Installing the 3.1 beta:** pin the prerelease while this UX is being
14
- > validated. For npm/Node use `npx -y @casys/mcp-erpnext@3.1.0-beta.3`; for Deno
15
- > use `deno run -A jsr:@casys/mcp-erpnext@3.1.0-beta.3/server`. The moving npm
16
- > alias is `@next`. The beta adds the generic document viewer and attachment
17
- > workflows, so test it with the MCP host your users actually run before
18
- > replacing a stable deployment.
13
+ > **Installing the 3.1 beta:** for npm/Node use
14
+ > `npx -y @casys/mcp-erpnext@next`; for Deno use
15
+ > `deno run -A jsr:@casys/mcp-erpnext@^3.1.0-beta/server`. Both follow the
16
+ > current prerelease JSR has no dist-tags, hence the range there. Exact
17
+ > versions are in the [CHANGELOG](CHANGELOG.md). The beta adds the generic
18
+ > document viewer and attachment workflows, so test it with the MCP host your
19
+ > users actually run before replacing a stable deployment.
19
20
 
20
21
  Let any MCP-compatible AI agent operate your [ERPNext](https://erpnext.com) /
21
22
  Frappe instance — documents, workflows, and interactive viewers inside the host