chore(packages): mark memory-digest-cli + agent-memory-sync private (internal-only)#58
Merged
Merged
Conversation
…internal-only) Resolve the "stranded MEDIUM fix has no release vehicle" finding (task 9723a709) by recording the release posture: both are internal/local CLIs with no npm consumers (E404; this repo publishes only @lannguyensi/memory-router). The MEDIUM audit fix (PR #43) already ships in source, where the only (local) users run it. Mark private:true + document so accidental publish is blocked and the non-release is intentional and recorded. Refs: 9723a709 (memory-digest-cli / agent-memory-sync release-vehicle posture) Co-Authored-By: Claude Opus 4.8 (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.
What
Mark
memory-digest-cliandagent-memory-syncasprivate: trueand document them as internal-only CLIs.Why
Resolves the "stranded MEDIUM fix has no release vehicle" finding (task 9723a709). Evidence: neither package is on npm (E404), both have zero first-party consumers, and this repo deliberately publishes only
@lannguyensi/memory-router(release.ymlmemory-router-v*plus publish-memory-router.yml). The MEDIUM audit fix (PR #43) already ships in source, where the only (local) users run it. Marking private records the intentional non-release and blocks accidental publish.Changes
packages/memory-digest-cli/package.json,packages/agent-memory-sync/package.json:private: trueplus a//note.Review / gates
Review-subagent: APPROVE-WITH-NITS (sole nit, em dashes, fixed inline). Confirmed valid JSON,
name/bin/scriptsunchanged, no CI/publish regression (publish gated tomemory-router-v*; repo is not an npm workspace). build OK; memory-digest-cli 12/12, agent-memory-sync 18/18.Refs: 9723a709