Skip to content

docs(release): mark npm alpha published#52

Merged
omerakben merged 1 commit into
mainfrom
codex/npm-published-status
Jun 14, 2026
Merged

docs(release): mark npm alpha published#52
omerakben merged 1 commit into
mainfrom
codex/npm-published-status

Conversation

@omerakben

@omerakben omerakben commented Jun 14, 2026

Copy link
Copy Markdown
Owner

Summary

  • Mark npm @tuel/code-oz@0.21.2-alpha.0 as published under the alpha dist-tag
  • Pin current npm install docs to the exact release version while latest still points at 0.21.1-alpha.0
  • Update the plugin resolver hard-stop install hint to use the plugin-pinned npm package version

Why

  • The npm package was published successfully after interactive npm login and 2FA
  • Registry state now has alpha -> 0.21.2-alpha.0, while latest still points at 0.21.1-alpha.0
  • Unqualified npm install instructions could otherwise install the older release

Validation

  • npm view @tuel/code-oz@0.21.2-alpha.0 version dist-tags --json
  • npm view @tuel/code-oz dist-tags --json
  • clean temp npx -y @tuel/code-oz@0.21.2-alpha.0 --version -> 0.21.2-alpha.0
  • bun test tests/plugins/bootstrap-resolver.test.ts
  • git diff --check

Risks / follow-ups

  • Optional: promote npm latest with npm dist-tag add @tuel/code-oz@0.21.2-alpha.0 latest --otp=
  • Historical handoff/release-note files for older releases were left unchanged

Summary by CodeRabbit

  • Documentation
    • Updated installation guides and provider setup documentation to reflect availability of version 0.21.2-alpha.0
    • Clarified npm registry channels and distribution methods for the alpha release
    • Enhanced release readiness and trust documentation with specific version details

Copilot AI review requested due to automatic review settings June 14, 2026 18:10
@coderabbitai

coderabbitai Bot commented Jun 14, 2026

Copy link
Copy Markdown

Review Change Stack

Caution

Review failed

Pull request was closed or merged during review

📝 Walkthrough

Walkthrough

All install references to @tuel/code-oz are pinned to 0.21.2-alpha.0: the launcher shell script now passes ${PINNED_VERSION} in its not-installed npm install instruction, the hard-stop test asserts the versioned string in output, and README, PROVIDER_SETUP, and TRUST docs update their command examples accordingly. Release readiness and handoff docs are updated to reflect the current npm alpha/latest dist-tag split.

Changes

Pin @tuel/code-oz to 0.21.2-alpha.0

Layer / File(s) Summary
Launcher script version pin and test assertion
plugins/code-oz/scripts/resolve-code-oz.sh, tests/plugins/bootstrap-resolver.test.ts
resolve-code-oz.sh not-installed branch updated to emit npm i -g @tuel/code-oz@${PINNED_VERSION}; hard-stop test updated to assert that versioned string appears in combined output.
User-facing install docs pinned to 0.21.2-alpha.0
README.md, docs/PROVIDER_SETUP.md, docs/TRUST.md
npm install snippets, npmrc gotcha notes, Claude Code plugin fallback command, and TRUST scope-routing examples updated from unpinned @tuel/code-oz to @tuel/code-oz@0.21.2-alpha.0.
Release readiness and handoff docs
docs/RELEASE_READINESS.md, docs/handoffs/2026-06-14-release-readiness-audit.md
Release readiness doc adds npm dist-tag status prose, a new publish/dist-tag verification section with exact install and latest promotion commands, and a revised "ready" declaration; handoff audit reflects the alpha/latest dist-tag split and the remaining unqualified-install gap.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~4 minutes

Poem

🐇 Hopped through the garden and pinned every vine,
No more wild installs left unconfined!
0.21.2-alpha.0 — exact as can be,
Dist-tags and scripts all aligned perfectly.
npm latest still waits for its 2FA key,
But the alpha bunny has hopped the right way! 🥕

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title 'docs(release): mark npm alpha published' directly describes the main change—updating documentation to reflect the npm alpha release publication state.
Description check ✅ Passed The description includes a clear summary, explanation of why changes were made, validation steps performed, and identifies follow-up risks, covering all essential sections.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check 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 docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch codex/npm-published-status

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@gemini-code-assist gemini-code-assist 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.

Code Review

This pull request updates documentation, installation guides, and helper scripts to pin npm installation commands to the exact version 0.21.2-alpha.0 instead of relying on the moving latest tag. It also updates release readiness and audit logs to reflect the publication of v0.21.2-alpha.0. Feedback was provided on a test in bootstrap-resolver.test.ts to dynamically retrieve the pinned version using readPinnedVersion() instead of hardcoding the version string, which will prevent future test failures when the version is bumped.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

Comment on lines +263 to +264
// Must pin the plugin version instead of relying on npm's moving latest tag.
expect(result.stdout + result.stderr).toContain('@tuel/code-oz@0.21.2-alpha.0')

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

The test currently hardcodes the version string '0.21.2-alpha.0'. To prevent this test from breaking when the version is bumped in plugin.json in the future, retrieve the pinned version dynamically using the existing readPinnedVersion() helper, matching the pattern used in other tests in this file.

Suggested change
// Must pin the plugin version instead of relying on npm's moving latest tag.
expect(result.stdout + result.stderr).toContain('@tuel/code-oz@0.21.2-alpha.0')
// Must pin the plugin version instead of relying on npm's moving latest tag.
const pinnedVersion = await readPinnedVersion()
expect(result.stdout + result.stderr).toContain('@tuel/code-oz@' + pinnedVersion)

Copilot AI 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.

Pull request overview

Updates release-facing documentation and plugin resolver messaging to reflect that @tuel/code-oz@0.21.2-alpha.0 is now published under the alpha dist-tag, and ensures install guidance pins the exact version while latest still points to 0.21.1-alpha.0.

Changes:

  • Pin npm install instructions in docs/README to @tuel/code-oz@0.21.2-alpha.0.
  • Update the plugin resolver hard-stop message to print the plugin-pinned version.
  • Refresh release-readiness and handoff docs to reflect the npm publish + dist-tag state, and add a regression test expectation for pinned install hints.

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 2 comments.

Show a summary per file
File Description
tests/plugins/bootstrap-resolver.test.ts Adds an assertion that hard-stop output includes a pinned npm package version.
README.md Pins npm install command and updates plugin fallback wording to reference the pinned package version.
plugins/code-oz/scripts/resolve-code-oz.sh Prints pinned npm install guidance using the version parsed from plugin.json.
docs/TRUST.md Pins npm install examples to the published alpha version.
docs/RELEASE_READINESS.md Updates release readiness status and documents npm publish/dist-tag verification + promotion steps.
docs/PROVIDER_SETUP.md Pins recommended first-run npm install command to the published alpha version.
docs/handoffs/2026-06-14-release-readiness-audit.md Updates the audit note to reflect the completed npm publish and current dist-tag state.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +263 to +264
// Must pin the plugin version instead of relying on npm's moving latest tag.
expect(result.stdout + result.stderr).toContain('@tuel/code-oz@0.21.2-alpha.0')
Comment thread README.md
```

The `code-oz` plugin is a thin wrapper. It adds `/code-oz-run`, `/code-oz-init`, `/code-oz-doctor`, and `/code-oz-resume`, and each command discovers the `code-oz` engine on your `PATH`, falling back to `npx @tuel/code-oz` when the binary is absent. Install the engine from the channels above for the fastest path. The plugin never writes gates, events, or reviews — the engine binary is the only writer, so the gate guarantees hold whether you drive code-oz from the CLI or through the plugin.
The `code-oz` plugin is a thin wrapper. It adds `/code-oz-run`, `/code-oz-init`, `/code-oz-doctor`, and `/code-oz-resume`, and each command discovers the `code-oz` engine on your `PATH`, falling back to the plugin-pinned `npx @tuel/code-oz@0.21.2-alpha.0` when the binary is absent. Install the engine from the channels above for the fastest path. The plugin never writes gates, events, or reviews — the engine binary is the only writer, so the gate guarantees hold whether you drive code-oz from the CLI or through the plugin.
@omerakben omerakben merged commit fbc73f2 into main Jun 14, 2026
3 of 4 checks passed
@omerakben omerakben deleted the codex/npm-published-status branch June 14, 2026 18:13
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.

2 participants