@particle-academy/resend-js 0.3.0 → 0.3.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 +54 -0
- package/package.json +4 -3
package/CHANGELOG.md
CHANGED
|
@@ -7,6 +7,59 @@ The four packages share one version, because they are generated from one
|
|
|
7
7
|
`provider/` definition and a version that meant something different in each
|
|
8
8
|
would be a version nobody could reason about.
|
|
9
9
|
|
|
10
|
+
## [0.3.2] — 2026-09-06
|
|
11
|
+
|
|
12
|
+
### Changed
|
|
13
|
+
|
|
14
|
+
- **Published through npm Trusted Publishing, so these packages now carry PROVENANCE.**
|
|
15
|
+
|
|
16
|
+
Every earlier release went out under a scope-wide npm token. This one is
|
|
17
|
+
published by an OIDC exchange from the release workflow itself, and npm records
|
|
18
|
+
which workflow in which repository built it. `npm view @particle-academy/resend-ui@0.3.2`
|
|
19
|
+
shows the attestation; releases before this one have none.
|
|
20
|
+
|
|
21
|
+
What it buys a consumer: the tarball on the registry can be tied to a public
|
|
22
|
+
commit and a public workflow run, rather than to whoever held a token. What it
|
|
23
|
+
does not buy: nothing about the code changed, and the runtime behaviour of all
|
|
24
|
+
four packages is identical to 0.3.1.
|
|
25
|
+
|
|
26
|
+
The release exists to establish that the publisher is configured for this
|
|
27
|
+
package. Trusted Publishers are per package, so a green run for one says nothing
|
|
28
|
+
about the next — this is the first of forty-six, and it is deliberately one
|
|
29
|
+
rather than four.
|
|
30
|
+
|
|
31
|
+
- **`repository.directory` in the npm packages.**
|
|
32
|
+
|
|
33
|
+
`@particle-academy/resend-ui` and `@particle-academy/resend-js` live at
|
|
34
|
+
`packages/ui` and `packages/js` inside the provider repo. npm's `repository`
|
|
35
|
+
field now says so, which makes the "Repository" link on each package page point
|
|
36
|
+
at the package rather than at the repository root.
|
|
37
|
+
|
|
38
|
+
## [0.3.1] — 2026-08-24
|
|
39
|
+
|
|
40
|
+
### Fixed
|
|
41
|
+
|
|
42
|
+
- **`@particle-academy/resend-js` now accepts a RANGE of `@particle-academy/resend-ui`, not one exact version.**
|
|
43
|
+
|
|
44
|
+
It peer-depended on `@particle-academy/resend-ui` at exactly the release it shipped with. That is the
|
|
45
|
+
strict form of the thing the kit's own rule forbids — a first-party sibling gets
|
|
46
|
+
a range — and the same block applied the rule correctly to its other two
|
|
47
|
+
dependencies. It was this one pair that slipped.
|
|
48
|
+
|
|
49
|
+
What it cost: ship `@particle-academy/resend-ui` with a fixed help string and every consumer on the
|
|
50
|
+
previous `@particle-academy/resend-js` had an **unmet peer**, which npm 7+ errors on. A documentation
|
|
51
|
+
patch could not be delivered without a matching runtime release, and a routine
|
|
52
|
+
`npm update` that moved the ui package alone broke the install.
|
|
53
|
+
|
|
54
|
+
The coupling is real and is not being loosened away. The ui package emits the
|
|
55
|
+
config schema and the js package implements against it, so a ui that adds a
|
|
56
|
+
field to a js that ignores it is silently wrong. But a PATCH is non-additive by
|
|
57
|
+
definition and a MINOR is where a field can appear — so `>=0.3.1 <0.4.0` is the
|
|
58
|
+
coupling that actually exists rather than the strictest one expressible.
|
|
59
|
+
|
|
60
|
+
Nothing else changed. `particle-academy/resend-php` and `fancy-resend` are unaffected; neither has an
|
|
61
|
+
equivalent edge.
|
|
62
|
+
|
|
10
63
|
## [0.3.0] — 2026-08-24
|
|
11
64
|
|
|
12
65
|
### Added
|
|
@@ -117,3 +170,4 @@ only webhook the vocabulary has ever described.
|
|
|
117
170
|
[0.1.0]: https://github.com/Fancy-Friends/resend/releases/tag/v0.1.0
|
|
118
171
|
[0.2.0]: https://github.com/Fancy-Friends/resend/releases/tag/v0.2.0
|
|
119
172
|
[0.3.0]: https://github.com/Fancy-Friends/resend/releases/tag/v0.3.0
|
|
173
|
+
[0.3.1]: https://github.com/Fancy-Friends/resend/releases/tag/v0.3.1
|
package/package.json
CHANGED
|
@@ -1,10 +1,11 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@particle-academy/resend-js",
|
|
3
|
-
"version": "0.3.
|
|
3
|
+
"version": "0.3.2",
|
|
4
4
|
"description": "Resend for Node — the service descriptor, its faker, its webhook verification, and one function per operation. Plain HTTP on @particle-academy/fancy-connector-core; no vendor SDK.",
|
|
5
5
|
"repository": {
|
|
6
6
|
"type": "git",
|
|
7
|
-
"url": "git+https://github.com/Fancy-Friends/resend.git"
|
|
7
|
+
"url": "git+https://github.com/Fancy-Friends/resend.git",
|
|
8
|
+
"directory": "packages/js"
|
|
8
9
|
},
|
|
9
10
|
"homepage": "https://github.com/Fancy-Friends/resend#readme",
|
|
10
11
|
"bugs": "https://github.com/Fancy-Friends/resend/issues",
|
|
@@ -52,7 +53,7 @@
|
|
|
52
53
|
},
|
|
53
54
|
"peerDependencies": {
|
|
54
55
|
"@particle-academy/fancy-flow": ">=0.47.1 <2.0",
|
|
55
|
-
"@particle-academy/resend-ui": "0.3.0"
|
|
56
|
+
"@particle-academy/resend-ui": ">=0.3.0 <0.4.0"
|
|
56
57
|
},
|
|
57
58
|
"peerDependenciesMeta": {
|
|
58
59
|
"@particle-academy/fancy-flow": {
|