Skip to content

fix: MCP repository field + idempotent publish #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ragnorc merged 1 commit into from
May 14, 2026
Merged

fix: MCP repository field + idempotent publish #5

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 24 additions & 2 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -89,10 +89,32 @@ jobs:

# SDK first — MCP's workspace:* dependency resolves to the just-published
# version once pnpm rewrites the manifest at publish time.
#
# Each step skips if `pkg@ver` is already on npm. Lets us re-run a tag
# after a partial-failure (e.g. SDK published, MCP rejected on a manifest
# issue) without npm rejecting the SDK with EPUBLISHCONFLICT.
- name: Publish @modernrelay/omnigraph
working-directory: packages/sdk
run: pnpm publish --no-git-checks --access public --provenance --tag ${{ steps.tag.outputs.dist }}
run: |
set -euo pipefail
pkg=$(node -p "require('./package.json').name")
ver=$(node -p "require('./package.json').version")
existing=$(npm view "${pkg}@${ver}" version 2>/dev/null || true)
if [ -n "$existing" ]; then
echo "${pkg}@${ver} already on npm — skipping"
else
pnpm publish --no-git-checks --access public --provenance --tag ${{ steps.tag.outputs.dist }}
fi

- name: Publish @modernrelay/omnigraph-mcp
working-directory: packages/mcp
run: pnpm publish --no-git-checks --access public --provenance --tag ${{ steps.tag.outputs.dist }}
run: |
set -euo pipefail
pkg=$(node -p "require('./package.json').name")
ver=$(node -p "require('./package.json').version")
existing=$(npm view "${pkg}@${ver}" version 2>/dev/null || true)
if [ -n "$existing" ]; then
echo "${pkg}@${ver} already on npm — skipping"
else
pnpm publish --no-git-checks --access public --provenance --tag ${{ steps.tag.outputs.dist }}
fi
7 changes: 7 additions & 0 deletions packages/mcp/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,13 @@
"version": "0.4.0",
"description": "MCP server exposing an Omnigraph database to LLM clients (Tools + Resources, stdio transport).",
"license": "MIT",
"repository": {
"type": "git",
"url": "git+https://github.com/ModernRelay/omnigraph-ts.git",
"directory": "packages/mcp"
},
"homepage": "https://github.com/ModernRelay/omnigraph-ts",
"bugs": "https://github.com/ModernRelay/omnigraph/issues",

@devin-ai-integration devin-ai-integration Bot May 14, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Bugs URL points to wrong repository (omnigraph instead of omnigraph-ts)

The newly added bugs field at packages/mcp/package.json:12 points to https://github.com/ModernRelay/omnigraph/issues, but the repository URL (line 8) and homepage (line 11) both correctly reference omnigraph-ts. This will direct users reporting issues to the wrong GitHub repository (or a 404). The same typo exists pre-existing in packages/sdk/package.json:12, and it was copy-pasted into this PR.

Suggested change
"bugs": "https://github.com/ModernRelay/omnigraph/issues",
"bugs": "https://github.com/ModernRelay/omnigraph-ts/issues",
Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

@cursor cursor Bot May 14, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bugs URL points to wrong repository name

Low Severity

The bugs URL references omnigraph while repository.url and homepage both reference omnigraph-ts. This means the bugs link will point to https://github.com/ModernRelay/omnigraph/issues instead of https://github.com/ModernRelay/omnigraph-ts/issues, likely sending users to a nonexistent or unrelated repo's issue tracker. The same inconsistency exists in the SDK's package.json and appears to have been copied for parity.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 5b44e1f. Configure here.

"type": "module",
"main": "./dist/index.js",
"module": "./dist/index.js",
Expand Down
Loading