Skip to main content
@jiggai/recipes
This is the practical release guide.

​
Before you release

Make sure these are true:
  • package.json version is correct
  • openclaw.plugin.json version matches
  • tests pass
  • the branch/PR you intend to release is actually the one merged to main
Useful checks: 
npm test
npm view @jiggai/recipes version
node -p "require('./package.json').version"
cat openclaw.plugin.json
From main: 
git checkout main
git pull --ff-only
npm version patch
Or use minor / major when appropriate: 
npm version minor
npm version major
Then push commit + tag: 
git push origin main --follow-tags
GitHub Actions will run the normal publish workflow.

​
Manual local publish

If you are intentionally publishing from your local machine: 
npm ci
npm run lint
npm test
npm publish
You will need local npm auth: 
npm whoami

​
Verify after publishing

Check the published version: 
npm view @jiggai/recipes version
Then test a fresh install or upgrade path: 
openclaw plugins install @jiggai/recipes
openclaw gateway restart
openclaw recipes list

​
Important note about local patches

If you maintain a local controller-specific patch (for example, workflow posting behavior), publishing a clean package does not mean that patch is part of the public release unless you intentionally merged it. So after publishing, you may need to:
  • reapply your local patch
  • relink/reinstall the plugin
  • tell your assistant to turn the local posting path back on
If you use a patch file or gist for that workflow, keep it handy as part of your release checklist.

​
About canary publishes

If canary publishing is paused in the repo workflow config, PR activity will not automatically publish canary builds. That is separate from the normal release workflow.

​
Minimum safe release checklist

# sync to main
git checkout main
git pull --ff-only

# run checks
npm test

# bump version
npm version patch

# push
git push origin main --follow-tags

# verify published version
npm view @jiggai/recipes version