Skip to content

Comments

fix: add repository field to package.json for npm provenance verification#286

Draft
Copilot wants to merge 1 commit intomainfrom
copilot/fix-repository-url-error
Draft

fix: add repository field to package.json for npm provenance verification#286
Copilot wants to merge 1 commit intomainfrom
copilot/fix-repository-url-error

Conversation

Copy link
Contributor

Copilot AI commented Feb 5, 2026

npm publish with --provenance was failing with E422 because package.json was missing repository.url. The provenance verification requires this field to match the GitHub repository URL from build metadata.

Root Cause

The tag mcp-server-azure-devops-v0.1.44 was created before the repository field was added. When manual-publish checks out that tag, it gets the old package.json without the required field.

Fix

Added the repository field to package.json:

"repository": {
  "type": "git",
  "url": "https://github.com/Tiberriver256/mcp-server-azure-devops"
}

Notes

  • Fix is now in main; all future releases will publish successfully
  • To publish v0.1.44 specifically, the tag must be deleted and recreated pointing to a commit with this fix

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

Copilot AI changed the title [WIP] Fix npm publish error related to repository URL fix: add repository field to package.json for npm provenance verification Feb 5, 2026
Copilot AI requested a review from Tiberriver256 February 5, 2026 17:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants