@mcp-abap-adt/connection 9.3.4 → 9.4.0

package/CHANGELOG.md

@@ -7,6 +7,25 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [9.4.0] - 2026-09-27
+
+### Changed
+
+- **`@mcp-abap-adt/sap-rfc-lite` `^0.2.0`** (was `^0.1.0 || ^0.2.0`), still an
+  optional dependency. The range let an install that already had 0.1.0 in its
+  lockfile keep it: npm does not move a locked version that still satisfies
+  the range, so 9.3.4's context reset never reached it, and every stateless
+  RFC call opened a conversation of its own (~0.67 s instead of ~0.24 s,
+  measured on an on-premise system). With 0.2.0 required, every stateless
+  call reuses one conversation and resets its server context. A minor
+  release, not a patch: support for 0.1.x ends and the behaviour of an
+  install that had it changes. No API changes.
+
+  **What a consumer does:** reinstall with the SAP NW RFC SDK visible, so the
+  optional native build of 0.2.0 succeeds (npm drops a failed optional build
+  silently). The check for a client without `resetServerContext` stays as a
+  guard; with 0.2.0 it is not taken.
+
 ## [9.3.4] - 2026-09-27
 
 ### Changed
@@ -1883,7 +1902,8 @@ const connection = createAbapConnection(config, logger);
 - JWT token refresh now properly handles connection errors (401/403 during initial connect)
 - Permission errors (403 with "ExceptionResourceNoAccess") no longer trigger JWT refresh loops
 - Proper separation: base class handles HTTP/session, concrete classes handle auth-specific errors
-[Unreleased]: https://github.com/fr0ster/mcp-abap-connection/compare/v9.3.4...HEAD
+[Unreleased]: https://github.com/fr0ster/mcp-abap-connection/compare/v9.4.0...HEAD
+[9.4.0]: https://github.com/fr0ster/mcp-abap-connection/compare/v9.3.4...v9.4.0
 [9.3.4]: https://github.com/fr0ster/mcp-abap-connection/compare/v9.3.3...v9.3.4
 [9.3.3]: https://github.com/fr0ster/mcp-abap-connection/compare/v9.3.2...v9.3.3
 [9.3.2]: https://github.com/fr0ster/mcp-abap-connection/compare/v9.3.1...v9.3.2

package/docs/STATEFUL_SESSION_GUIDE.md

@@ -57,14 +57,14 @@ implementations must read `request.stateful`; the connection no longer adds
 `x-sap-adt-sessiontype` itself. The cookie fix was verified on E19 and E98;
 BASIS 7.40 and ABAP Cloud were not integration-tested for this change.
 
-## RFC conversation isolation (9.3.2–9.3.4)
+## RFC conversation isolation (9.3.2–9.4.0)
 
 Stateful requests, including LOCK and UNLOCK, share the conversation opened
-by `connect()`. Since 9.3.4, `sap-rfc-lite` 0.2.0 and newer let stateless calls
-reuse a second conversation: the transport resets its ABAP server context after
-each call, keeping the RFC logon open. With older clients (0.1.x), or when a
-resettable conversation is busy, each stateless call gets a separate temporary
-conversation. Both `setSessionType('stateful')` and a caller-supplied stateful
+by `connect()`. Stateless calls reuse a second conversation: the transport
+resets its ABAP server context after each call, keeping the RFC logon open
+(`sap-rfc-lite` 0.2.0, required since 9.4.0; 9.3.4 introduced it and still
+accepted 0.1.x). When that conversation is busy with another call, a stateless
+call gets a separate temporary conversation. Both `setSessionType('stateful')` and a caller-supplied stateful
 session header select the persistent conversation.
 
 Previously all RFC requests shared one ABAP session. On E19, saving a package
@@ -73,9 +73,10 @@ with **400 PAK/058, “Package … is already locked”**. Reading immediately a
 creation could fail with **400 SADT_RESOURCE/007**. With separate conversations,
 create, read, two lock/PUT/unlock rounds and delete passed on one connection.
 
-When using `sap-rfc-lite` 0.1.x, each stateless call pays for an RFC logon:
-about 0.5 s on E19, in addition to about 0.1 s for the call. With 0.2.0+, a
-resettable call took about 0.24 s total on E19. Direct connector users must mark
+A resettable call took about 0.24 s total on E19; a temporary conversation
+pays for an RFC logon, about 0.5 s on top of about 0.1 s for the call — which
+is what every stateless call cost with `sap-rfc-lite` 0.1.x, and why 9.4.0
+requires 0.2.0. Direct connector users must mark
 LOCK and UNLOCK stateful to retain their conversation. If disconnect occurs
 while a temporary conversation is logging on, it is closed without sending
 the request; reconnect does not revive that pending request.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mcp-abap-adt/connection",
-  "version": "9.3.4",
+  "version": "9.4.0",
   "description": "ABAP connection layer for MCP ABAP ADT server",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
@@ -63,7 +63,7 @@
     "open": "^11.0.0"
   },
   "optionalDependencies": {
-    "@mcp-abap-adt/sap-rfc-lite": "^0.1.0 || ^0.2.0"
+    "@mcp-abap-adt/sap-rfc-lite": "^0.2.0"
   },
   "devDependencies": {
     "@biomejs/biome": "^2.3.14",