@mcp-abap-adt/connection 9.3.3 → 9.3.4

package/CHANGELOG.md

@@ -7,6 +7,17 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [9.3.4] - 2026-09-27
+
+### Changed
+
+- **Release the RFC context reset under an available package version.** npm
+  already contained version `9.3.3`, so this release carries the RFC stateless
+  context reset as `9.3.4`. With `sap-rfc-lite` 0.2.0, stateless calls reuse a
+  conversation and reset its server context after each call; older clients
+  continue to open a conversation per call. See the `9.3.3` entry below for
+  measured behavior and performance.
+
 ## [9.3.3] - 2026-09-27
 
 ### Changed
@@ -1872,7 +1883,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.3...HEAD
+[Unreleased]: https://github.com/fr0ster/mcp-abap-connection/compare/v9.3.4...HEAD
+[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
 [9.3.1]: https://github.com/fr0ster/mcp-abap-connection/compare/v9.3.0...v9.3.1

package/README.md

@@ -298,7 +298,7 @@ conversation; stateless requests use a separate ABAP context. With
 conversation; older clients open one conversation per call. This prevents stale
 package state from causing PAK/058 on later writes or SADT_RESOURCE/007 on a
 read after create. Concurrent calls use a separate conversation. See
-[RFC conversation isolation](./docs/STATEFUL_SESSION_GUIDE.md#rfc-conversation-isolation-933).
+[RFC conversation isolation](./docs/STATEFUL_SESSION_GUIDE.md#rfc-conversation-isolation-932-and-933).
 
 Needs the SAP NW RFC SDK on the machine and `npm install @mcp-abap-adt/sap-rfc-lite`.
 

package/docs/STATEFUL_SESSION_GUIDE.md

@@ -49,7 +49,7 @@ The filter also applies to cookies supplied in request headers and retries.
 | --- | --- |
 | HTTP (on-prem / cloud) | Sends `x-sap-adt-sessiontype: stateful` and the context cookie, when held |
 | Legacy on-prem HTTP | Keeps the context cookie but omits the session-type header |
-| RFC | Uses the persistent conversation for stateful requests; since 9.3.3 resets a kept stateless conversation between calls when supported |
+| RFC | Uses the persistent conversation for stateful requests; since 9.3.4 resets a kept stateless conversation between calls when supported |
 
 A caller-supplied stateful header is also recognized, including by the legacy
 HTTP transport before it removes that header. Custom `IAdtTransport`
@@ -57,10 +57,10 @@ 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 and 9.3.3)
+## RFC conversation isolation (9.3.2–9.3.4)
 
 Stateful requests, including LOCK and UNLOCK, share the conversation opened
-by `connect()`. Since 9.3.3, `sap-rfc-lite` 0.2.0 and newer let stateless calls
+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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mcp-abap-adt/connection",
-  "version": "9.3.3",
+  "version": "9.3.4",
   "description": "ABAP connection layer for MCP ABAP ADT server",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",