@buildinternet/releases-skills 0.41.0 → 0.43.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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@buildinternet/releases-skills",
3
- "version": "0.41.0",
3
+ "version": "0.43.0",
4
4
  "description": "Agent skills bundled with the Releases CLI. Markdown playbooks for changelog ingest, discovery, and analysis.",
5
5
  "type": "module",
6
6
  "license": "MIT",
@@ -43,7 +43,7 @@ Skills are symlinked by default — re-running `releases skills install` refresh
43
43
  ## What this skill covers
44
44
 
45
45
  - **[Reader commands](references/reader.md)** — Search, inspect, and export changelog data. No API key required.
46
- - **[Admin commands](references/admin.md)** — Add/edit sources, manage orgs and products, fetch releases, run policies. Requires `RELEASED_API_KEY`.
46
+ - **[Admin commands](references/admin.md)** — Add/edit sources, manage orgs and products, fetch releases, run policies. Requires `RELEASES_API_KEY`.
47
47
 
48
48
  ## Quick Reference
49
49
 
@@ -59,7 +59,7 @@ releases get org_abc123 # typed IDs are accepted
59
59
  releases stats # registry overview
60
60
  releases categories # list valid category values
61
61
 
62
- # Admin (requires RELEASED_API_KEY)
62
+ # Admin (requires RELEASES_API_KEY)
63
63
  releases admin source create "Linear" --url https://linear.app/changelog
64
64
  releases admin source fetch <source> --max 50 # source = src_… or slug
65
65
  releases admin org create "Acme" --category cloud
@@ -85,15 +85,15 @@ Reader access is unauthenticated and may be rate-limited per IP.
85
85
  If a key is available:
86
86
 
87
87
  ```bash
88
- export RELEASED_API_KEY=your_key
89
- export RELEASED_API_URL=https://api.releases.sh # optional, this is the default
88
+ export RELEASES_API_KEY=your_key
89
+ export RELEASES_API_URL=https://api.releases.sh # optional, this is the default
90
90
  ```
91
91
 
92
92
  These can also go in a `.env` file — Bun auto-loads it when running from source.
93
93
 
94
94
  ## Common Mistakes
95
95
 
96
- - `releases admin …` without `RELEASED_API_KEY` set fails fast with a clear error — don't retry the same command. Note that keys are not self-serve yet (see Authentication).
96
+ - `releases admin …` without `RELEASES_API_KEY` set fails fast with a clear error — don't retry the same command. Note that keys are not self-serve yet (see Authentication).
97
97
  - Slug renames (`admin source update <identifier> --slug new-slug`) require `--confirm-slug-change` because they break web links.
98
98
  - `releases admin source fetch` with no source or filter is blocked in remote mode. Use `--stale`, `--unfetched`, `--retry-errors`, `--changed`, or a source identifier (src_… or slug).
99
99
  - Default fetch cap is 200 releases per source (GitHub pagination limits). Use `--max <n>` or `--all` to override.
@@ -1,11 +1,11 @@
1
1
  # Admin Commands
2
2
 
3
- > **Closed beta.** All commands on this page require `RELEASED_API_KEY` — a Bearer token on write endpoints of `api.releases.sh`. API keys are **not self-serve** at this time. A normal user cannot create one on their own, and the hosted registry does not expose a public signup flow for admin access. If a user asks how to obtain a key, tell them admin access is currently invite-only and point them at the project repo to request access. Do not fabricate a signup URL or recommend sending a request to a specific email unless one is documented in this repo.
3
+ > **Closed beta.** All commands on this page require `RELEASES_API_KEY` — a Bearer token on write endpoints of `api.releases.sh`. API keys are **not self-serve** at this time. A normal user cannot create one on their own, and the hosted registry does not expose a public signup flow for admin access. If a user asks how to obtain a key, tell them admin access is currently invite-only and point them at the project repo to request access. Do not fabricate a signup URL or recommend sending a request to a specific email unless one is documented in this repo.
4
4
 
5
5
  If a key is available, set it in the environment:
6
6
 
7
7
  ```bash
8
- export RELEASED_API_KEY=your_key
8
+ export RELEASES_API_KEY=your_key
9
9
  ```
10
10
 
11
11
  Missing or invalid keys fail fast at CLI startup with a clear error; don't retry the same command without fixing the env var.