kojee-mcp 0.7.5-staging.6 → 0.7.6-staging.6
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 +0 -16
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -574,22 +574,6 @@ npm run dev:stub
|
|
|
574
574
|
# Stub listens on http://localhost:8765
|
|
575
575
|
```
|
|
576
576
|
|
|
577
|
-
## Releases & staging versioning
|
|
578
|
-
|
|
579
|
-
Two channels, and one rule that keeps them clean:
|
|
580
|
-
|
|
581
|
-
- **`latest` (production)** — a **manual** release off `main` (`npm publish` → `latest`, or promote a verified staging build via `npm dist-tag add kojee-mcp@<ver> latest`).
|
|
582
|
-
- **`staging` (pre-release)** — **automatic** on every merge to the `staging` branch, via `.github/workflows/publish-staging.yml`, published under the `staging` dist-tag (never touches `latest`).
|
|
583
|
-
|
|
584
|
-
**How the staging version is computed** (`scripts/next-staging-version.mjs`):
|
|
585
|
-
|
|
586
|
-
1. **base** = `package.json.version` with its **PATCH bumped once** — e.g. `0.7.4` → `0.7.5`.
|
|
587
|
-
2. **counter** = `1 + highest existing <base>-staging.N on npm`. This is **per-base**, so it **RESETS to 1 automatically when the base progresses** (a brand-new base has no prior `-staging.N`).
|
|
588
|
-
|
|
589
|
-
So a run yields e.g. `0.7.5-staging.6`, and once `0.7.5` ships to `latest` and `package.json` moves to `0.7.5`, the next staging build resets to `0.7.6-staging.1`.
|
|
590
|
-
|
|
591
|
-
> ⚠️ **THE RULE: `package.json.version` must hold the LAST STABLE version — never a `-staging`/`-beta` pre-release.** The CI bumps the patch itself; if the file already carries the *next* version (or a `-beta` whose stable part is the next version), the base **double-bumps**. That is exactly how a `0.7.5-beta.1` base once published `0.7.6-staging.6` instead of the intended `0.7.5-staging.6`. Cutting a stable release is the *only* time `package.json.version` advances, and it advances to the version you just shipped to `latest`.
|
|
592
|
-
|
|
593
577
|
## How Approvals Work
|
|
594
578
|
|
|
595
579
|
Some tools are governed by approval policies configured in the Kojee dashboard. When an agent calls a governed tool:
|