ci(publish): add @agentmemory/fs-watcher to the release workflow

[rohitg00]

Backfills the new filesystem connector into the npm publish pipeline.

What

• Adds a `Publish @agentmemory/fs-watcher connector` step to `.github/workflows/publish.yml`.
• Adds `workflow_dispatch` so any of the three packages can be published manually without cutting a release.

Why

The v0.9.0 release shipped `@agentmemory/agentmemory` and `@agentmemory/mcp` to npm via the existing workflow, but `@agentmemory/fs-watcher` (new in this release) wasn't in the workflow yet so it didn't go out. Fixing it so future releases pick it up automatically, plus giving us a manual trigger to back-fill v0.9.0 without re-releasing.

After merge

Run the "Publish to npm" workflow via the Actions UI with `workflow_dispatch` to publish fs-watcher@0.1.0 for v0.9.0.

Summary by CodeRabbit

• Chores
  • Enhanced release automation with manual workflow trigger and selective package publishing options.
  • Improved package propagation verification to the npm registry with automated polling (up to 24 attempts over 2 minutes) to ensure successful deployment.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
agentmemory	Ready	Preview, Comment	Apr 18, 2026 7:04pm

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

📝 Walkthrough

Walkthrough

The workflow configuration adds a manual trigger with an optional packages input parameter and introduces automation steps to publish the @agentmemory/fs-watcher package to npm, including verification that the version propagates successfully to the registry.

Changes

Cohort / File(s)	Summary
Workflow Dispatch and Publishing .github/workflows/publish.yml	Added manual workflow_dispatch trigger with configurable packages input (comma-separated list); introduced two new steps for @agentmemory/fs-watcher: conditional npm publish based on version availability and registry propagation polling with 24 retry attempts (5s intervals).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• feat: filesystem connector — emits observations on file changes #163: Adds corresponding CI workflow steps to publish and verify the exact version from integrations/filesystem-watcher/package.json to npm registry, directly implementing the new @agentmemory/fs-watcher publishing automation.

Poem

🐰 A rabbit hops through CI flows so neat,
Packages bundled, dispatch complete,
npm polls with patience and care,
Twenty-four checks float through the air,
Publication assured, propagation fair! ✨📦

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'ci(publish): add @agentmemory/fs-watcher to the release workflow' directly summarizes the main change: adding a new package to the CI/CD publish workflow.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch ci/publish-fs-watcher

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}