google-services-mcp 0.1.84 → 0.1.85

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 +18 -7
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -88,13 +88,16 @@ everywhere below.
88
88
 
89
89
  - `latest` — stable releases, published automatically when a merge to `main`
90
90
  changes something the package ships
91
- - `beta` — staging builds, published manually from `main`
92
- (e.g. `0.x.x-beta.0`)
91
+ - `beta` — preview builds, not a snapshot of `main`. The tag moves to whichever
92
+ build ran last: a PR branch (each push to a non-draft PR, including the moment
93
+ it is marked ready for review), a `v*-beta*` tag, or a manual run from `main`.
94
+ Installing `@beta` gets you unmerged code that is currently under review.
93
95
 
94
- Try the staging channel without touching your stable install:
96
+ Install a stable version unless you specifically want to try a branch:
95
97
 
96
98
  ```bash
97
- npx -y google-services-mcp@beta --version
99
+ npx -y google-services-mcp@latest --version # stable
100
+ npx -y google-services-mcp@beta --version # preview build
98
101
  ```
99
102
 
100
103
  All publishes are signed with npm **provenance** (trusted publishing via
@@ -303,9 +306,17 @@ All publishing happens from GitHub Actions — no local npm login needed:
303
306
  release. No manual steps. The next version is derived from the last
304
307
  published `latest` on npm, so repeated merges never collide; an
305
308
  intentional minor/major bump in `package.json` is honored.
306
- 2. **Staging** — manual beta builds from `main`: **Actions → CI
307
- → Run workflow**. Publishes a `beta` build (`0.1.1-beta.X`) under the
308
- `beta` dist-tag with provenance.
309
+ 2. **Preview** — the `beta` dist-tag points at the last preview build, and is
310
+ advanced by three things:
311
+
312
+ - a push to a non-draft PR in this repository (including the
313
+ ready-for-review transition), as `<version>-beta.<run_number>`
314
+ - a `v*-beta*` tag push
315
+ - a manual run: **Actions → CI → Run workflow**, which publishes a
316
+ `0.x.x-beta.X` build of `main`
317
+
318
+ `beta` therefore tracks whichever build ran last, not `main`. Use `latest`
319
+ for anything you rely on.
309
320
 
310
321
  Prerelease tags `v*-beta*` publish to `beta` with a prerelease GitHub release
311
322
  (patch/minor builds for milestone testing). Publishing uses npm **trusted
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "google-services-mcp",
3
- "version": "0.1.84",
3
+ "version": "0.1.85",
4
4
  "description": "Gmail MCP server for AI agents — Google Workspace MCP with 100+ tools for Gmail, Calendar, Drive, Docs, Sheets, Meet, and more, multi-account OAuth.",
5
5
  "type": "module",
6
6
  "main": "dist/main.js",