@getpeppr/cli 0.8.0 → 0.8.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 +29 -0
- package/dist/index.js +5264 -0
- package/dist/index.js.map +1 -0
- package/package.json +4 -1
package/CHANGELOG.md
CHANGED
|
@@ -4,6 +4,35 @@ All notable changes to `@getpeppr/cli` are documented here.
|
|
|
4
4
|
|
|
5
5
|
The CLI bundles `@getpeppr/sdk` into its published artifact (tsup `noExternal`), so `validate`, `convert` and `init` run the SDK's validators, country rules and UBL builder locally — an SDK release only reaches CLI users once the CLI is rebundled. Rebundle-only releases are listed with the SDK version they ship.
|
|
6
6
|
|
|
7
|
+
## [0.8.2] — 2026-08-21
|
|
8
|
+
|
|
9
|
+
**`getpeppr lookup` accepts both spellings of a scheme** (GPR-1116). A Peppol
|
|
10
|
+
scheme is published twice — under its numeric EAS code (`9932`) and under a
|
|
11
|
+
symbolic form (`GB:VAT`) — and 98 of the code list's 105 entries contain a
|
|
12
|
+
colon in that symbolic form, the same character that separates a scheme from
|
|
13
|
+
its value. Splitting by position therefore turned `GB:VAT:123456789` into
|
|
14
|
+
scheme `GB` and value `VAT:123456789`: both wrong, and silently so.
|
|
15
|
+
|
|
16
|
+
`lookup`, the directory client and the `send` template all resolved the split
|
|
17
|
+
by position; they now resolve it against the code list. This has been fixed in
|
|
18
|
+
the gateway and the SDK since 4.4.0 — **the CLI kept the old behaviour until
|
|
19
|
+
this release**, because its copy of that logic is its own.
|
|
20
|
+
|
|
21
|
+
Rebundles `@getpeppr/sdk` **4.5.0** (was 4.4.0). Nothing in the CLI calls the
|
|
22
|
+
new `importFile({ sender })`, so the bundle refresh changes no CLI behaviour on
|
|
23
|
+
its own — it is listed because a bundled SDK only reaches CLI users when this
|
|
24
|
+
package is republished.
|
|
25
|
+
|
|
26
|
+
## [0.8.1] — 2026-08-19
|
|
27
|
+
|
|
28
|
+
Republish of 0.8.0 with the actual code in the tarball. The 0.8.0 tarball on
|
|
29
|
+
the registry shipped **without `dist/`** — three files, no binary — because
|
|
30
|
+
this package had no `prepack`/`prepublishOnly` guards and was published from a
|
|
31
|
+
tree where the bundle had never been built. 0.8.0 is deprecated on the
|
|
32
|
+
registry; this version is identical in content and adds the guards so a
|
|
33
|
+
dist-less publish can never happen again (`prepack` builds, `prepublishOnly`
|
|
34
|
+
runs the tests, `pretest` builds first — the same arming the SDK has).
|
|
35
|
+
|
|
7
36
|
## [0.8.0] — 2026-08-19
|
|
8
37
|
|
|
9
38
|
**`getpeppr whoami`** — show the Peppol identity of the account behind your
|