# Publishing Checklist

Use this checklist for follow-up releases of the already published `pi-open-code-review` npm package.

## Local Verification

```bash
npm test
npm run test:pi
npm pack --dry-run
```

`npm run test:pi` verifies Pi can load the package without installing it. It does not require OCR credentials.

## Release

1. Bump the version in `package.json`.
2. Verify the package:

```bash
npm test
npm run test:pi
npm pack --dry-run
```

3. Publish:

```bash
npm login
npm publish --access public
```

Users install the published package with:

```bash
pi install npm:pi-open-code-review
```

## Pi Package Gallery

Pi's package gallery at <https://pi.dev/packages> discovers npm packages with the `pi-package` keyword. This package includes:

```json
"keywords": ["pi-package"]
```

It also includes gallery preview metadata and runtime resources:

```json
"pi": {
  "extensions": ["./extensions/open-code-review.js"],
  "skills": ["./skills"],
  "image": "https://raw.githubusercontent.com/alibaba/open-code-review/main/imgs/highlights-en.png"
}
```

After npm publish, wait for npm and Pi package indexing. If the package appears but downloads show `0` or `not available`, compare against npm's download API; Pi gallery counts can lag or be unavailable independently of npm downloads.

If the package does not appear, verify:

- the published npm package includes `package.json`,
- `keywords` contains `pi-package`,
- the package is public,
- the package name on npm matches the install command,
- the `pi` manifest paths point to files included in the tarball.