chore(release): 0.13.0 — ThinkFleet Memory Bridge - #48
Merged
Conversation
Bumps version 0.12.0 → 0.13.0 and adds the CHANGELOG entry covering: - Memory plugin in the default plugin set (PR #44) - `detectMemoryBackend` env-aware backend selection + cred validation + secret-safe errors (PR #44) - `agentmark-mcp install --env=KEY=VALUE` with strict validation (PR #47, originally #45) - `agentmark-mcp install --skill=<name>` + canonical `thinkfleet-memory` skill (PR #47, originally #46) - Per-client skill installer with native + marker-block targets, atomic writes, idempotency (PR #47) - New helper exports: `detectMemoryBackend`, `describeMemoryBackend`, `MemoryBackendConfigError` Suite: 586 passed, 10 skipped. Typecheck clean. Ready to publish: after merge, `npm run build && npm publish --access public`. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
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
Cuts
@thinkfleet/agentmark@0.13.0. Bundles everything from #44 + #47 into a single shipping release: env-aware memory backend, the--env+--skillinstall flags, the canonicalthinkfleet-memoryskill, and the new public helper exports.After this merges, publish:
```bash
cd /Users/ryanrader/Dev/_code/agentmark
git checkout main && git pull
npm run build
npm publish --access public
```
Once
0.13.0is on the registry, ThinkFleet Desktop bumps automatically (its dep pin^0.12.0already matches0.13.0), and end users of the next desktop release get the bundled-and-skilled memory bridge baked in.What's in this release
Memory backend
agentmark_memory_*toolsdetectMemoryBackend()picksActivepiecesMemoryBackendwhenTHINKFLEET_BASE_URL/PROJECT_ID/API_KEYare set, falls back toLocalFileMemoryBackendotherwiseMemoryBackendConfigError) so a typo doesn't silently demote a user to local-only memorysk-prefix), truncates to first 4 chars in errors so secrets don't leak to logsdetectMemoryBackend,describeMemoryBackend,MemoryBackendConfigErrorInstall CLI
agentmark-mcp install --env=KEY=VALUEwrites env block into client MCP configs; strict validation (no shell metacharacters, 4KiB cap, no null bytes)agentmark-mcp install --skill=<name>installs an instruction packet alongside the MCP entry; native targets (Claude Code/Desktop) write whole files, rules-file targets (Cursor/Windsurf/Codex) scaffolded viaupsertManagedBlock--envwarnings contain key name but never valuesSkill
thinkfleet-memoryskill ships with the packageTest plan
npx vitest run— 586 passed, 10 skipped (596 total, no failures)0.12 → 0.13for additive features, no breaking changes)After publish
Once on npm:
npm installpulls 0.13.0 (pin is^0.12.0).dmg/.msi/.AppImagebundles 0.13 inside the app — no PATH dependency, nonpx -ydownload🤖 Generated with Claude Code