Skip to content

fix(cli): point colonyq repository.url at opencue/colony for npm provenance#599

Merged
NagyVikt merged 1 commit into
mainfrom
fix/colonyq-provenance-repo-url
Jun 14, 2026
Merged

fix(cli): point colonyq repository.url at opencue/colony for npm provenance#599
NagyVikt merged 1 commit into
mainfrom
fix/colonyq-provenance-repo-url

Conversation

@NagyVikt

Copy link
Copy Markdown
Collaborator

Problem

The Release workflow fails at changeset publish with:

E422 ... Error verifying sigstore provenance bundle: Failed to validate repository information:
package.json: "repository.url" is "git+https://github.com/recodeee/colony.git",
expected to match "https://github.com/opencue/colony" from provenance

npm trusted publishing (OIDC) now authenticates correctly and signs provenance, but the registry rejects the publish because the signed source repo (opencue/colony) doesn't match the package's repository.url, which still points at the pre-rename org recodeee/colony.

Fix

Update apps/cli/package.json homepage, repository.url, and bugs.url from recodeee/colonyopencue/colony (the org was renamed; recodeee/colony redirects here).

Effect

Once merged, the release job on main republishes colonyq@0.8.0 and the provenance check passes.

Notes

  • Scoped to the published package only. The root package.json and historical openspec//docs references still say recodeee but are unpublished/non-functional — separate cleanup if wanted.
  • No test asserts repository.url; the recodeee mentions in skills.ts/skills-wire.test.ts are an unrelated skill-install typo guard.

…enance

The org was renamed recodeee -> opencue, but apps/cli/package.json still
referenced github.com/recodeee/colony. npm trusted-publishing rejects the
release with E422 because the signed provenance source (opencue/colony) must
match repository.url. Updates homepage, repository.url, and bugs.url.
@NagyVikt NagyVikt merged commit 4502981 into main Jun 14, 2026
8 checks passed
@NagyVikt NagyVikt deleted the fix/colonyq-provenance-repo-url branch June 14, 2026 22:45
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.

1 participant