@buildinternet/releases 0.80.1 → 0.81.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 +3 -3
  2. package/package.json +6 -6
package/README.md CHANGED
@@ -103,7 +103,7 @@ releases json validate releases.json # check a releases.json manife
103
103
  Point any MCP-compatible agent at the hosted server:
104
104
 
105
105
  ```bash
106
- npx mcp-remote https://mcp.releases.sh/mcp
106
+ npx mcp-remote https://agents.releases.sh/mcp
107
107
  ```
108
108
 
109
109
  This repo is also a Claude Code marketplace with the `releases` plugin — hosted MCP tools, a `/releases` lookup command, and auto-trigger skills:
@@ -130,9 +130,9 @@ releases login # opens your browser to approve, then saves the key
130
130
  releases login --no-browser # print the URL + code to open yourself (headless / SSH)
131
131
  ```
132
132
 
133
- This uses the OAuth 2.0 Device Authorization Grant (RFC 8628): approve a short code at [releases.sh/device](https://releases.sh/device) in a signed-in browser, and a read-only key is saved to `~/.releases/credentials` (`0600`). Manage keys with `releases keys list` / `create` / `revoke`.
133
+ This uses the OAuth 2.0 Device Authorization Grant (RFC 8628): approve a short code at [releases.sh/device](https://releases.sh/device) in a signed-in browser, and a read-only key is saved to `~/.releases/credentials` (`0600`) — **the browser session itself is never saved**, only that key. Manage keys with `releases keys list` / `create` / `revoke`; each of those opens its own fresh browser approval and signs out again once the command finishes, rather than reusing a stored session (add `--no-browser` to print the URL + code instead, same as `login`).
134
134
 
135
- If you've verified ownership of a source's domain, mint a `publish-token` scoped to that one source — used by the [`publish-changelog` GitHub Action](https://releases.sh/docs/integrations/github-actions) as `RELEASES_API_TOKEN`:
135
+ If you've verified ownership of a source's domain, mint a `publish-token` scoped to that one source — used by the [`publish-changelog` GitHub Action](https://releases.sh/docs/integrations/github-actions) as `RELEASES_API_TOKEN`. Like `releases keys`, this opens its own browser approval each time:
136
136
 
137
137
  ```bash
138
138
  releases publish-token create --source src_… | gh secret set RELEASES_API_TOKEN
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@buildinternet/releases",
3
- "version": "0.80.1",
3
+ "version": "0.81.1",
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.80.1",
17
- "@buildinternet/releases-darwin-x64": "0.80.1",
18
- "@buildinternet/releases-linux-x64": "0.80.1",
19
- "@buildinternet/releases-linux-arm64": "0.80.1",
20
- "@buildinternet/releases-windows-x64": "0.80.1"
16
+ "@buildinternet/releases-darwin-arm64": "0.81.1",
17
+ "@buildinternet/releases-darwin-x64": "0.81.1",
18
+ "@buildinternet/releases-linux-x64": "0.81.1",
19
+ "@buildinternet/releases-linux-arm64": "0.81.1",
20
+ "@buildinternet/releases-windows-x64": "0.81.1"
21
21
  },
22
22
  "keywords": [
23
23
  "changelog",