chore: add package repository metadata#32
Merged
Conversation
Add GitHub repository metadata to all published package manifests and include MIT licenses for the scoped packages.
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
1 participant
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.
What is this?
This PR fills in missing npm package metadata for the published agent-cdp packages. Package consumers now get consistent GitHub repository, issue tracker, README, and license metadata across the CLI, SDK, and shared protocol packages.
How does it work?
The CLI package keeps its existing GitHub repository metadata and now declares its monorepo package directory. The
@agent-cdp/sdkand@agent-cdp/protocolmanifests now declare the canonical GitHub repository, package-specific directories, shared issue tracker, package README homepages, and MIT license metadata.Backward compatibility: this only adds package metadata. Existing commands, flags, exports, files, build output, daemon behavior, and runtime workflows remain unchanged.
Why is this useful?
Reviewers and package consumers can navigate from each published package to the right source directory, issues, README, and license without guessing how the monorepo is laid out.
Risks: the change is low risk because it does not affect runtime code or package entry points. The main compatibility assumption is that
callstackincubator/agent-cdpand themasterbranch remain the canonical GitHub locations for these packages.Manual testing: from a clean checkout on
chore/package-github-metadata, runnode -e "for (const file of ['packages/agent-cdp/package.json','packages/sdk/package.json','packages/protocol/package.json']) JSON.parse(require('fs').readFileSync(file, 'utf8')); console.log('package manifests are valid JSON')"andCI=true pnpm build. Verify the manifests parse successfully and all package builds complete.