chore: release main - #237
Merged
Merged
Conversation
There was a problem hiding this comment.
3 issues found across 11 files
Confidence score: 4/5
- This PR looks safe to merge from a runtime perspective, but there is moderate documentation risk:
packages/cli/CHANGELOG.mdcurrently labels0.2.1as dependency-only even though it pullssoop-encoder/soop-mcp0.3.0marked as breaking. - The most significant issue is release-note accuracy for users/operators: missing the breaking-change callout in
packages/cli/CHANGELOG.mdcould lead to upgrade surprises despite no direct code defect being reported. packages/mcp/CHANGELOG.mdandpackages/encoder/CHANGELOG.mdboth appear to duplicate prior entries, which can misstate what is actually new in0.3.0and reduce trust in release documentation.- Pay close attention to
packages/cli/CHANGELOG.md,packages/mcp/CHANGELOG.md,packages/encoder/CHANGELOG.md- align0.2.1/0.3.0notes with actual new and breaking changes.
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="packages/encoder/CHANGELOG.md">
<violation number="1" location="packages/encoder/CHANGELOG.md:12">
P3: This `0.3.0` changelog entry duplicates items already released in earlier versions, which makes the release notes inaccurate for this tag.</violation>
</file>
<file name="packages/mcp/CHANGELOG.md">
<violation number="1" location="packages/mcp/CHANGELOG.md:8">
P2: This 0.3.0 changelog entry repeats changes already documented under earlier soop-mcp releases, so it misstates what is actually new in 0.3.0.</violation>
</file>
<file name="packages/cli/CHANGELOG.md">
<violation number="1" location="packages/cli/CHANGELOG.md:10">
P2: Document the breaking CLI change here instead of listing this release as dependency-only; `0.2.1` pulls in `soop-encoder`/`soop-mcp` 0.3.0, which the release notes mark as breaking.</violation>
</file>
Architecture diagram
sequenceDiagram
participant User
participant CLI as @pleaseai/soop-cli
participant Encoder as @pleaseai/soop-encoder
participant AST as @pleaseai/soop-ast (WASM)
participant LLM as LLM Provider (Gemini 1.5/3.1)
participant Store as @pleaseai/soop-store (Vector/BM25)
participant MCP as @pleaseai/soop-mcp
Note over User,Store: Repository Encoding Flow (CLI)
User->>CLI: CHANGED: soop encode <repo-path> -l <load-path>
CLI->>Encoder: initialize(repoPath, loadPath)
Encoder->>AST: NEW: Parse files (C#, C++, Ruby, Kotlin support)
AST-->>Encoder: Symbols & Syntax Trees
Encoder->>Encoder: NEW: Build DependencyGraph (Invocation & Inheritance)
Encoder->>LLM: CHANGED: Batch semantic extraction (Gemini 3.1 Flash Lite)
LLM-->>Encoder: Extraction results
Encoder->>Store: NEW: save() with Float16 embeddings & BM25 scoring
Store->>Store: NEW: Git-managed vector persistence
Encoder-->>CLI: Encoding complete
CLI-->>User: Success
Note over User,MCP: Runtime Agent Flow (MCP)
User->>MCP: Request repository context (via LLM Agent)
MCP->>Store: NEW: Search using BM25 + Vector similarity
Store-->>MCP: Relevant code snippets & metadata
MCP->>Encoder: NEW: Resolve Type-aware calls/dependencies
Encoder-->>MCP: Dependency Graph context
MCP-->>User: Enhanced Context for Agent (JSON-RPC)
alt NEW: Zero-dependency Fallback
Store->>Store: Use local fallback if native deps missing
end
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
pleaseai-release-bot
Bot
force-pushed
the
release-please--branches--main
branch
3 times, most recently
from
March 16, 2026 07:36
f9418a8 to
ef9579c
Compare
amondnet
enabled auto-merge (squash)
March 16, 2026 07:37
pleaseai-release-bot
Bot
force-pushed
the
release-please--branches--main
branch
from
March 16, 2026 07:37
ef9579c to
0e5d3f3
Compare
pleaseai-release-bot
Bot
force-pushed
the
release-please--branches--main
branch
from
March 16, 2026 07:38
0e5d3f3 to
30228c5
Compare
|
Contributor
Author
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
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.



🤖 I have created a release beep boop
soop: 0.1.27-alpha.1
0.1.27-alpha.1 (2026-03-16)
Dependencies
soop-cli: 0.2.1
0.2.1 (2026-03-16)
Bug Fixes
Dependencies
soop-encoder: 0.3.0
0.3.0 (2026-03-16)
⚠ BREAKING CHANGES
Features
Bug Fixes
Code Refactoring
Dependencies
soop-graph: 0.1.10
0.1.10 (2026-03-16)
Bug Fixes
soop-mcp: 0.3.0
0.3.0 (2026-03-16)
⚠ BREAKING CHANGES
Features
Bug Fixes
Code Refactoring
Dependencies
soop-tools: 0.1.12
0.1.12 (2026-03-16)
Dependencies
soop-zerorepo: 0.1.10
0.1.10 (2026-03-16)
Dependencies
This PR was generated with Release Please. See documentation.