Skip to content

fix: prepare scoped npm prerelease - #252

Merged
pbroom merged 3 commits into
mainfrom
codex/npm-next-0.1.0
Oct 11, 2026
Merged

pbroom merged 3 commits into
mainfrom
codex/npm-next-0.1.0

Conversation

@pbroom

@pbroom pbroom commented Oct 11, 2026 •

Copy link
Copy Markdown
Owner

npm rejected the unscoped color-kit name because it is too similar to the existing colorkit package. Prepare the authorized fallback @pbroom/[email protected], published with public access under next.

Update the facade manifest, built JS/CJS/type self-imports, package checks, workspace dependency and filters, docs aliases, public examples, install commands, API labels, and release guidance together. The engine API, internal @color-kit/* packages, product name, and directory names stay the same. The changelog records the existing unpublished development changes under the requested prerelease version.

Validation passed after rebasing onto main with the hero axis fix: lint, preproduction policy, full build/DTS/docs, artifact checks (exports/licensing/publint/attw), 2,101 workspace tests, formatting, strict agent learnings, typecheck, and size budgets. A fresh install of the final 711-file tarball passed every ESM/CJS subpath, shared-state and removed-API assertions, NodeNext ESM/CJS type imports, and MIT/Apache notice checks.

Agent learnings: N/A; this applies the existing hard-cutover and release policies.

@vercel

vercel Bot commented Oct 11, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
color-kit Ready Ready Preview Oct 11, 2026 3:13pm UTC

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 11, 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-10-11T15:03:47.558372Z 36379a4 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.

pbroom commented Oct 11, 2026

Copy link
Copy Markdown
Owner Author

This stack of pull requests is managed by Graphite. Learn more about stacking.

@greptile-apps

greptile-apps Bot commented Oct 11, 2026 •

Copy link
Copy Markdown

RetriggerConfidence Score: 4/5

[High impact] Bumps package version and publishes under prerelease tag.

The PR appears safe to merge, with a non-blocking update needed to the release guide.

Fix All in CursorFindings

  1. P2 Release instructions disagree ▶

Summary

Prepares color-kit for its initial npm prerelease.

  • The package and changelog mark the initial npm prerelease.

Reviews (1) · Last reviewed commit: "chore: prepare initial npm prerelease" · Reviewed by Greptile

Comment thread packages/color-kit/package.json

@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: 36379a4c66

ℹ️ 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".

Comment thread packages/color-kit/package.json
@pbroom
pbroom force-pushed the codex/npm-next-0.1.0 branch from 36379a4 to 453e521 Compare October 11, 2026 15:08
@pbroom pbroom changed the title chore: prepare initial npm prerelease fix: publish under the available scoped npm name Oct 11, 2026
@pbroom pbroom changed the title fix: publish under the available scoped npm name fix: prepare scoped npm prerelease Oct 11, 2026
@pbroom pbroom changed the title fix: prepare scoped npm prerelease docs: clarify bootstrap prerelease policy Oct 11, 2026
@pbroom pbroom changed the title docs: clarify bootstrap prerelease policy fix: prepare scoped npm prerelease Oct 11, 2026
@pbroom
pbroom merged commit 1b002c4 into main Oct 11, 2026
7 checks passed
@pbroom
pbroom deleted the codex/npm-next-0.1.0 branch October 11, 2026 15:15

This branch was successfully deployed

1 active deployment
Preview — 73ee5230 Deployed Oct 11, 2026 by vercel[bot]
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