@theokit/di-agent 0.3.0 → 0.4.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 +43 -1
- package/package.json +4 -4
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,40 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.4.0
|
|
4
|
+
|
|
5
|
+
### Minor Changes
|
|
6
|
+
|
|
7
|
+
- 33670b7: Realign the `@theokit/sdk` peer with the SDK this package actually imports.
|
|
8
|
+
|
|
9
|
+
**Install-contract break.** `@theokit/sdk` moves from `^1.3.0` to `>=4.0.1 <5`. An app pinned below
|
|
10
|
+
4 stops satisfying the peer. Minor bump because the version is still 0.x, where minor is the
|
|
11
|
+
breaking slot.
|
|
12
|
+
|
|
13
|
+
The old range described nothing that existed. `src/workflow-builder.ts` imports
|
|
14
|
+
`@theokit/sdk/workflow` at runtime, the package is developed and tested against the modern SDK, and
|
|
15
|
+
the published SDK has been on 4.x for months — so `npm i @theokit/di-agent @theokit/sdk@^4` ended in
|
|
16
|
+
`ERESOLVE`, and pnpm users got a peer warning for a combination that was never supported.
|
|
17
|
+
(usetheokit/theokit-di#40)
|
|
18
|
+
|
|
19
|
+
Verified at both ends of the new range: the suite passes against 4.0.1 and against 4.57.0. The
|
|
20
|
+
`@theokit/sdk` devDependency moves to `^4.57.0` for the same reason the range went stale unnoticed —
|
|
21
|
+
CI was resolving 1.x, compiling against it, and going green on a combination no consumer installs.
|
|
22
|
+
|
|
23
|
+
### Patch Changes
|
|
24
|
+
|
|
25
|
+
- 5bb0600: O peer range do `@theokit/di` deixa de prometer uma versão em que o pacote não funciona.
|
|
26
|
+
|
|
27
|
+
Declarava `^0.1.0-next.0 || ^0.2.0`, e o piso resolvível disso é `0.1.0` — que **não exporta
|
|
28
|
+
`METADATA_KEYS`**, um símbolo que `src/` importa. Um consumidor que resolvesse para 0.1.0 instalava
|
|
29
|
+
sem erro e partia nos decorators.
|
|
30
|
+
|
|
31
|
+
Medido antes de escrever o novo range, versão a versão: `0.1.0` não tem o símbolo, `0.1.1` tem,
|
|
32
|
+
`0.2.0` tem. O range passa a ser `>=0.1.1 <0.3`, que é o que a suíte prova.
|
|
33
|
+
|
|
34
|
+
Encontrado pelo leg `suite at the bottom of every declared range` do dep-check, que instala o piso
|
|
35
|
+
de cada range declarado e corre os testes contra ele — 31 falharam. É a única forma de um piso
|
|
36
|
+
mentiroso aparecer: nada mais no CI instala a versão mínima.
|
|
37
|
+
|
|
3
38
|
All notable changes to `@theokit/di-agent` are documented in this file.
|
|
4
39
|
|
|
5
40
|
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
|
|
@@ -7,6 +42,14 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|
|
7
42
|
|
|
8
43
|
## [Unreleased]
|
|
9
44
|
|
|
45
|
+
### Fixed
|
|
46
|
+
|
|
47
|
+
- Installing this package next to the `@theokit/sdk` it actually needs no longer fails. The declared
|
|
48
|
+
peer range was `^1.3.0` while the package imports `@theokit/sdk/workflow` at runtime and the SDK
|
|
49
|
+
has been on 4.x for months, so `npm i @theokit/di-agent @theokit/sdk@^4` ended in `ERESOLVE` and
|
|
50
|
+
pnpm users got a peer warning for a combination that was never supported. The range is now
|
|
51
|
+
`>=4.0.1 <5`, verified at both ends: the suite passes against 4.0.1 and against 4.57.0. (#40)
|
|
52
|
+
|
|
10
53
|
## [0.3.0] - 2026-08-21
|
|
11
54
|
|
|
12
55
|
### Added
|
|
@@ -32,7 +75,6 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|
|
32
75
|
- JSDoc and comments no longer cite plan tasks or edge-case identifiers that exist in no repository a reader can reach.
|
|
33
76
|
- **Breaking:** `readCronMetadata` and `readHitlMetadata` return a `ReadonlyMap` keyed by method name instead of a single object or `undefined`. `@Cron` and `@Hitl` kept one object per class, so decorating a second method silently discarded the first — a class with two scheduled routines quietly lost one. Both now accumulate per method, like the other fourteen decorators. Migration: `readCronMetadata(C)?.schedule` becomes `readCronMetadata(C).get("methodName")?.schedule`, and an undecorated class yields an empty map rather than `undefined` (#6).
|
|
34
77
|
|
|
35
|
-
|
|
36
78
|
## 0.2.0
|
|
37
79
|
|
|
38
80
|
### Minor Changes
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@theokit/di-agent",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.4.0",
|
|
4
4
|
"description": "Agent-first DI integration for @theokit/di. Ships @InjectAgent() decorator + createAgentProvider() helper that produces a REQUEST-scoped Agent factory — so every HTTP request gets an isolated @theokit/sdk Agent automatically.",
|
|
5
5
|
"license": "Apache-2.0",
|
|
6
6
|
"homepage": "https://github.com/usetheokit/theokit-di#readme",
|
|
@@ -43,13 +43,13 @@
|
|
|
43
43
|
"Theo"
|
|
44
44
|
],
|
|
45
45
|
"peerDependencies": {
|
|
46
|
-
"@theokit/di": "
|
|
47
|
-
"@theokit/sdk": "
|
|
46
|
+
"@theokit/di": ">=0.1.1 <0.3",
|
|
47
|
+
"@theokit/sdk": ">=4.0.1 <5",
|
|
48
48
|
"reflect-metadata": "^0.2.0"
|
|
49
49
|
},
|
|
50
50
|
"devDependencies": {
|
|
51
51
|
"@swc/core": "^1.15.40",
|
|
52
|
-
"@theokit/sdk": "^
|
|
52
|
+
"@theokit/sdk": "^4.57.0",
|
|
53
53
|
"reflect-metadata": "^0.2.0",
|
|
54
54
|
"tsup": "^8.5.0",
|
|
55
55
|
"typedoc": "^0.28.19",
|