Skip to content

Pin claude-code-memory to v0.2.0 - #13

Merged
joshuanapoli merged 2 commits into
mainfrom
memory-v0.2.0
Nov 12, 2026
Merged

joshuanapoli merged 2 commits into
mainfrom
memory-v0.2.0

Conversation

@joshuanapoli

Copy link
Copy Markdown
Member

Why

v0.4.1 pins claude-code-memory at 0cedc537, the head of its s3-store branch. That branch is deleted now that the change is released as v0.2.0, so the commit survives only through the pull request's ref.

What changes

  • triage, respond and fix-ci pin claude-code-memory@bf38ca4 (v0.2.0). It has the same tree as 0cedc537, so behavior is unchanged.
  • The three reusable workflows pin their own actions to d554e31, the commit above. Merge with a merge commit so d554e31 stays on main.

Release as v0.4.2 after merging; CVector-Energy/ui then moves its pins to that release.

Testing

  • npm test: 132 pass.
  • actionlint is clean.

The actions pinned the head of its s3-store branch, which is deleted now that the change is released. v0.2.0 has the same tree.
Merge this with a merge commit: d554e31 has to stay on main for these pins to resolve.
@joshuanapoli
joshuanapoli requested a review from alok27a November 12, 2026 19:32
@joshuanapoli
joshuanapoli merged commit 6fd3b22 into main Nov 12, 2026
3 checks passed
@joshuanapoli
joshuanapoli deleted the memory-v0.2.0 branch November 12, 2026 21:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants