bmad-dashboard 1.0.10 → 1.0.11

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 +2 -2
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -159,9 +159,9 @@ On every **push to `main`**, GitHub Actions:
159
159
  1. Runs tests and build in the `dashboard/` directory.
160
160
  2. If tests pass, bumps the **patch** version (e.g. `1.0.9` → `1.0.10`), publishes to npm via **Trusted Publishers (OIDC)**, and commits the version bump back to `main` (with message `chore(release): 1.0.10 [skip ci]` so the release commit does not trigger another publish).
161
161
 
162
- **Setup (one-time):** Use [npm Trusted Publishers](https://docs.npmjs.com/trusted-publishers). Your **npm account must be linked to your GitHub account** (npm profile/Account link GitHub). Then on [npmjs.com](https://www.npmjs.com/) go to **Packages** → **bmad-dashboard** → **Settings** **Trusted publishing**, choose **GitHub Actions**, set **Workflow filename** to `release.yml`, and save. The workflow file is `.github/workflows/release.yml`.
162
+ **Setup (one-time), either:** **Option A — Granular token (recommended):** Create a [Granular access token](https://docs.npmjs.com/about-access-tokens) on npm with **read and write** access for this package and **Bypass 2FA** enabled. Add it as repo secret **`NPM_TOKEN`** under **Settings** → **Secrets and variables** → **Actions**. **Option B Trusted Publishers (OIDC):** Link npm to GitHub and set Trusted publishing for this package (workflow `release.yml`) on npmjs.com; leave `NPM_TOKEN` unset. The workflow file is `.github/workflows/release.yml`.
163
163
 
164
- **If you get 404 on publish:** The package must exist on npm before you can add a Trusted Publisher (you configure it in the package’s Settings). If [npmjs.com/package/bmad-dashboard](https://www.npmjs.com/package/bmad-dashboard) returns 404, do **one manual publish** from your machine: `cd dashboard && npm login && npm publish --access public` (enter OTP when prompted). After that, add the Trusted Publisher for `release.yml` in the package settings; then CI can publish future versions.
164
+ **If OIDC gives 404 on publish:** The package must exist on npm before you can add a Trusted Publisher (you configure it in the package’s Settings). If [npmjs.com/package/bmad-dashboard](https://www.npmjs.com/package/bmad-dashboard) returns 404, do **one manual publish** from your machine: `cd dashboard && npm login && npm publish --access public` (enter OTP when prompted). After that, add the Trusted Publisher for `release.yml` in the package settings; then CI can publish future versions.
165
165
 
166
166
  ---
167
167
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "bmad-dashboard",
3
- "version": "1.0.10",
3
+ "version": "1.0.11",
4
4
  "description": "Local dashboard to view BMAD project state (phase, artifacts, stories, sprint) in real time",
5
5
  "type": "module",
6
6
  "bin": {