@ricardochen1996/browser-use-mcp 0.1.0 → 0.1.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.
package/CHANGELOG.md CHANGED
@@ -7,6 +7,25 @@ uses [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
7
7
 
8
8
  ## [Unreleased]
9
9
 
10
+ ## [0.1.1] - 2026-10-27
11
+
12
+ Release tooling and documentation only: the server behaves exactly as 0.1.0.
13
+
14
+ ### Changed
15
+
16
+ - **npm Trusted Publishing.** A `vX.Y.Z` tag release now publishes through npm's OIDC trusted
17
+ publishing when no `NPM_TOKEN` secret is configured: the package names this repository,
18
+ `.github/workflows/release.yml` and the `npm` environment, so npm exchanges the job's short-lived
19
+ OIDC token for publish access and generates provenance without a long-lived token. A repository
20
+ that adds an `NPM_TOKEN` secret keeps working the old way.
21
+ - GitHub Actions runs the unit suite on Node 22.19 and 24 and every end-to-end suite as its own
22
+ annotated step on Ubuntu (Chrome plus a managed Python 3.12 environment); a failing unit test is
23
+ published as an annotation, so a red run is diagnosable from the run page without the job log.
24
+ - The release workflow fetches annotated tag objects explicitly (checkout can leave a lightweight
25
+ ref), refuses to continue when the tag or version disagree, skips a version that is already on
26
+ npm, and attaches the verified `dist/` tarball to the GitHub Release.
27
+ - README (English and Chinese) documents the trusted-publisher path and the tag workflow.
28
+
10
29
  ## [0.1.0] - 2026-10-27
11
30
 
12
31
  The first public version of `browser-use-mcp`: an MCP server that gives any agent a browser it can
@@ -161,5 +180,6 @@ These are the pre-release fixes that made the first version safe to publish.
161
180
  - `browser-use-mcp` is MIT licensed and bundles or vendors MIT work from `dsh-browser-use`,
162
181
  `jev-ultrafast` and `browser-harness`; see [NOTICE](NOTICE).
163
182
 
164
- [Unreleased]: https://github.com/ricardochen1996/browser-use-mcp/compare/v0.1.0...HEAD
183
+ [Unreleased]: https://github.com/ricardochen1996/browser-use-mcp/compare/v0.1.1...HEAD
184
+ [0.1.1]: https://github.com/ricardochen1996/browser-use-mcp/releases/tag/v0.1.1
165
185
  [0.1.0]: https://github.com/ricardochen1996/browser-use-mcp/releases/tag/v0.1.0
package/README.md CHANGED
@@ -445,8 +445,12 @@ into a test state root on their first run. Release history is in [CHANGELOG.md](
445
445
 
446
446
  **Releases** are tagged `vX.Y.Z` on `main`; the [release workflow](.github/workflows/release.yml)
447
447
  validates the annotated tag against `package.json`, reruns CI (unit plus real-browser e2e), publishes
448
- to npm with provenance using the `NPM_TOKEN` repository secret, and creates the GitHub Release. Bump
449
- the version, add its `CHANGELOG.md` section, then `git tag -a vX.Y.Z -m "vX.Y.Z"` and push the tag.
448
+ to npm with provenance, and creates the GitHub Release with the verified tarball attached. It accepts
449
+ either an `NPM_TOKEN` repository secret (an automation or publish-capable granular token) or npm
450
+ **Trusted Publishing**: name this repository and `.github/workflows/release.yml` as the package's
451
+ trusted publisher and the OIDC token of the job is used instead. An already-published version is
452
+ skipped, so a re-run only refreshes the GitHub Release. Bump the version, add its `CHANGELOG.md`
453
+ section, then `git tag -a vX.Y.Z -m "vX.Y.Z"` and push the tag.
450
454
 
451
455
  ---
452
456
 
package/README.zh-CN.md CHANGED
@@ -321,7 +321,7 @@ npm run doctor # CLI 自检
321
321
 
322
322
  默认测试不花模型调用、不需要任何凭据;e2e 测试首次运行会把引擎装进一个测试用的状态根。版本历史见 [CHANGELOG.md](CHANGELOG.md)。
323
323
 
324
- **发布**:在 `main` 上打标注 tag `vX.Y.Z`,[release 工作流](.github/workflows/release.yml) 会校验 tag 与 `package.json` 一致、重跑 CI(单元 + 真浏览器 e2e)、用仓库 secret `NPM_TOKEN` 带 provenance 发布到 npm,并创建 GitHub Release。流程是幂等的:已发布的版本会被跳过,不会让重跑失败。
324
+ **发布**:在 `main` 上打标注 tag `vX.Y.Z`,[release 工作流](.github/workflows/release.yml) 会校验 tag 与 `package.json` 一致、重跑 CI(单元 + 真浏览器 e2e)、带 provenance 发布到 npm,并创建 GitHub Release,附上校验过的 tarball。凭据二选一:仓库 secret `NPM_TOKEN`(automation 或带 publish 权限的 granular token),或在 npm 上把本仓库与 `.github/workflows/release.yml` 配成 **Trusted Publisher**,工作流会用 OIDC 换取短期发布凭据。已发布的版本会被跳过,重跑只刷新 GitHub Release。
325
325
 
326
326
  ---
327
327
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ricardochen1996/browser-use-mcp",
3
- "version": "0.1.0",
3
+ "version": "0.1.1",
4
4
  "description": "An MCP server that gives any agent a browser it can see and click: the page is read as an indexed action space, and every step is one guarded operation on an observed target.",
5
5
  "type": "module",
6
6
  "license": "MIT",