@prooftell/node-red-prooftell 1.0.0 → 1.0.1

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.
Files changed (2) hide show
  1. package/README.md +7 -4
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -88,11 +88,14 @@ is read from the environment only.
88
88
  The package is published by GitHub Actions with npm provenance, from `.github/workflows/release-node-red.yml` at the
89
89
  root of [prooftell/integrations](https://github.com/prooftell/integrations).
90
90
 
91
- 1. Once: the repository secret `NPM_TOKEN` publishes the first release (the package does not exist on npm before
92
- it); then npm's trusted publishing — on npmjs.com, the package's settings, Publish access → Trusted Publishers →
93
- GitHub Actions, owner `prooftell`, repository `integrations`, workflow `release-node-red.yml`.
91
+ 1. Once: the first release needs the repository secret `NPM_TOKEN` (the package does not exist on npm before it): a
92
+ granular token with Read and write on all packages and Bypass two-factor authentication, or the publish stops at
93
+ npm's one-time password. Then npm's trusted publishing — on npmjs.com, the package's settings, Publish access →
94
+ Trusted Publishers → GitHub Actions, owner `prooftell`, repository `integrations`, workflow
95
+ `release-node-red.yml`, "Allow npm publish" ticked — and the secret and the token deleted. npm expires a new trusted publisher that no successful publish has used within 2 days (then: delete it,
96
+ create it again and release within 2 days); the token-free path was first proven with 1.0.1.
94
97
  2. For each release: bump `version` in `package.json`, commit, then tag that commit `node-red-v<version>`
95
- (`git tag node-red-v1.0.0 && git push origin node-red-v1.0.0`). The workflow tests, checks that the tag names the
98
+ (`git tag node-red-v1.0.1 && git push origin node-red-v1.0.1`). The workflow tests, checks that the tag names the
96
99
  version, and publishes.
97
100
  3. For the Flow Library, once: on https://flows.nodered.org, signed in with GitHub, + → Node, the package's name. It
98
101
  is listed at once; a new version is picked up from its page's "request refresh" link, or by submitting again.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@prooftell/node-red-prooftell",
3
- "version": "1.0.0",
3
+ "version": "1.0.1",
4
4
  "description": "ProofTell for Node-RED: look up a phone number, verify an email address, look up an IP address, or assess the risk of an identity, with one API key.",
5
5
  "license": "MIT",
6
6
  "homepage": "https://prooftell.com/integrations?utm_source=node-red&utm_medium=integration",