fix(release): point package metadata at office-kit/docx repo#20
Merged
Conversation
The repo was transferred from baseballyama/word-kit to office-kit/docx, but package.json "repository.url" still referenced the old slug. npm provenance is signed with the Actions repo (office-kit/docx), so publish failed E422: provenance repository did not match package.json. Update repository/homepage/bugs in both packages, plus the stale site and CONTRIBUTING links, to the current slug. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013A1Lh6BeJKb2fNsfxQnv9x
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.
Summary
The repository was transferred from
baseballyama/word-kittooffice-kit/docx, but the published package metadata (repository.url,homepage,bugs) still pointed at the old slug. npm provenance is signed with the GitHub Actions repository (office-kit/docx), sochangeset publishfailed withE422 - Error verifying sigstore provenance bundle: "repository.url" ... expected to match "https://github.com/office-kit/docx". This blocks the Release workflow on every push tomain.Motivation
The
Releaseworkflow onmainhas been failing on publish. After OIDC trusted publishing was configured on npm, auth and provenance signing now succeed, but the provenance-vs-package.jsonrepository mismatch causes npm to reject the tarball. This PR aligns the metadata with the current repo slug so0.1.1can publish.Changes
repository.url/homepage/bugs.urlatoffice-kit/docxin both@office-kit/docxand@office-kit/docx-preview.baseballyama/word-kitlinks in the docs site andCONTRIBUTING.md(kept the separatexlsx-kitsibling link untouched).Testing
Releasere-run reproduced the failure:E422 ... expected to match "https://github.com/office-kit/docx" from provenance.node -e "JSON.parse(...)"confirms bothpackage.jsonfiles remain valid.main.Breaking changes
None. Metadata-only; no code or public API change.
Checklist
🤖 Generated with Claude Code
https://claude.ai/code/session_013A1Lh6BeJKb2fNsfxQnv9x