@buildinternet/releases 0.57.0 → 0.58.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/README.md +13 -0
- package/package.json +6 -6
package/README.md
CHANGED
|
@@ -204,6 +204,19 @@ releases login --no-browser # print the URL + code to open yourself (headless /
|
|
|
204
204
|
|
|
205
205
|
This uses the OAuth 2.0 Device Authorization Grant (RFC 8628): the CLI shows a short code, you approve it at [releases.sh/device](https://releases.sh/device) in a signed-in browser, and a **read-only** key is minted and saved to `~/.releases/credentials`. Sign up / sign in to the web app first if you haven't. A read-only key is all that's self-serve today; write/admin keys are closed beta (see above).
|
|
206
206
|
|
|
207
|
+
### Managing keys
|
|
208
|
+
|
|
209
|
+
List, create, and revoke your personal API keys without leaving the terminal:
|
|
210
|
+
|
|
211
|
+
```bash
|
|
212
|
+
releases keys list # your keys (id, scope, prefix, created, expiry)
|
|
213
|
+
releases keys create --name "ci-bot" # mints a read-only key, shown once
|
|
214
|
+
releases keys create --name "ci-bot" --expires-in-days 90
|
|
215
|
+
releases keys revoke <id> # delete a key (confirm, or pass --yes)
|
|
216
|
+
```
|
|
217
|
+
|
|
218
|
+
Keys created here are **read-only** (write/admin are not self-serve). The created key string is shown exactly once — store it then. These commands reuse the session from `releases login`, re-prompting the browser approval only when it has expired; the session is bound to the API environment it was issued against, so switching `RELEASES_API_URL` re-authenticates rather than reusing a key from another environment.
|
|
219
|
+
|
|
207
220
|
### Storing a token directly
|
|
208
221
|
|
|
209
222
|
If you've been issued a token (for example a write/admin key during the closed beta), store it without the browser flow using the `auth` namespace, so you don't need `RELEASES_API_KEY` in your shell every time:
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@buildinternet/releases",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.58.0",
|
|
4
4
|
"description": "The changelog & release-notes registry for developers and AI agents",
|
|
5
5
|
"bin": {
|
|
6
6
|
"releases": "bin/releases"
|
|
@@ -13,11 +13,11 @@
|
|
|
13
13
|
"README.md"
|
|
14
14
|
],
|
|
15
15
|
"optionalDependencies": {
|
|
16
|
-
"@buildinternet/releases-darwin-arm64": "0.
|
|
17
|
-
"@buildinternet/releases-darwin-x64": "0.
|
|
18
|
-
"@buildinternet/releases-linux-x64": "0.
|
|
19
|
-
"@buildinternet/releases-linux-arm64": "0.
|
|
20
|
-
"@buildinternet/releases-windows-x64": "0.
|
|
16
|
+
"@buildinternet/releases-darwin-arm64": "0.58.0",
|
|
17
|
+
"@buildinternet/releases-darwin-x64": "0.58.0",
|
|
18
|
+
"@buildinternet/releases-linux-x64": "0.58.0",
|
|
19
|
+
"@buildinternet/releases-linux-arm64": "0.58.0",
|
|
20
|
+
"@buildinternet/releases-windows-x64": "0.58.0"
|
|
21
21
|
},
|
|
22
22
|
"keywords": [
|
|
23
23
|
"changelog",
|