@mcp-abap-adt/interfaces-adt-connection 2.0.0 → 3.0.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 +33 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -7,6 +7,39 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|
|
7
7
|
|
|
8
8
|
## [Unreleased]
|
|
9
9
|
|
|
10
|
+
## [3.0.0] - 2026-10-12
|
|
11
|
+
|
|
12
|
+
### Removed (breaking)
|
|
13
|
+
|
|
14
|
+
- **`IAbapRequestOptions.signal`, `ADT_REQUEST_ERROR` and `AdtRequestErrorCode`**
|
|
15
|
+
(added in 2.1.0). A per-request signal has no use against ADT: ABAP neither
|
|
16
|
+
cancels a request that reached it nor rolls back across requests, a
|
|
17
|
+
connection is never shared between threads, and a session closed with a
|
|
18
|
+
logoff releases its locks — measured on premise (BASIS 816, 2026-10-12),
|
|
19
|
+
including a logoff sent while a long request still ran in the same session:
|
|
20
|
+
SAP queued it and the lock was gone afterwards. What a consumer needs at its
|
|
21
|
+
end is the connection's logoff, not a signal.
|
|
22
|
+
|
|
23
|
+
### Migrating from 2.1
|
|
24
|
+
|
|
25
|
+
Drop `signal` from request options and any match on `ADT_REQUEST_ERROR`. Code
|
|
26
|
+
written for 2.0 compiles unchanged.
|
|
27
|
+
|
|
28
|
+
## [2.1.0] - 2026-10-12
|
|
29
|
+
|
|
30
|
+
### Added
|
|
31
|
+
|
|
32
|
+
- **`IAbapRequestOptions.signal?: AbortSignal | undefined`** — the caller no
|
|
33
|
+
longer needs this request. A connection honouring it sends nothing more of
|
|
34
|
+
the request once the signal has aborted: not the request, if it has not left
|
|
35
|
+
yet, and no resend (a CSRF retry, a reconnect). A request already on the wire
|
|
36
|
+
is not recalled — the server may still act on it. Optional: every request
|
|
37
|
+
written for 2.0.0 compiles unchanged, and a connection that ignores the
|
|
38
|
+
field still satisfies `IAbapConnection`.
|
|
39
|
+
- **`ADT_REQUEST_ERROR` / `AdtRequestErrorCode`** — what such a request fails
|
|
40
|
+
with: `ADT_REQUEST_ERROR.ABORTED` (`'ADT_REQUEST_ABORTED'`), as the thrown
|
|
41
|
+
error's `code`. Match on the code, not on a message.
|
|
42
|
+
|
|
10
43
|
## [2.0.0] - 2026-10-05
|
|
11
44
|
|
|
12
45
|
### Changed (breaking)
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@mcp-abap-adt/interfaces-adt-connection",
|
|
3
|
-
"version": "
|
|
3
|
+
"version": "3.0.0",
|
|
4
4
|
"description": "The ABAP connection contract: IAbapConnection, its capability atoms, the wire response and the session error codes",
|
|
5
5
|
"main": "dist/index.js",
|
|
6
6
|
"types": "dist/index.d.ts",
|