Skip to content

Conversation

@1egoman
Copy link
Contributor

@1egoman 1egoman commented Jan 16, 2026

I merged a pull request to make a new @livekit/protocol package release here: #1336

However, that release failed due to this reason:

error an error occurred while publishing @livekit/protocol: E422 422 Unprocessable Entity - PUT https://registry.npmjs.org/@livekit%2fprotocol - Error verifying sigstore provenance bundle: Failed to validate repository information: package.json: "repository.url" is "", expected to match "https://github.com/livekit/protocol" from provenance

So I tried to fix it here: #1369

But after merging that, the build still failed... (not really a good way to test trusted publishing locally, so unfortunately it's got to be sort of just guessing and checking here). Digging into this repo's structure a bit more, I think I added that snippet to the wrong package.json 🤦 . So, this pull request puts this fix in the right place.

@changeset-bot
Copy link

changeset-bot bot commented Jan 16, 2026

⚠️ No Changeset found

Latest commit: 276222b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

💥 An error occurred when fetching the changed packages and changesets in this PR
Some errors occurred when validating the changesets config:
The package or glob expression "github.com/livekit/protocol" specified in the `fixed` option does not match any package in the project. You may have misspelled the package name or provided an invalid glob expression. Note that glob expressions must be defined according to https://www.npmjs.com/package/micromatch.

@1egoman 1egoman merged commit 765a80e into main Jan 16, 2026
8 checks passed
@1egoman 1egoman deleted the add-repository-url-fix-to-one-more-place branch January 16, 2026 21:10
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.

3 participants