Skip to content

chore(release): prepare npm publishing switch - #811

Closed
ScriptedAlchemy wants to merge 1 commit into
mainfrom
chore/npm-publishing-ready
Closed

ScriptedAlchemy wants to merge 1 commit into
mainfrom
chore/npm-publishing-ready

Conversation

@ScriptedAlchemy

Copy link
Copy Markdown
Owner

Summary

  • switch Changesets and all four publishable package manifests to public npm access while preserving provenance and repository metadata
  • document the exact three-step owner enablement sequence in English and Chinese release docs
  • keep the existing release gates intact; audited changesets/action@v2 publish-script, the pnpm release build path, and the four-package registry verification list

External blocker

Do not enable or merge Version Packages yet. agent-bundle@0.1.2 on npm is owned by yujiachen-y and points to an unrelated repository. Transfer that name (or rename this package) and create or confirm control of the @agent-bundle npm scope first; otherwise changeset publish can leave a partial four-package release.

Owner enablement checklist

  1. Create an npm granular access token for CI with Read and write (publish and stage), Bypass 2FA, and All packages so it can publish agent-bundle, create-agent-bundle, rsc-markdown-stream, and the @agent-bundle scope; set repository secret NPM_TOKEN.
  2. Set repository variable AGENT_BUNDLE_NPM_PUBLISH=true.
  3. Merge the Version Packages pull request, with no intervening main push after step 2.

If publishing does not happen, Verify published registry artifacts fails on each package version that npm view cannot resolve.

Verification

  • pnpm build
  • pnpm --filter agent-bundle --filter @agent-bundle/runtime --filter rsc-markdown-stream --filter create-agent-bundle -r exec npm pack --dry-run
  • npx --yes publint@latest <package> for all four publishable packages
  • pnpm check:release:ci
  • pnpm docs:site:build
  • independent change-risk review on Fable; all code/config/docs findings resolved, external npm ownership blocker retained

Changeset

Metadata, workflow comments, and documentation only; apply skip-changeset.

@changeset-bot

changeset-bot Bot commented Sep 16, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: efdd966

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.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

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

@ScriptedAlchemy ScriptedAlchemy added the skip-changeset PR changes a publishable package but ships no observable change; changeset not required label Sep 16, 2026
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 16, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-09-16T17:28:57.854039Z efdd966 PR opened
ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 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",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge 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 👍 / 👎.

@pkg-pr-new

pkg-pr-new Bot commented Sep 16, 2026

Copy link
Copy Markdown
npm i https://pkg.pr.new/ScriptedAlchemy/agent-bundle@811
npm i https://pkg.pr.new/ScriptedAlchemy/agent-bundle/create-agent-bundle@811
npm i https://pkg.pr.new/ScriptedAlchemy/agent-bundle/rsc-markdown-stream@811
npm i https://pkg.pr.new/ScriptedAlchemy/agent-bundle/@agent-bundle/runtime@811

commit: efdd966

@ScriptedAlchemy

Copy link
Copy Markdown
Owner Author

superseded: distribution is pkg.pr.new only

@ScriptedAlchemy
ScriptedAlchemy deleted the chore/npm-publishing-ready branch September 16, 2026 20:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip-changeset PR changes a publishable package but ships no observable change; changeset not required

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant