Skip to content

Release 0.3.0 - #51

Merged
sethigoldy merged 2 commits into
mainfrom
release/0.3.0-from-main
Sep 24, 2026
Merged

sethigoldy merged 2 commits into
mainfrom
release/0.3.0-from-main

Conversation

@sethigoldy

@sethigoldy sethigoldy commented Sep 24, 2026 •

Copy link
Copy Markdown
Member

This release ships the skill and hooks from memvara core v0.15.0, which
were vendored in #50. Until the version number changes, the plugin
update command tells an existing install that it is already current, so
none of this reaches anyone who installed 0.2.4. It is a minor release
because it adds features. The hooks here were last vendored before core
v0.10.0, so this brings six core releases of hook changes.

The daily recall allowance is named. On a paid hosted plan, when the
day's recalls are used up the recall hook now reports that allowance and
when it resets, instead of "recall failed". The hooks also send each
hosted recall once, and never resend a refused one.

Project scoping and counts. The hooks send the git project with every
hosted call, in a Memvara-Project header, so memories are kept per
repository. They keep per-session counts in ~/.memvara/.hooks/counts/,
and every recalled memory line starts with a mark so capture does not
store it a second time. The switches project_scope, status_line and
recall_mark in ~/.memvara/settings.json turn each one off.

Agentic capture is in the vendored hooks but does not run on this host,
because it needs a different first extractor from the one this host
uses. Capture still reads each turn with one model call, and
capture.log records that agentic capture was skipped. Setting
"agentic_capture": false in ~/.memvara/settings.json stops that line.

Skill. The vendored skill lists the twenty-two tools the hosted endpoint now serves, including the new memory_profile, memory_end_matching, memory_forget_matching, memory_link and four document tools. It explains how to use metadata filters on search and recall, valid_at on recall and merge_predicate. It also says the OAuth grant lasts until it is
revoked, or ten years.

The version is bumped in plugin.json, the only tracked file that
declares one, and in VERSION in test/test_plugin.py.

The README, the header comment in bin/install.mjs and the Installer
test's docstring said "Until 0.2.5". The hooks and the installer change
they describe shipped in 0.2.4, and opencode never had a 0.2.5 release,
so all three now say "Until 0.2.4".

Tests

Run in this worktree with stdin closed and MEMVARA_LIBRARY pointing at a clone of memvara/memvara whose origin/main is v0.15.0 (026be5cf), the commit the lock files pin:

MEMVARA_LIBRARY=<clone> python3 -m unittest discover -s test -v </dev/null
Ran 46 tests
OK

Version.test_every_version_this_repo_states_is_the_released_one and Version.test_exactly_the_manifests_that_must_declare_a_version_do read every tracked JSON file, so they confirm that no file still states the old version.

After merge

The release is cut by pushing the tag v0.3.0. release.yml runs CI again, checks that the tag matches the manifest version, and publishes the GitHub release with plugin.zip.

Review

The release bump was reviewed and approved.

The skill paragraph above was corrected before merge. It had said the skill covers the new tools, but the skill only lists memory_end_matching, memory_forget_matching and memory_link by name, so it now says which tools are listed and which are explained.

This release ships the skill and hooks from memvara core v0.15.0, which
were vendored in #50. Until the version number changes, the plugin
update command tells an existing install that it is already current, so
none of this reaches anyone who installed 0.2.4. It is a minor release
because it adds features. The hooks here were last vendored before core
v0.10.0, so this brings six core releases of hook changes.

The daily recall allowance is named. On a paid hosted plan, when the
day's recalls are used up the recall hook now reports that allowance and
when it resets, instead of "recall failed". The hooks also send each
hosted recall once, and never resend a refused one.

Project scoping and counts. The hooks send the git project with every
hosted call, in a `Memvara-Project` header, so memories are kept per
repository. They keep per-session counts in `~/.memvara/.hooks/counts/`,
and every recalled memory line starts with a mark so capture does not
store it a second time. The switches `project_scope`, `status_line` and
`recall_mark` in `~/.memvara/settings.json` turn each one off.

Agentic capture is in the vendored hooks but does not run on this host,
because it needs a different first extractor from the one this host
uses. Capture still reads each turn with one model call, and
`capture.log` records that agentic capture was skipped. Setting
`"agentic_capture": false` in `~/.memvara/settings.json` stops that line.

Skill. The vendored skill covers the tools the hosted endpoint now
serves, twenty-two in all: `memory_profile`, ending or retiring memories
by query with a preview, `memory_link`, the document tools, metadata
filters on search and recall, `valid_at` on recall, and
`merge_predicate`. It also says the OAuth grant lasts until it is
revoked, or ten years.

The version is bumped in `plugin.json`, the only tracked file that
declares one, and in `VERSION` in `test/test_plugin.py`.
The README, the installer's header comment and the Installer test's
docstring each said "Until 0.2.5". The hooks and the installer change
they describe shipped in 0.2.4, and there has never been an opencode
0.2.5 release, so all three now say "Until 0.2.4".
@sethigoldy
sethigoldy merged commit 2de740d into main Sep 24, 2026
1 check passed
@sethigoldy
sethigoldy deleted the release/0.3.0-from-main branch September 24, 2026 11:02
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.

1 participant