@mcp-abap-adt/auth-broker 3.0.1 → 3.0.2

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/CHANGELOG.md CHANGED
@@ -11,6 +11,12 @@ Thank you to all contributors! See [CONTRIBUTORS.md](CONTRIBUTORS.md) for the co
11
11
 
12
12
  ## [Unreleased]
13
13
 
14
+ ## [3.0.2] - 2026-09-27
15
+
16
+ ### Changed
17
+
18
+ - **Node.js 26 is supported**: `engines` is `"^22 || ^24 || ^26"`. Under Node 26 npm skipped every release whose `engines` did not admit it and installed the newest one that did — silently an older major, for this package one without the restriction. Measured: `npm i -g @mcp-abap-adt/proxy` on Node 26.7.0 installed 4.2.0 while 5.0.1 was `latest`. The release build runs on Node 22 (it was 18, below `engines`).
19
+
14
20
  ## [3.0.1] - 2026-09-26
15
21
 
16
22
  ### Fixed
package/README.md CHANGED
@@ -26,8 +26,9 @@ authorization code or client credentials) and `mcp-sso` (OIDC and SAML single si
26
26
  npm install @mcp-abap-adt/auth-broker
27
27
  ```
28
28
 
29
- Requires Node.js 22 or 24 (`engines: "^22 || ^24"`), the versions SAP BTP's Cloud Foundry
30
- Node.js buildpack offers.
29
+ Requires Node.js 22, 24 or 26 (`engines: "^22 || ^24 || ^26"`): 22 and 24 are
30
+ the versions SAP BTP's Cloud Foundry Node.js buildpack offers, and 26 is
31
+ supported as well.
31
32
 
32
33
  ## Usage
33
34
 
@@ -206,7 +207,7 @@ const connection = new JwtAbapConnection(config, tokenRefresher);
206
207
  5. The broker no longer writes the client secret into the session store. Read
207
208
  it from the service key store if you relied on finding it in the session.
208
209
  6. `refreshToken()` now forces a new token; it used to return `getToken()`'s.
209
- 7. Node.js 22 or 24; SAML runs need the IdP trust (see *Migrating `mcp-sso`
210
+ 7. Node.js 22, 24 or 26; SAML runs need the IdP trust (see *Migrating `mcp-sso`
210
211
  SAML runs from 2.2.0*).
211
212
 
212
213
  ## Configuration
@@ -857,7 +858,7 @@ With 4.x every `mcp-sso` SAML run (`bearer`, `saml2 --flow pure`, and `mcp-auth
857
858
  `--assertion-flow manual`. For any other `--assertion` from an SP-initiated login:
858
859
  `--authn-request-id`.
859
860
 
860
- Node.js 22 or 24 is required.
861
+ Node.js 22, 24 or 26 is required.
861
862
 
862
863
  ### Utility Script
863
864
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@mcp-abap-adt/auth-broker",
3
- "version": "3.0.1",
3
+ "version": "3.0.2",
4
4
  "description": "Per-destination token broker for SAP BTP and ABAP: sessions and service keys from stores, tokens from an injected provider, results persisted - plus the mcp-auth and mcp-sso CLIs",
5
5
  "main": "dist/index.js",
6
6
  "types": "dist/index.d.ts",
@@ -64,7 +64,7 @@
64
64
  "mcp-sso": "./dist/bin/mcp-sso.js"
65
65
  },
66
66
  "engines": {
67
- "node": "^22 || ^24"
67
+ "node": "^22 || ^24 || ^26"
68
68
  },
69
69
  "dependencies": {
70
70
  "@mcp-abap-adt/auth-providers": "^4.2.0",