domainstorm 0.2.3 → 0.2.5
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/README.md +0 -46
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -130,52 +130,6 @@ Output columns:
|
|
|
130
130
|
- `--timeout-ms <n>`
|
|
131
131
|
- `--raw`
|
|
132
132
|
|
|
133
|
-
## Add `NPM_TOKEN` In GitHub (2 Minutes)
|
|
134
|
-
|
|
135
|
-
1. Create an npm Automation token:
|
|
136
|
-
`npmjs.com -> Account Settings -> Access Tokens -> Generate New Token -> Automation`
|
|
137
|
-
2. Open your repo:
|
|
138
|
-
`github.com/tanishqsh/domain-cli`
|
|
139
|
-
3. Go to:
|
|
140
|
-
`Settings -> Secrets and variables -> Actions`
|
|
141
|
-
4. Click:
|
|
142
|
-
`New repository secret`
|
|
143
|
-
5. Set:
|
|
144
|
-
`Name = NPM_TOKEN`
|
|
145
|
-
`Secret = <your npm automation token>`
|
|
146
|
-
6. Save.
|
|
147
|
-
|
|
148
|
-
Now GitHub Actions can publish with `.github/workflows/npm-publish.yml`.
|
|
149
|
-
|
|
150
|
-
## GitHub -> npm Auto Publish
|
|
151
|
-
|
|
152
|
-
The publish workflow triggers on:
|
|
153
|
-
|
|
154
|
-
- GitHub Release published
|
|
155
|
-
- Manual `workflow_dispatch`
|
|
156
|
-
|
|
157
|
-
Workflow path:
|
|
158
|
-
|
|
159
|
-
`/.github/workflows/npm-publish.yml`
|
|
160
|
-
|
|
161
|
-
Important:
|
|
162
|
-
|
|
163
|
-
- Bump `package.json` version before publishing a new release
|
|
164
|
-
- npm will reject already-published versions
|
|
165
|
-
|
|
166
|
-
## Local Publish
|
|
167
|
-
|
|
168
|
-
```bash
|
|
169
|
-
npm login
|
|
170
|
-
npm publish --access public
|
|
171
|
-
```
|
|
172
|
-
|
|
173
|
-
If local provenance is unsupported in your shell/provider, use:
|
|
174
|
-
|
|
175
|
-
```bash
|
|
176
|
-
npm publish --access public --provenance=false
|
|
177
|
-
```
|
|
178
|
-
|
|
179
133
|
## Notes
|
|
180
134
|
|
|
181
135
|
- WHOIS formats vary by registry; treat `likely_available` as a pre-check, not final registrar checkout.
|