Repository navigation
chore: release 0.5.2 - #8
Merged
Merged
Conversation
A robustness release: every change fixes a case where lore silently did nothing, or the wrong thing, while looking healthy. - Hooks follow the agent's cwd (#5): the store is found from any subdirectory, and edit-time dedupe plus recall telemetry work in git worktrees. - The capture skill finds its scripts on Claude Code again (#6): the write-time overlap check and secret scan had been falling through to the Codex install path. - Linter blind spots (#7): trailing `# comments` in frontmatter are dropped as YAML does, `--strict` fails on a status or date the hooks would misread, and an in-repo personal store that git would publish gets a warning. `_common.py` and `verify_refs.py` changed, so projects that ran /lore:init have stale `.lore/` copies; the version bump is what makes the linter say so and point them at re-running /lore:init. Their CI `--strict` picks up the new value checks only after that refresh. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DMXx6BJswH6xiwdqrwQnEf
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
2 participants
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.
Summary
This bumps the three version fields (marketplace, marketplace plugin entry,
plugin.json) from 0.5.1 to 0.5.2, the same change as the 0.5.1 release.This is a robustness release. Each fix covers a case where lore did nothing, or the wrong thing, while looking healthy:
# commentsin frontmatter are now dropped, as YAML does.--strictfails on a status or date the hooks would misread.Upgrade notes
_common.pyandverify_refs.pychanged, so projects that ran/lore:inithave stale.lore/copies. This version bump is what makes the linter report them and suggest re-running/lore:init.--strictin the pre-push hook and in CI also fails on an invalid status or date.#(title: Fix #12) now ends before the#, as in YAML.Test plan
python -m unittest discover -s tests: 199 passed, 1 skipped.test_manifestschecks that the three versions agree.claude plugin validate .: passed.v0.5.2and publish the GitHub release "Lore 0.5.2".🤖 Generated with Claude Code
https://claude.ai/code/session_01DMXx6BJswH6xiwdqrwQnEf
Generated by Claude Code