@mcp-abap-adt/connection 9.4.0 → 9.4.2

package/CHANGELOG.md

@@ -7,6 +7,27 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [9.4.2] - 2026-09-27
+
+### Changed
+
+- **`@mcp-abap-adt/sap-rfc-lite` `^0.2.1`** (was `^0.2.0`). 0.2.0 on npm was
+  packed with a stale `lib/`: its JS client has no `resetServerContext`, so
+  this connector found no reset and fell back to a new RFC connection per
+  stateless call — correct, but a full RFC run took about 1010 s instead of
+  about 684 s. 0.2.1 is packed from `src/`. Raising the minimum makes npm
+  replace a locked 0.2.0 too, since it no longer satisfies the range.
+
+## [9.4.1] - 2026-09-27
+
+### Fixed
+
+- **`sap-abap-auth --version` printed `0.1.0`** — a number written into the CLI, not the package's. It reads `package.json` now.
+
+### Added
+
+- **`version` as a command, and `-v`**, for `sap-abap-auth`: `help` / `--help` / `-h` and `version` / `--version` / `-v` — the same set in every CLI of the family, each answering before anything starts or connects.
+
 ## [9.4.0] - 2026-09-27
 
 ### Changed
@@ -1902,7 +1923,9 @@ 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.4.0...HEAD
+[Unreleased]: https://github.com/fr0ster/mcp-abap-connection/compare/v9.4.2...HEAD
+[9.4.2]: https://github.com/fr0ster/mcp-abap-connection/compare/v9.4.1...v9.4.2
+[9.4.1]: https://github.com/fr0ster/mcp-abap-connection/compare/v9.4.0...v9.4.1
 [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

package/README.md

@@ -294,8 +294,9 @@ on BASIS < 7.50.
 
 Since 9.3.2, LOCK and UNLOCK in stateful mode share the persistent RFC
 conversation; stateless requests use a separate ABAP context. With
-`sap-rfc-lite` 0.2.0 or newer, that context is reset between calls on a kept
-conversation; older clients open one conversation per call. This prevents stale
+`sap-rfc-lite` 0.2.1 or newer (required since 9.4.2), that context is reset
+between calls on a kept conversation; older clients open one conversation per
+call. 0.2.0 on npm lacks the reset in its JS client and behaves like an older one. 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-932-and-933).

package/bin/sap-abap-auth.js

@@ -595,7 +595,7 @@ async function main() {
     .description(
       "CLI utility for authentication in SAP BTP ABAP Environment (Steampunk) via browser. Creates .env file with connection configuration."
     )
-    .version("0.1.0")
+    .version(require("../package.json").version, "-v, --version", "Show version number")
     .helpOption("-h, --help", "Show help for all commands and options");
 
   program
@@ -736,6 +736,14 @@ async function main() {
       }
     });
 
+  // `version` as a command, like every CLI in the family (`help` is commander's).
+  program
+    .command("version")
+    .description("Show version number")
+    .action(() => {
+      console.log(require("../package.json").version);
+    });
+
   // Parse and handle command-line arguments
   program.parse(process.argv);
 

package/docs/STATEFUL_SESSION_GUIDE.md

@@ -62,7 +62,8 @@ BASIS 7.40 and ABAP Cloud were not integration-tested for this change.
 Stateful requests, including LOCK and UNLOCK, share the conversation opened
 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
+(`sap-rfc-lite` 0.2.1, required since 9.4.2; 9.4.0 required 0.2.0, whose npm
+package lacks the reset in its JS client, and 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.
@@ -75,8 +76,8 @@ create, read, two lock/PUT/unlock rounds and delete passed on one connection.
 
 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
+is what every stateless call cost with `sap-rfc-lite` 0.1.x (and with 0.2.0,
+whose npm package lacks the reset), and why 9.4.2 requires 0.2.1. 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.4.0",
+  "version": "9.4.2",
   "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.2.0"
+    "@mcp-abap-adt/sap-rfc-lite": "^0.2.1"
   },
   "devDependencies": {
     "@biomejs/biome": "^2.3.14",