Use this checklist before publishing a new memory-lancedb-pro package. It is
intended for the release tracked in #812 and future beta/stable cuts.
- Current package version:
1.1.0-beta.11 - Recommended first publish: beta dist-tag
- Stable channel decision: maintainer-owned after beta smoke testing
The current release driver is that npm users are still behind repository
master: merged fixes are not available from the published latest package,
and the beta dist-tag still points at an older beta package.
Run these from a clean checkout:
npm ci
npm run test:packaging-and-workflow
npm run build
npm pack --dry-runConfirm:
package.jsonandopenclaw.plugin.jsonversions matchpackage.json mainpoints atdist/index.jspackage.json openclaw.extensionspoints at./dist/index.jspackage.json filesincludesdist/**/*CHANGELOG.mdandCHANGELOG-v1.1.0.mdstart with the package versionnpm pack --dry-runincludes compileddistoutput and excludes test files
npm publish --tag beta --dry-runReview the file list and package metadata before publishing.
npm publish --tag betaAfter publish, verify the public registry state:
npm view memory-lancedb-pro dist-tags version versions --json
npm view memory-lancedb-pro@beta version main openclaw files --jsonThe beta dist-tag should point at the newly published version, and the package
runtime entries should point at compiled JavaScript under dist/.
On a machine with a current OpenClaw install:
openclaw plugins registry --refresh
openclaw plugins install memory-lancedb-pro@beta
openclaw plugins doctorConfirm OpenClaw installs the package without falling back to TypeScript source entrypoints.