npm package stale: v0.12.0 on npm vs v0.14.0 in git (tag dominance + keyword bugs present)

[autojack-bot]

Problem

The automem npm package is currently at v0.12.0 on the npm registry, while the git repo is at v0.14.0 (and PR #118 is ready to release v0.15.0).

This means anyone installing via npm gets a version that includes:

• The searchByTag dual-merge behaviour that causes tag dominance (high-importance tag-matched memories outscoring vector results regardless of topical relevance)
• The keyword scoring bug from issue recall: Keyword scoring dead for vector results + adaptive floor too aggressive #128 (keyword component = 0.0 for all vector-sourced results, meaning 35% of the scoring formula is dead weight)

Both bugs were addressed in commits that landed after v0.12.0, but npm users are blocked from those fixes until a publish happens.

Release Please PR

PR #118 (chore(main): release 0.15.0) is already open and passing all checks — it just needs a merge + npm publish. This would bring npm users to v0.15.0 and unblock the fixes.

Related

• recall: Keyword scoring dead for vector results + adaptive floor too aggressive #128 — keyword scoring + adaptive floor fix (not yet in npm)
• PR chore(main): release 0.15.0 #118 — Release Please PR for v0.15.0, ready to merge
• The searchByTag dual-merge was introduced in v0.12.0 and is the root cause of the tag dominance issue discussed in the community

Suggested fix

1. Merge PR chore(main): release 0.15.0 #118 to cut v0.15.0
2. Run npm publish from the release workflow
3. Consider adding a CI check or reminder to keep npm in sync with git releases

[coderabbitai]

🔗 Related PRs

#25 - chore(release): prepare v0.9.3 [merged]
#77 - chore(main): release 0.11.0 [merged]
#82 - chore(main): release 0.12.0 [merged]
#95 - chore(main): release 0.13.0 [merged]
#106 - chore(main): release 0.14.0 [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!