@mcp-abap-adt/connection 9.0.0 → 9.1.0

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
@@ -5,6 +5,40 @@ All notable changes to the `@mcp-abap-adt/connection` package will be documented
5
5
  The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
6
6
  and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
7
7
 
8
+ ## [9.1.0] - 2026-09-23
9
+
10
+ ### Changed
11
+
12
+ - **`@mcp-abap-adt/interfaces-adt@^8.0.0`** (was `^6.0.0`) and
13
+ **`interfaces-network@^1.1.0`** (was `^1.0.0`).
14
+
15
+ **Nothing this package imports moved or changed.** Of the 15 names it takes
16
+ from the ADT contract, none is a header name and none is Cloud ALM — the two
17
+ groups that left in 8.0.0 — and `IAdtWireResponse` keeps its name and shape,
18
+ now extending `IHttpWireResponse` from `interfaces-network`, which this package
19
+ already declared. 7.0.0's change was `source` leaving six object configs, and
20
+ this package imports no config.
21
+
22
+ **`interfaces-network` had to move with it**, and the reason is worth keeping:
23
+ with `^1.0.0` declared here and `interfaces-adt@8` requiring `^1.1.0`, npm kept
24
+ 1.0.0 at the root and nested 1.1.0 beneath the ADT contract. Two physical
25
+ copies of the same package, silently — which is the cost
26
+ `docs/MIGRATION-9.0.md` describes and the reason this bump is explicit rather
27
+ than left to a caret range.
28
+
29
+ Checked rather than assumed, after installing:
30
+
31
+ ```
32
+ find node_modules -path "*@mcp-abap-adt/interfaces*/package.json"
33
+ ```
34
+
35
+ One copy of each of the four.
36
+
37
+ - `docs/MIGRATION-9.0.md` said in the present tense that the umbrella decides
38
+ which contract version a consumer gets, and that `interfaces-adt` has majors 1
39
+ through 6. The umbrella — `@mcp-abap-adt/interfaces` — was deleted in its
40
+ 52.0.0, for exactly the cost that paragraph describes. It says so now.
41
+
8
42
  ## [Unreleased]
9
43
 
10
44
  ## [9.0.0] - 2026-09-23
@@ -1649,7 +1683,8 @@ const connection = createAbapConnection(config, logger);
1649
1683
  - JWT token refresh now properly handles connection errors (401/403 during initial connect)
1650
1684
  - Permission errors (403 with "ExceptionResourceNoAccess") no longer trigger JWT refresh loops
1651
1685
  - Proper separation: base class handles HTTP/session, concrete classes handle auth-specific errors
1652
- [Unreleased]: https://github.com/fr0ster/mcp-abap-connection/compare/v8.0.1...HEAD
1686
+ [Unreleased]: https://github.com/fr0ster/mcp-abap-connection/compare/v9.1.0...HEAD
1687
+ [9.1.0]: https://github.com/fr0ster/mcp-abap-connection/compare/v9.0.0...v9.1.0
1653
1688
  [9.0.0]: https://github.com/fr0ster/mcp-abap-connection/compare/v8.1.0...v9.0.0
1654
1689
  [8.1.0]: https://github.com/fr0ster/mcp-abap-connection/compare/v8.0.1...v8.1.0
1655
1690
  [8.0.1]: https://github.com/fr0ster/mcp-abap-connection/compare/v8.0.0...v8.0.1
@@ -69,9 +69,16 @@ package you get. It carries its own ranges — `interfaces-adt: ^6.0.0`,
69
69
  `interfaces-auth: ^1.0.0`, and so on. A consumer who also names a contract
70
70
  package directly, at a version outside those ranges, ends up with two physical
71
71
  copies in the tree: the direct one at the root, the umbrella's nested beneath
72
- it. That is observable today — `interfaces-adt` has published majors 1 through
73
- 6, so a project on `interfaces-adt@4` plus the umbrella gets 4 at the root and 6
74
- underneath.
72
+ it. That was observable when this was written — `interfaces-adt` had published
73
+ majors 1 through 6, so a project on `interfaces-adt@4` plus the umbrella got 4
74
+ at the root and 6 underneath.
75
+
76
+ > **The umbrella is gone.** `@mcp-abap-adt/interfaces` was deleted in its 52.0.0
77
+ > — decision 34 in `mcp-abap-adt-interfaces` — for exactly the cost this
78
+ > paragraph describes, measured across the family rather than argued. npm still
79
+ > serves 51.0.0 to anyone pinned to it, so the reasoning below still applies to
80
+ > them; there is simply nothing left to migrate *to* except naming the packages,
81
+ > which is what this document already asks for.
75
82
 
76
83
  Two copies are harmless everywhere their shapes agree, because TypeScript is
77
84
  structural. They stop being harmless exactly where the shapes differ — and then
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@mcp-abap-adt/connection",
3
- "version": "9.0.0",
3
+ "version": "9.1.0",
4
4
  "description": "ABAP connection layer for MCP ABAP ADT server",
5
5
  "main": "dist/index.js",
6
6
  "types": "dist/index.d.ts",
@@ -53,9 +53,9 @@
53
53
  "node": ">=18.0.0"
54
54
  },
55
55
  "dependencies": {
56
- "@mcp-abap-adt/interfaces-adt": "^6.0.0",
56
+ "@mcp-abap-adt/interfaces-adt": "^8.0.0",
57
57
  "@mcp-abap-adt/interfaces-auth": "^1.1.0",
58
- "@mcp-abap-adt/interfaces-network": "^1.0.0",
58
+ "@mcp-abap-adt/interfaces-network": "^1.1.0",
59
59
  "@mcp-abap-adt/interfaces-utils": "^1.0.0",
60
60
  "axios": "^1.16.0",
61
61
  "commander": "^14.0.3",