chore(release): v0.9.16 — DevEx polish + website refresh#417
Merged
Conversation
Patch bump per the established rule: additive surface only, no breaks to MemoryProvider trait, exported types, or default behaviour. New top-level subcommands (`--reset` already shipped 0.9.15, no new commands here) are opt-in. PRs included since v0.9.15: #408 — onboarding wires selected agents inline + memory-share callout #409 — clarify MCP is opt-in (REST primary) #410 — 5-port ready panel, iii console install, global-install prompt #411 — splash banner rerender + README install hoist + npx caveat #415 — agent-memory.dev refresh (FeaturedIn bar + Agents/Compare/ CommandCenter/Hero updates) Files bumped (9): package.json, packages/mcp/package.json, plugin/.claude-plugin/plugin.json, plugin/.codex-plugin/plugin.json, src/version.ts, src/types.ts, src/functions/export-import.ts, test/export-import.test.ts, CHANGELOG.md
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
📝 WalkthroughWalkthroughThis PR is a straightforward version release for v0.9.16. All version identifiers across the monorepo are bumped from 0.9.15 to 0.9.16, including the main version constant, package manifests, and plugin configurations. The export/import compatibility system is updated to accept exports in the 0.9.16 format, and the changelog documents the release features and fixes. ChangesRelease v0.9.16
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
ESLint skipped: no ESLint configuration detected in root package.json. To enable, add 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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (2)
src/functions/export-import.ts (1)
179-179: ⚡ Quick winUse a single source of truth for supported export versions.
The version list is manually duplicated across runtime checks and type definitions; this is easy to drift on the next release bump. Consider exporting one
SUPPORTED_EXPORT_VERSIONSconstant and deriving both runtime validation andExportData.versionfrom it.♻️ Suggested direction
+// src/export-versions.ts +export const SUPPORTED_EXPORT_VERSIONS = [ + "0.3.0", /* ... */, "0.9.16", +] as const; +export type ExportVersion = (typeof SUPPORTED_EXPORT_VERSIONS)[number];-const supportedVersions = new Set(["0.3.0", /* ... */, "0.9.16"]); +import { SUPPORTED_EXPORT_VERSIONS } from "../export-versions.js"; +const supportedVersions = new Set(SUPPORTED_EXPORT_VERSIONS);- version: "0.3.0" | ... | "0.9.16"; + version: ExportVersion;🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@src/functions/export-import.ts` at line 179, The supported export version strings are duplicated; replace the inline Set("...") assigned to supportedVersions with a single exported constant array or Set named SUPPORTED_EXPORT_VERSIONS and import/use it wherever versions are needed (including the runtime check in export-import.ts and the ExportData.version type/default), then derive the ExportData.version (or its type) from that single exported constant so bumping versions requires changing only SUPPORTED_EXPORT_VERSIONS; update references to supportedVersions to use SUPPORTED_EXPORT_VERSIONS and ensure the runtime validation and any type definitions import/derive from that constant.test/export-import.test.ts (1)
122-122: ⚡ Quick winAvoid hardcoded release version in test expectation.
Use the shared
VERSIONconstant here so patch bumps don’t require touching this test each release.🧪 Suggested update
+import { VERSION } from "../src/version.js"; ... - expect(result.version).toBe("0.9.16"); + expect(result.version).toBe(VERSION);🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@test/export-import.test.ts` at line 122, The test currently asserts a hardcoded version string via expect(result.version).toBe("0.9.16"); — replace the literal with the shared VERSION constant so the test stays up-to-date; locate the assertion in export-import.test.ts and change it to compare result.version against the exported VERSION (importing VERSION from its module if not already imported) rather than a hardcoded string.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@CHANGELOG.md`:
- Line 21: Inline code spans in the changelog contain leading/trailing spaces
inside the backticks (triggering MD038); locate the inline spans related to
runOnboarding and the agent command (e.g., `agentmemory connect <agent>` shown
in the onboarding description and any other inline samples) and remove the extra
spaces inside the backticks so the code spans are exact (e.g., change `` `
agentmemory connect <agent> ` `` to `` `agentmemory connect <agent>` ``)
ensuring all similar inline backtick instances are fixed.
---
Nitpick comments:
In `@src/functions/export-import.ts`:
- Line 179: The supported export version strings are duplicated; replace the
inline Set("...") assigned to supportedVersions with a single exported constant
array or Set named SUPPORTED_EXPORT_VERSIONS and import/use it wherever versions
are needed (including the runtime check in export-import.ts and the
ExportData.version type/default), then derive the ExportData.version (or its
type) from that single exported constant so bumping versions requires changing
only SUPPORTED_EXPORT_VERSIONS; update references to supportedVersions to use
SUPPORTED_EXPORT_VERSIONS and ensure the runtime validation and any type
definitions import/derive from that constant.
In `@test/export-import.test.ts`:
- Line 122: The test currently asserts a hardcoded version string via
expect(result.version).toBe("0.9.16"); — replace the literal with the shared
VERSION constant so the test stays up-to-date; locate the assertion in
export-import.test.ts and change it to compare result.version against the
exported VERSION (importing VERSION from its module if not already imported)
rather than a hardcoded string.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 7a4833f5-5a4b-4552-a99a-f4c1797a5aa4
📒 Files selected for processing (9)
CHANGELOG.mdpackage.jsonpackages/mcp/package.jsonplugin/.claude-plugin/plugin.jsonplugin/.codex-plugin/plugin.jsonsrc/functions/export-import.tssrc/types.tssrc/version.tstest/export-import.test.ts
|
|
||
| - **Interactive global-install prompt** (PR #410). Replaces the passive `p.log.info` npx hint with a `p.confirm` on first npx run that runs `npm install -g @agentmemory/agentmemory@<VERSION>` inline. Suppressible via `preferences.skipGlobalInstall` so we never ask twice. Closes the v0.9.15-era footgun where users typed `agentmemory stop` in a new shell and hit `command not found`. | ||
|
|
||
| - **Onboarding wires selected agents inline** ([PR #408](https://github.com/rohitg00/agentmemory/pull/408)). After the multi-select agents step in `runOnboarding`, asks `Run \`agentmemory connect <agent>\` for each selected agent now? [Y/n]` and dispatches each through the existing `runAdapter` path used by the explicit `agentmemory connect` command. Successes + failures get bucketed in a summary block (`Wired: claude-code, codex, cursor · Skipped/failed: hermes (manual install required)`). Cancellation prints the explicit per-agent commands for the user to run later. |
There was a problem hiding this comment.
Fix inline code span spacing flagged by markdownlint (MD038).
Line 21 and Line 29 have inline code spans with inner spacing that trigger MD038 (no-space-in-code). Please remove leading/trailing spaces inside the backticks to keep docs lint-clean.
Also applies to: 29-29
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)
[warning] 21-21: Spaces inside code span elements
(MD038, no-space-in-code)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@CHANGELOG.md` at line 21, Inline code spans in the changelog contain
leading/trailing spaces inside the backticks (triggering MD038); locate the
inline spans related to runOnboarding and the agent command (e.g., `agentmemory
connect <agent>` shown in the onboarding description and any other inline
samples) and remove the extra spaces inside the backticks so the code spans are
exact (e.g., change `` ` agentmemory connect <agent> ` `` to `` `agentmemory
connect <agent>` ``) ensuring all similar inline backtick instances are fixed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Patch bump per established rule (additive surface only). Wraps 5 PRs merged post-v0.9.15:
Files bumped (9)
package.json,packages/mcp/package.json,plugin/.claude-plugin/plugin.json,plugin/.codex-plugin/plugin.json,src/version.ts,src/types.ts,src/functions/export-import.ts,test/export-import.test.ts,CHANGELOG.md.Test plan
npm run buildcleannpm test— 944/954 passing (10 pre-existingmcp-standalonefailures unrelated)gh release create v0.9.16triggers publish.yml for both npm packagesSummary by CodeRabbit