@buildinternet/releases 0.44.0 → 0.45.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 +22 -1
- package/package.json +6 -6
package/README.md
CHANGED
|
@@ -67,20 +67,41 @@ On an interactive terminal, a persistent, self-resolving notice on the landing s
|
|
|
67
67
|
|
|
68
68
|
```bash
|
|
69
69
|
releases search "authentication"
|
|
70
|
+
releases search "slack integration" --since 90d # filter release hits by publish date
|
|
70
71
|
releases tail next-js # or `releases tail -f` to follow new releases
|
|
71
72
|
releases tail src_abc123 # IDs work everywhere a slug does
|
|
73
|
+
releases tail --since 30d # only releases from the last 30 days
|
|
72
74
|
releases list --category ai
|
|
73
75
|
releases get vercel # org, product, or source
|
|
74
76
|
releases get org_abc123 # typed IDs are accepted
|
|
75
77
|
releases org overview vercel # full AI-generated overview for an org
|
|
76
78
|
releases stats
|
|
79
|
+
releases feedback "great tool, here's an idea…" # send feedback to the maintainers
|
|
77
80
|
```
|
|
78
81
|
|
|
79
82
|
Every command that takes an org / product / source / release identifier accepts the typed ID form (`org_…`, `prod_…`, `src_…`, `rel_…`) interchangeably with the slug. IDs are stable across renames; slugs are friendlier when typing. Sources and products also accept the `org/slug` coordinate form (e.g. `vercel/next-js`).
|
|
80
83
|
|
|
84
|
+
`search` and `tail`/`latest` accept `--since` and `--until` to bound releases by publish date — an ISO date (`2026-01-01`) or relative shorthand (`90d`, `4w`, `6m`, `2y`). On `search` the window applies to release hits only.
|
|
85
|
+
|
|
81
86
|
Every reader command supports `--json` for machine-readable output. List commands emit a `{ items, pagination }` envelope — parse with `jq '.items[]'`, and check `.pagination.hasMore` before assuming you've seen every row. Nested `metadata` fields are returned as parsed objects (no `fromjson` needed). `org get` includes a short overview preview (with a stale warning when more than 30 days old); `org overview <identifier>` prints the full body.
|
|
82
87
|
|
|
83
|
-
|
|
88
|
+
The release reader commands (`get`, `search`, `tail`/`latest`) return a **slim** release shape by default — `id`, `version`, `title`, `summary`, a markdown-stripped `excerpt`, `url`, `publishedAt`, nested `source`/`org`, and `contentChars`/`contentTokens` size hints — so agents aren't billed tokens for storage/pipeline internals. Pass `--full` to recover the complete payload (`content`, `contentHash`, `composition`, the `title*` variants, …). Note this is the inverse of the catalog `list` command, which is verbose by default and opts _into_ a lightweight shape with `--compact`.
|
|
89
|
+
|
|
90
|
+
Tabular reader commands fit themselves to the terminal width when stdout is a TTY (column truncation with `…`) and switch to bare TSV when piped — no headers, no color, no truncation — so `releases org list | cut -f2` works without parsing ANSI. `COLUMNS=<n>` overrides the detected width. For complete, parseable output prefer `--json`. The `search` / `tail`/`latest` human view is a single aligned row per release (identity · description · relative age · dimmed `rel_…`); `search` adds a cleaned, markdown-stripped excerpt under each hit.
|
|
91
|
+
|
|
92
|
+
### Feedback
|
|
93
|
+
|
|
94
|
+
Tell the maintainers about a bug, an idea, or anything else. No API key or account required:
|
|
95
|
+
|
|
96
|
+
```bash
|
|
97
|
+
releases feedback "tail -f reconnects slowly on flaky wifi" # one-shot message
|
|
98
|
+
releases feedback --type bug # prompt for the text (interactive)
|
|
99
|
+
echo "longer write-up…" | releases feedback # pipe from stdin
|
|
100
|
+
releases feedback "love the tool" --contact you@example.com # optional reply-to
|
|
101
|
+
releases feedback "draft" --dry-run --json # preview the payload, send nothing
|
|
102
|
+
```
|
|
103
|
+
|
|
104
|
+
With no message argument in an interactive terminal, `feedback` prompts for the text (and an optional contact); otherwise pass it inline or pipe via stdin. `--type` accepts `bug`, `idea`, or `other`. Maintainers with admin access review submissions via `releases admin feedback list` (filter by `--type` / `--status`, paginate with `--cursor`).
|
|
84
105
|
|
|
85
106
|
### MCP
|
|
86
107
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@buildinternet/releases",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.45.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.45.0",
|
|
17
|
+
"@buildinternet/releases-darwin-x64": "0.45.0",
|
|
18
|
+
"@buildinternet/releases-linux-x64": "0.45.0",
|
|
19
|
+
"@buildinternet/releases-linux-arm64": "0.45.0",
|
|
20
|
+
"@buildinternet/releases-windows-x64": "0.45.0"
|
|
21
21
|
},
|
|
22
22
|
"keywords": [
|
|
23
23
|
"changelog",
|