@mcp-abap-adt/auth-broker 5.0.4 → 5.0.6

package/CHANGELOG.md

@@ -9,6 +9,28 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 Thank you to all contributors! See [CONTRIBUTORS.md](../../CONTRIBUTORS.md) for the complete list.
 
+## [5.0.6] - 2026-10-12
+
+The code is the same as 5.0.5.
+
+### Changed
+- Dependency `@mcp-abap-adt/interfaces-utils` `^1.1.1` (was `^1.1.0`), the current release of
+  the contract; its API is unchanged. The other contracts were already current.
+- The lockfile is refreshed from the registry: the tests run on auth-providers 6.0.2,
+  auth-errors 2.2.1 and auth-stores 5.0.1.
+
+## [5.0.5] - 2026-10-12
+
+The library's code and runtime dependencies are the same as 5.0.4. What changed is the
+docs, the README's connection note included, and the tests.
+
+### Changed
+- The tests and live checks run on `@mcp-abap-adt/connection` 15.0.0 (dev dependency
+  `^15.0.0`, on `@mcp-abap-adt/interfaces-adt-connection` 2.0.0, one copy). Their
+  end-to-end suite is renamed `adtConnector.test.ts`.
+- The docs name `connection` 14 or 15 as the connector `getProvider`'s provider is for.
+  The README says why a consumer that also uses `adt-clients` should take 15.
+
 ## [5.0.4] - 2026-10-12
 
 The first published release after 5.0.1. The code is the same as 5.0.2 and 5.0.3, which were

package/README.md

@@ -4,7 +4,7 @@
 A per-destination credential broker for SAP BTP and ABAP systems. For a destination — a name,
 such as `TRIAL` — `getProvider` builds the `IAuthProvider` the destination states (basic, SNC, a
 UAA, OIDC or SAML grant, or a credential handed over) from the *means* in the service key store
-and the *secret* in the session store, ready for a `@mcp-abap-adt/connection` 14 connector, and
+and the *secret* in the session store, ready for a `@mcp-abap-adt/connection` 14 or 15 connector, and
 stores back every token or set of SAML session cookies that provider obtains or renews. The
 token API (`getToken`, `refreshToken`, `createTokenRefresher`) serves whoever wants a token and
 nothing else. It decides nothing about tokens itself: whether the cached token is still good,
@@ -23,7 +23,7 @@ auth-broker-cli 3.1.1, `mcp-auth --env <file>` (or `--destination <name>`) over
 discards its session and logs in anew.
 
 The `mcp-auth` command that writes destination files is
-[`@mcp-abap-adt/auth-broker-cli`](../auth-broker-cli/README.md) (3.1.1, on this version), in the
+[`@mcp-abap-adt/auth-broker-cli`](../auth-broker-cli/README.md) (3.1.2, on this version), in the
 same repository. This package has no `bin`.
 
 ## Features
@@ -43,10 +43,10 @@ same repository. This package has no `bin`.
 npm install @mcp-abap-adt/auth-broker @mcp-abap-adt/auth-providers @mcp-abap-adt/auth-errors @mcp-abap-adt/auth-stores
 ```
 
-5.0.4 depends on `@mcp-abap-adt/auth-providers` `^6.0.0`, `@mcp-abap-adt/auth-errors`
+5.0.6 depends on `@mcp-abap-adt/auth-providers` `^6.0.0`, `@mcp-abap-adt/auth-errors`
 `^2.2.0`, `@mcp-abap-adt/interfaces-auth` `^7.5.0`, `@mcp-abap-adt/interfaces-auth-sap`
 `^3.3.0`, `@mcp-abap-adt/interfaces-auth-broker` `^1.3.0` and
-`@mcp-abap-adt/interfaces-utils` `^1.1.0`. Declare `auth-providers` yourself — the renewal
+`@mcp-abap-adt/interfaces-utils` `^1.1.1`. Declare `auth-providers` yourself — the renewal
 strategies (`refreshThenLogin`, `refreshOnly`) and the interactive strategies come from it —
 and `auth-errors` to read a failure. The stores are yours to choose: `@mcp-abap-adt/auth-stores`
 `^4.0.0`, or any implementation of the `@mcp-abap-adt/interfaces-auth-broker` contracts. Keep
@@ -100,7 +100,7 @@ const provider = await broker.getProvider('TRIAL', { signal: session.signal });
 ```
 
 `getProvider(destination)` returns the `IAuthProvider` (from `@mcp-abap-adt/interfaces-auth`
-7) that a `@mcp-abap-adt/connection` 14 connector takes as it is. The broker reads two stores,
+7) that a `@mcp-abap-adt/connection` 14 or 15 connector takes as it is. The broker reads two stores,
 each for one role:
 
 - **the means** — `authType`, `grantType`, basic's user and password, the SNC, OIDC and SAML
@@ -842,12 +842,15 @@ const current = await tokenRefresher.getToken();
 const renewed = await tokenRefresher.refreshToken();
 ```
 
-A `@mcp-abap-adt/connection` 14 connector takes an `IAuthProvider` instead: give it `await
+A `@mcp-abap-adt/connection` 14 or 15 connector takes an `IAuthProvider` instead: give it `await
 broker.getProvider('TRIAL', { signal })`.
 
 Use `@mcp-abap-adt/connection` 14.1.0 or later. From 14.1.0 its `disconnect()` sends the
 session's logoff. An earlier 14.x left each closed connection's SAP session open until the
 server's own timeout, so a process that connects again and again collects sessions.
+Connection 15 is built on `@mcp-abap-adt/interfaces-adt-connection` 2, as `adt-clients` is.
+If your consumer uses both, choose 15: with 14 it installs two copies of that contract.
+The broker hands either one the same `IAuthProvider`.
 
 ## Errors
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mcp-abap-adt/auth-broker",
-  "version": "5.0.4",
+  "version": "5.0.6",
   "description": "Per-destination credential broker for SAP BTP and ABAP: the IAuthProvider a destination states, built from its key store and session store, with every secret it obtains stored back; and a token API",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
@@ -61,12 +61,12 @@
     "@mcp-abap-adt/interfaces-auth": "^7.5.0",
     "@mcp-abap-adt/interfaces-auth-broker": "^1.3.0",
     "@mcp-abap-adt/interfaces-auth-sap": "^3.3.0",
-    "@mcp-abap-adt/interfaces-utils": "^1.1.0"
+    "@mcp-abap-adt/interfaces-utils": "^1.1.1"
   },
   "devDependencies": {
     "@mcp-abap-adt/auth-mocks": "^0.4.0",
     "@mcp-abap-adt/auth-stores": "^5.0.0",
-    "@mcp-abap-adt/connection": "^14.1.0",
+    "@mcp-abap-adt/connection": "^15.0.0",
     "@mcp-abap-adt/logger": "^0.4.0",
     "@types/js-yaml": "^4.0.9",
     "js-yaml": "^4.1.1",