Skip to content

fix: add native package publishing metadata - #35

Merged
ian-pascoe merged 1 commit into
mainfrom
fix-native-package-publishing
May 15, 2026
Merged

fix: add native package publishing metadata#35
ian-pascoe merged 1 commit into
mainfrom
fix-native-package-publishing

Conversation

@ian-pascoe

@ian-pascoeian-pascoe commented May 15, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Add npm repository, homepage, bugs, license, and author metadata to @caplets/opencode and @caplets/pi.
  • Add a patch changeset so the native integration packages get republished with metadata required by npm trusted publishing.

Verification

  • pnpm verify
  • pnpm --filter @caplets/opencode pack --dry-run
  • pnpm --filter @caplets/pi pack --dry-run

Summary by CodeRabbit

  • Chores
    • Updated package metadata for @caplets/opencode and @caplets/pi to enable npm trusted publishing support.

Review Change Stack

@coderabbitai

coderabbitaiBot commented May 15, 2026

Copy link
Copy Markdown
Contributor

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: d7a7764a-6b0b-424e-ade6-0acb9e87421d

📥 Commits

Reviewing files that changed from the base of the PR and between c0ce72f and 5b09771.

📒 Files selected for processing (3)
  • .changeset/fix-native-package-publishing.md
  • packages/opencode/package.json
  • packages/pi/package.json

📝 Walkthrough

Walkthrough

This PR adds repository metadata (homepage, bugs, repository details) to the opencode and pi package.json files and declares patch version bumps in the changeset to support npm trusted publishing.

Changes

NPM Publishing Setup

Layer / File(s)Summary
Repository metadata and changeset
.changeset/fix-native-package-publishing.md, packages/opencode/package.json, packages/pi/package.json
Package metadata (homepage, bugs.url, license, author, repository) is added to opencode and pi packages. A changeset entry declares patch version bumps and notes the addition of repository metadata for npm trusted publishing.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

📦 A rabbit hops with joy so bright,
Adding metadata left and right!
Repository paths now clear and true,
NPM trust flows through and through! 🐰✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check nameStatusExplanation
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.
Title check✅ PassedThe title clearly and concisely summarizes the main change: adding metadata required for npm package publishing to native packages.
Docstring Coverage✅ PassedNo functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check✅ PassedCheck skipped because no linked issues were found for this pull request.
Out of Scope Changes check✅ PassedCheck skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix-native-package-publishing

Comment @coderabbitai help to get the list of available commands and usage tips.

@greptile-apps

Copy link
Copy Markdown
Contributor

Greptile Summary

This PR adds standard npm publishing metadata (homepage, bugs, license, author, repository) to @caplets/opencode and @caplets/pi, along with a patch changeset to trigger republishing. Both packages were missing this metadata, which is required by npm trusted publishing workflows.

  • Both package.json files receive identical metadata blocks; the repository.directory field is correctly scoped to each package's subdirectory within the monorepo.
  • The changeset correctly marks both packages as patch, which is appropriate for a metadata-only change.

Confidence Score: 5/5

Safe to merge — purely additive metadata changes with no functional code altered.

All three files contain only metadata additions: standard npm fields that are well-understood and carry no runtime risk. The repository URLs, directory paths, license identifier, and changeset bump type are all correct and consistent between both packages.

No files require special attention.

Important Files Changed

FilenameOverview
.changeset/fix-native-package-publishing.mdNew changeset marking both @caplets/opencode and @caplets/pi for a patch release to trigger republishing with metadata.
packages/opencode/package.jsonAdds homepage, bugs, license, author, and repository fields; repository.directory correctly set to packages/opencode for monorepo resolution.
packages/pi/package.jsonSame metadata additions as packages/opencode; repository.directory correctly set to packages/pi; consistent with sibling package.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[PR Merged] --> B[Changesets picks up patch bump]
B --> C[opencode bumped to 0.1.2]
B --> D[pi bumped to 0.1.2]
C --> E[npm publish with full metadata]
D --> E
E --> F[npm trusted publishing provenance verified]
Loading

Reviews (1): Last reviewed commit: "fix: add native package publishing metad..." | Re-trigger Greptile

@ian-pascoe
ian-pascoe merged commit fac459f into mainMay 15, 2026
5 checks passed
@ian-pascoe
ian-pascoe deleted the fix-native-package-publishing branch May 15, 2026 15:26
Sign up for freeto 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

@ian-pascoe