lorekeep 0.8.0__tar.gz → 0.8.2__tar.gz

lorekeep-0.8.2/.github/workflows/auto-merge-release-please.yml

@@ -0,0 +1,27 @@
+name: auto-merge-release-please
+
+# When release-please creates or updates a Release PR on the
+# release-please--branches--main branch, enable auto-merge so it
+# merges automatically once branch-protection checks pass.
+#
+# NOTE: uv.lock sync happens post-release in release-please.yml
+# (sync-uv-lock job), NOT here. GITHUB_TOKEN PRs don't trigger
+# pull_request workflows, so pre-merge uv lock never runs.
+on:
+  pull_request:
+    types: [opened, synchronize]
+
+permissions:
+  contents: write
+  pull-requests: write
+
+jobs:
+  auto-merge:
+    if: startsWith(github.head_ref, 'release-please--')
+    runs-on: ubuntu-latest
+    steps:
+      - name: Enable auto-merge for Release PR
+        run: |
+          gh pr merge --auto --squash "${{ github.event.pull_request.html_url }}"
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}

{lorekeep-0.8.0 → lorekeep-0.8.2}/.github/workflows/release-please.yml

@@ -33,7 +33,7 @@ jobs:
       tag_name: ${{ steps.rp.outputs.tag_name }}
     steps:
       - id: rp
-        uses: googleapis/release-please-action@v4
+        uses: googleapis/release-please-action@v5
         with:
           token: ${{ secrets.GITHUB_TOKEN }}
 
@@ -57,3 +57,42 @@ jobs:
       - run: uv build
 
       - uses: pypa/gh-action-pypi-publish@release/v1
+
+  sync-uv-lock:
+    needs: release-please
+    if: needs.release-please.outputs.release_created == 'true'
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+      pull-requests: write
+    steps:
+      - uses: actions/checkout@v5
+        with:
+          ref: main
+
+      - uses: astral-sh/setup-uv@v7
+
+      - run: uv lock
+
+      - name: Sync uv.lock via PR
+        run: |
+          if git diff --quiet uv.lock; then
+            echo "uv.lock already in sync"
+            exit 0
+          fi
+          git config user.name "github-actions[bot]"
+          git config user.email "github-actions[bot]@users.noreply.github.com"
+          git checkout -b chore/sync-uv-lock-${{ needs.release-please.outputs.tag_name }}
+          git add uv.lock
+          git commit -m "chore: sync uv.lock to ${{ needs.release-please.outputs.tag_name }}"
+          git push origin chore/sync-uv-lock-${{ needs.release-please.outputs.tag_name }}
+          gh pr create \
+            --title "chore: sync uv.lock to ${{ needs.release-please.outputs.tag_name }}" \
+            --body "Auto-synced after release." \
+            --base main \
+            --head chore/sync-uv-lock-${{ needs.release-please.outputs.tag_name }}
+          sleep 3
+          gh pr merge --squash --auto --delete-branch \
+            chore/sync-uv-lock-${{ needs.release-please.outputs.tag_name }}
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}

lorekeep-0.8.2/.release-please-manifest.json

@@ -0,0 +1,3 @@
+{
+  ".": "0.8.2"
+}

{lorekeep-0.8.0 → lorekeep-0.8.2}/CHANGELOG.md

@@ -1,5 +1,19 @@
 # Changelog
 
+## [0.8.2](https://github.com/manhhailua/lorekeep/compare/v0.8.1...v0.8.2) (2026-06-30)
+
+
+### Bug Fixes
+
+* sync uv.lock via PR — branch protection blocks direct push to main ([#80](https://github.com/manhhailua/lorekeep/issues/80)) ([4b2b94f](https://github.com/manhhailua/lorekeep/commit/4b2b94fc511fd1fd2d67e01e6559224491e6931f))
+
+## [0.8.1](https://github.com/manhhailua/lorekeep/compare/v0.8.0...v0.8.1) (2026-06-30)
+
+
+### Documentation
+
+* tighten Why section ([#78](https://github.com/manhhailua/lorekeep/issues/78)) ([4da2edd](https://github.com/manhhailua/lorekeep/commit/4da2edd8f0451535ac47d8318b657cc4ccca958d))
+
 ## [0.8.0](https://github.com/manhhailua/lorekeep/compare/v0.7.1...v0.8.0) (2026-06-30)
 
 

{lorekeep-0.8.0 → lorekeep-0.8.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: lorekeep
-Version: 0.8.0
+Version: 0.8.2
 Summary: Temporal knowledge graph for AI agents via MCP
 Project-URL: Homepage, https://github.com/manhhailua/lorekeep
 Project-URL: Repository, https://github.com/manhhailua/lorekeep
@@ -28,31 +28,24 @@ Description-Content-Type: text/markdown
 
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
 
-Lorekeep compiles a team's raw documentation into a versioned, time-aware
-knowledge graph (`facts.jsonl`) and exposes it to coding agents (Claude Code,
-Cursor, Codex, opencode) through the Model Context Protocol — with per-namespace
-permission and zero servers to run.
-
-It applies Andrej Karpathy's "LLM Knowledge Base" idea: raw docs are the
-**source code**, the compiled graph is the **executable**. Knowledge is
-processed once at compile time, not re-RAG'd per query — and agent
-conversations continuously enrich the graph through append-only journals.
+Lorekeep compiles a team's raw docs into a temporal knowledge graph (`facts.jsonl`),
+serves it to coding agents (Claude Code, Cursor, Codex, opencode) over MCP, and
+lets agents propose new facts at zero LLM cost. Knowledge is processed once at
+compile time, not re-RAG'd per query.
 
 ---
 
 ## Why
 
-Existing tools each miss part of what a team needs:
-
 | | file-based | temporal KG | compile step | team permission | MCP |
 |---|---|---|---|---|---|
 | Obsidian + MCP | ✅ | ❌ | ❌ | ❌ | ✅ |
 | mcp-knowledge-graph | ✅ | ❌ | ❌ | ❌ (local) | ✅ |
 | mem0 / cognee | ❌ (DB) | partial | ❌ | partial (DB) | ✅ |
 
-Lorekeep targets the gap: **strictly file-based + temporal graph + compile-once +
-namespace-scoped permission + MCP** — for team-level (not just single-user)
-knowledge.
+No tool combines all five. Lorekeep does: **file-based + temporal graph +
+compile-once + namespace permission + MCP** — for team-level knowledge, not
+just single-user.
 
 ## Features
 

{lorekeep-0.8.0 → lorekeep-0.8.2}/README.md

@@ -6,31 +6,24 @@
 
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
 
-Lorekeep compiles a team's raw documentation into a versioned, time-aware
-knowledge graph (`facts.jsonl`) and exposes it to coding agents (Claude Code,
-Cursor, Codex, opencode) through the Model Context Protocol — with per-namespace
-permission and zero servers to run.
-
-It applies Andrej Karpathy's "LLM Knowledge Base" idea: raw docs are the
-**source code**, the compiled graph is the **executable**. Knowledge is
-processed once at compile time, not re-RAG'd per query — and agent
-conversations continuously enrich the graph through append-only journals.
+Lorekeep compiles a team's raw docs into a temporal knowledge graph (`facts.jsonl`),
+serves it to coding agents (Claude Code, Cursor, Codex, opencode) over MCP, and
+lets agents propose new facts at zero LLM cost. Knowledge is processed once at
+compile time, not re-RAG'd per query.
 
 ---
 
 ## Why
 
-Existing tools each miss part of what a team needs:
-
 | | file-based | temporal KG | compile step | team permission | MCP |
 |---|---|---|---|---|---|
 | Obsidian + MCP | ✅ | ❌ | ❌ | ❌ | ✅ |
 | mcp-knowledge-graph | ✅ | ❌ | ❌ | ❌ (local) | ✅ |
 | mem0 / cognee | ❌ (DB) | partial | ❌ | partial (DB) | ✅ |
 
-Lorekeep targets the gap: **strictly file-based + temporal graph + compile-once +
-namespace-scoped permission + MCP** — for team-level (not just single-user)
-knowledge.
+No tool combines all five. Lorekeep does: **file-based + temporal graph +
+compile-once + namespace permission + MCP** — for team-level knowledge, not
+just single-user.
 
 ## Features
 

{lorekeep-0.8.0 → lorekeep-0.8.2}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "lorekeep"
-version = "0.8.0"
+version = "0.8.2"
 description = "Temporal knowledge graph for AI agents via MCP"
 readme = "README.md"
 license = {text = "MIT"}

{lorekeep-0.8.0 → lorekeep-0.8.2}/src/lorekeep/__init__.py

@@ -1,3 +1,3 @@
 """Lorekeep — temporal knowledge graph for AI agents via MCP."""
 
-__version__ = "0.8.0"
+__version__ = "0.8.2"

{lorekeep-0.8.0 → lorekeep-0.8.2}/uv.lock

@@ -1024,7 +1024,7 @@ wheels = [
 
 [[package]]
 name = "lorekeep"
-version = "0.5.0"
+version = "0.8.0"
 source = { editable = "." }
 dependencies = [
     { name = "litellm" },

lorekeep-0.8.0/.github/workflows/auto-merge-release-please.yml

@@ -1,47 +0,0 @@
-name: auto-merge-release-please
-
-# When release-please creates or updates a Release PR, this workflow:
-# 1. Runs `uv lock` to sync the lockfile with the bumped version in pyproject.toml
-# 2. Commits the updated uv.lock back to the PR branch (if changed)
-# 3. Enables auto-merge so the PR merges once CI passes
-#
-# This ensures uv.lock is always correct in the release commit — no stale lockfile.
-on:
-  pull_request:
-    types: [opened, synchronize]
-
-permissions:
-  contents: write
-  pull-requests: write
-
-jobs:
-  prepare-and-auto-merge:
-    if: startsWith(github.head_ref, 'release-please--')
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v5
-        with:
-          ref: ${{ github.head_ref }}
-          token: ${{ secrets.GITHUB_TOKEN }}
-
-      - uses: astral-sh/setup-uv@v7
-
-      - name: Sync uv.lock
-        run: uv lock
-        continue-on-error: true
-
-      - name: Commit uv.lock if changed
-        continue-on-error: true
-        run: |
-          git config user.name "github-actions[bot]"
-          git config user.email "github-actions[bot]@users.noreply.github.com"
-          git add uv.lock
-          git diff --cached --quiet || git commit -m "chore: sync uv.lock"
-          git push || true
-
-      - name: Enable auto-merge for Release PR
-        run: |
-          sleep 3
-          gh pr merge --auto --squash "${{ github.event.pull_request.html_url }}"
-        env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}

lorekeep-0.8.0/.release-please-manifest.json

@@ -1,3 +0,0 @@
-{
-  ".": "0.8.0"
-}