paperclip-plugin-plica 0.5.0 → 0.6.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 CHANGED
@@ -5,6 +5,37 @@ Short-form. The reader-facing write-up for each version is in
5
5
 
6
6
  ## Unreleased
7
7
 
8
+ - **A failed publish says which credential to go and fix.** npm's two rejections
9
+ here are both misleading: `ENEEDAUTH` in a workflow run means the package has
10
+ no trusted publisher, not that the runner needs `npm adduser`, and a `403`
11
+ from a working token means the token is read-only, not that the account is
12
+ wrong. `scripts/publish-npm.mjs` already knows which credential it used, so it
13
+ now prints the matching explanation. Both are written up in
14
+ [docs/releases/README.md](docs/releases/README.md#what-npms-two-credential-errors-actually-mean).
15
+ - **A refused trusted publish reports the registry's reason, not `ENEEDAUTH`.**
16
+ npm asks GitHub for an OIDC token, trades it with the registry for a publish
17
+ credential, and on refusal discards what the registry said — leaving one error
18
+ that means both "no trusted publisher" and "an entry that does not match this
19
+ run", with a tag push as the only way to tell them apart. The new
20
+ `scripts/diagnose-npm-oidc.mjs` repeats those two requests and prints the
21
+ status and message behind them; a failed publish runs it automatically. It is
22
+ read-only, publishes nothing, and logs no credential.
23
+
24
+ ## 0.6.0
25
+
26
+ - **Releases publish themselves.** Pushing a `v*` tag runs the new
27
+ [`release` workflow](.github/workflows/release.yml), which publishes
28
+ `paperclip-plugin-plica` to npm. It shares one script with a publish by hand
29
+ (`pnpm release:publish`), so both refuse the same things: a tag that disagrees
30
+ with `package.json`, a manifest left on the previous version, a version with
31
+ no changelog entry or release page, and an unclean checkout. `pnpm
32
+ check:release` runs those version checks alone, before there is a tag to
33
+ push. Credentials come from an npm token on the environment — the `NPM_TOKEN`
34
+ Actions secret in CI, the token Paperclip binds to an agent otherwise — or,
35
+ preferably, npm trusted publishing with no token at all; the script prints
36
+ which one it used. See
37
+ [docs/releases/README.md](docs/releases/README.md#publishing-credentials).
38
+
8
39
  ## 0.5.0
9
40
 
10
41
  - **Published to npm as `paperclip-plugin-plica`.** Install it from Paperclip's
package/dist/manifest.js CHANGED
@@ -5,7 +5,7 @@ var PLUGIN_ID = "nickallevato.plugin-plica";
5
5
  var manifest = {
6
6
  id: PLUGIN_ID,
7
7
  apiVersion: 1,
8
- version: "0.5.0",
8
+ version: "0.6.0",
9
9
  displayName: "Plica",
10
10
  description: "Cross-company HUD: company panes, triage, approvals, attention, and briefing.",
11
11
  // The manifest schema has no homepage/repository fields — `author` is a plain
package/dist/ui/index.js CHANGED
@@ -17825,7 +17825,7 @@ function mi({ className: e, ...t }) {
17825
17825
  var ik = {
17826
17826
  id: Wt,
17827
17827
  apiVersion: 1,
17828
- version: "0.5.0",
17828
+ version: "0.6.0",
17829
17829
  displayName: "Plica",
17830
17830
  description: "Cross-company HUD: company panes, triage, approvals, attention, and briefing.",
17831
17831
  // The manifest schema has no homepage/repository fields — `author` is a plain