chore(release): prepare npm publishing switch - #811
ScriptedAlchemy wants to merge 1 commit into
Conversation
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: efdd9668e2
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "url": "git+https://github.com/ScriptedAlchemy/agent-bundle.git" | ||
| }, | ||
| "publishConfig": { | ||
| "access": "public", |
There was a problem hiding this comment.
Add the required changeset for public publishing
This changes the publishable agent-bundle manifest and shipped README but adds no .changeset/*.md file. Setting publishConfig.access to public is an intentional release-behavior change rather than a genuinely no-op edit, so using the proposed skip-changeset label would bypass the repository's required versioning and release-note record; add one patch changeset covering agent-bundle.
AGENTS.md reference: AGENTS.md:L114-L127
Useful? React with 👍 / 👎.
commit: |
|
superseded: distribution is pkg.pr.new only |
Summary
changesets/action@v2publish-script, thepnpm releasebuild path, and the four-package registry verification listExternal blocker
Do not enable or merge Version Packages yet.
agent-bundle@0.1.2on npm is owned byyujiachen-yand points to an unrelated repository. Transfer that name (or rename this package) and create or confirm control of the@agent-bundlenpm scope first; otherwisechangeset publishcan leave a partial four-package release.Owner enablement checklist
agent-bundle,create-agent-bundle,rsc-markdown-stream, and the@agent-bundlescope; set repository secretNPM_TOKEN.AGENT_BUNDLE_NPM_PUBLISH=true.mainpush after step 2.If publishing does not happen, Verify published registry artifacts fails on each package version that
npm viewcannot resolve.Verification
pnpm buildpnpm --filter agent-bundle --filter @agent-bundle/runtime --filter rsc-markdown-stream --filter create-agent-bundle -r exec npm pack --dry-runnpx --yes publint@latest <package>for all four publishable packagespnpm check:release:cipnpm docs:site:buildChangeset
Metadata, workflow comments, and documentation only; apply
skip-changeset.