@brignano/design 0.1.1 → 0.1.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/LICENSE +21 -0
- package/README.md +16 -1
- package/package.json +1 -1
package/LICENSE
ADDED
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
MIT License
|
|
2
|
+
|
|
3
|
+
Copyright (c) 2026 Anthony Brignano
|
|
4
|
+
|
|
5
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
6
|
+
of this software and associated documentation files (the "Software"), to deal
|
|
7
|
+
in the Software without restriction, including without limitation the rights
|
|
8
|
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
9
|
+
copies of the Software, and to permit persons to whom the Software is
|
|
10
|
+
furnished to do so, subject to the following conditions:
|
|
11
|
+
|
|
12
|
+
The above copyright notice and this permission notice shall be included in all
|
|
13
|
+
copies or substantial portions of the Software.
|
|
14
|
+
|
|
15
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
16
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
17
|
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
18
|
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
19
|
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
20
|
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
|
21
|
+
SOFTWARE.
|
package/README.md
CHANGED
|
@@ -55,7 +55,7 @@ something actually looks different.
|
|
|
55
55
|
|
|
56
56
|
## Releasing
|
|
57
57
|
|
|
58
|
-
The tag is the trigger. `.github/workflows/
|
|
58
|
+
The tag is the trigger. `.github/workflows/publish.yml` publishes to npm on any
|
|
59
59
|
`v*` tag, after checking the tag agrees with `package.json` — npm versions are
|
|
60
60
|
immutable, so a mismatch is caught before it's permanent.
|
|
61
61
|
|
|
@@ -69,4 +69,19 @@ this repo and there should never be one — the runner exchanges its OIDC identi
|
|
|
69
69
|
for a short-lived credential via npm [trusted publishing][tp], which is also what
|
|
70
70
|
produces the provenance attestation. A laptop has no such identity.
|
|
71
71
|
|
|
72
|
+
**The workflow is called `publish.yml` in every repo that publishes a package,
|
|
73
|
+
and that is not cosmetic.** npm's Trusted Publisher form takes the workflow
|
|
74
|
+
filename as part of the OIDC claim, and offers `publish.yml` as its example. Any
|
|
75
|
+
other name is a value you have to remember correctly, from the GitHub side, while
|
|
76
|
+
filling in a form on the npm side. Getting it wrong fails as `ENEEDAUTH` — npm
|
|
77
|
+
declines the exchange, `npm publish` falls back to token auth, and there is no
|
|
78
|
+
token — which names neither the workflow nor the mismatch. Matching the tool's
|
|
79
|
+
default is cheaper than being right every time.
|
|
80
|
+
|
|
81
|
+
Setting up a new package: create `.github/workflows/publish.yml` from this one,
|
|
82
|
+
then add the Trusted Publisher on npmjs.com — publisher GitHub Actions, the org
|
|
83
|
+
and repo, workflow filename `publish.yml`, and **environment name blank**, since
|
|
84
|
+
these workflows declare no `environment:`. Configure it before the first tag, or
|
|
85
|
+
the first publish fails the way this one did.
|
|
86
|
+
|
|
72
87
|
[tp]: https://docs.npmjs.com/trusted-publishers/
|