Skip to content

ci(release): publish npm alphas under alpha tag#51

Merged
omerakben merged 1 commit into
mainfrom
codex/npm-alpha-dist-tag
Jun 14, 2026
Merged

ci(release): publish npm alphas under alpha tag#51
omerakben merged 1 commit into
mainfrom
codex/npm-alpha-dist-tag

Conversation

@omerakben

Copy link
Copy Markdown
Owner

Summary

  • Publish npm prerelease versions with the explicit alpha dist-tag
  • Document alpha dist-tag verification in release readiness

Why

  • The first npm-publish workflow run reached the publish step and npm rejected the prerelease without an explicit tag:
    npm error You must specify a tag using --tag when publishing a prerelease version.

Validation

  • npm publish --dry-run --access public --tag alpha
  • ruby -e "require 'yaml'; YAML.load_file('.github/workflows/npm-publish.yml'); puts 'yaml ok'"\n- git diff --check\n\n## Risks / follow-ups\n- After merge, rerun npm-publish.yml with version=0.21.2-alpha.0\n- If npm trusted publishing is not configured, the next failure should be npm OIDC/trusted-publisher authorization rather than package shape\n

Copilot AI review requested due to automatic review settings June 14, 2026 16:27
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

@coderabbitai

coderabbitai Bot commented Jun 14, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@omerakben, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 37 minutes and 18 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more credits in the billing tab to continue.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 49becf53-ea6e-4d29-8b7b-49ddf8f76a7a

📥 Commits

Reviewing files that changed from the base of the PR and between f9491c5 and 505b9fa.

📒 Files selected for processing (2)
  • .github/workflows/npm-publish.yml
  • docs/RELEASE_READINESS.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch codex/npm-alpha-dist-tag

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 the release readiness documentation (docs/RELEASE_READINESS.md) to include instructions for viewing npm distribution tags and explicitly using the --tag alpha flag when publishing alpha versions locally. It also clarifies that alpha versions are published under the alpha dist-tag rather than latest. There are no review comments to address, so no additional feedback is provided.

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.

@omerakben omerakben merged commit 3e8f877 into main Jun 14, 2026
4 checks passed
@omerakben omerakben deleted the codex/npm-alpha-dist-tag branch June 14, 2026 16:29

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 the npm publishing workflow and release-readiness documentation so prerelease (alpha) versions can be published successfully by using an explicit alpha dist-tag, aligning with npm’s requirement for prerelease publishing.

Changes:

  • Update GitHub Actions npm publish step to include an alpha dist-tag.
  • Document dist-tag verification and local publish instructions for alpha releases.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File Description
docs/RELEASE_READINESS.md Adds guidance to verify npm dist-tags and updates local publish instructions to use --tag alpha.
.github/workflows/npm-publish.yml Adds --tag alpha to the npm publish command in the GitHub Actions workflow.

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

Comment on lines 93 to +95
- name: Publish package
if: steps.published.outputs.already != 'true'
run: npm publish --access public
run: npm publish --access public --tag alpha
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