chore(release): merge dev into main [0.260526.5]#92
Conversation
chore(workflows): consolidate npm publishing into single-source version.yml
|
Warning Review limit reached
More reviews will be available in 20 minutes and 40 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b9e15dc4eb
ℹ️ 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".
| --title "${TAG}" \ | ||
| --notes-file /tmp/release-notes.md | ||
| fi |
There was a problem hiding this comment.
Restore npm publish step after creating a main release
This change removes the only unconditional npm publish path from release.yml, so a push to main now just creates a GitHub release and exits without publishing @latest. The remaining publisher (.github/workflows/version.yml, auto-version job) only runs for main when the CI-triggering commit message matches startsWith(..., 'Merge pull request') and contains '/dev' (lines 51-53), so direct promotion commits (for example release: promote dev to main (...)) will no longer publish to npm at all.
Useful? React with 👍 / 👎.
Merging the latest stable version and publishing workflow consolidation from dev into main for release.