chore: normalize package repository urls and the mcp bin path - #911
Merged
Merged
Conversation
npm 11 rewrites these at publish time and warns on every run: repository.url without the git+ prefix and a bin path with a leading ./ (its warning even says the bin was removed, though it keeps the normalized path). Ship the manifests in the form npm publishes so the release log stays clean; @pascal-app/editor gains the same repository field as its siblings. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
I hit an error while handling your request (Model unavailable on AI Gateway free tier: Free tier users do not have access to this model. Upgrade to paid credits at https://vercel.com/d?to=%2F%5Bteam%5D%2F%7E%2Fai%3Fmodal%3Dtop-up for unrestricted…). Please try again, rephrase, or reach out if it keeps failing. Error id: 9a1d7ec9-51d6-4194-a0ab-3645f247f1cd |
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
1 participant
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.
What does this PR do?
npm 11 rewrites two manifest fields at publish time and warns on every release run:
repository.urlwithout thegit+prefix, and the mcpbinpath with a leading./(npm's warning even claims the bin "was invalid and removed", though it keeps the normalized path). Ship the manifests in the form npm publishes so the release log stays clean.@pascal-app/editorgains the samerepositoryfield as its siblings.Seen in the 1.0.3 dry run: https://github.com/pascalorg/editor/actions/runs/35776677972
How to test
jq .repository.url packages/*/package.json→ allgit+https://github.com/pascalorg/editor.git;jq .bin packages/mcp/package.json→dist/bin/pascal-mcp.js.repository.urlorbin[...]warnings.Screenshots / screen recording
N/A — manifest metadata only.
Checklist
bun devbun checkto verify)mainbranchNote
Low Risk
Metadata-only manifest tweaks with no runtime, API, or publish behavior changes beyond quieter npm 11 release logs.
Overview
Aligns published package manifests with npm 11’s normalized form so release dry runs stop warning about rewritten metadata.
Across core, ifc-converter, mcp, nodes, and viewer,
repository.urlnow uses thegit+https://…prefix instead of a bare HTTPS URL.@pascal-app/editorgets the same monoreporepositoryblock (withdirectory: packages/editor) that the other packages already had.In
@pascal-app/mcp, thepascal-mcpbin entry drops the leading./(dist/bin/pascal-mcp.js), matching what npm emits at publish time.Reviewed by Cursor Bugbot for commit aa38f31. Bugbot is set up for automated code reviews on this repo. Configure here.