Skip to content

GitHub release v0.9.22 exists, but npm latest is still 0.9.21 #661

Closed

Description

@Serg2000Mr

GitHub release v0.9.22 exists, but the npm package @agentmemory/agentmemory is still published only up to 0.9.21, so users cannot install the fixes through the documented npm path.

What happened

v0.9.22 was published on GitHub and issue #613 was closed as fixed in that release:

However, npm registry still reports 0.9.21 as the latest published package version.

Reproduction

As of 2026-05-26:

npm view @agentmemory/agentmemory version
# 0.9.21

Registry API also shows:

dist-tags.latest = 0.9.21
published versions tail = 0.9.14 ... 0.9.21

At the same time, the GitHub tag contains:

{
  "version": "0.9.22"
}

from:

https://raw.githubusercontent.com/rohitg00/agentmemory/v0.9.22/package.json

User impact

Users following the documented npm install/update path remain on 0.9.21, even though the GitHub release notes say v0.9.22 includes fixes such as:

This makes it look like the issue is fixed, but users cannot actually consume the fix via npm yet.

Expected result

Either:

  • publish @agentmemory/agentmemory@0.9.22 to npm and move the latest dist-tag to 0.9.22; or
  • if npm publishing is intentionally delayed, mention that in the GitHub release notes so users do not try to update repeatedly.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions