release: v1.3.1 → main#800
Conversation
## Summary - Bump NPM packages (`@yellow-org/sdk`, `@yellow-org/sdk-compat`, `@yellow-org/sdk-mcp`) to `1.3.0` - Set `appVersion: 1.3.0` on nitronode, playground, faucet-app Helm charts Merges `release/v1.3.0` into `stable`. Tagging `v1.3.0` on stable HEAD after merge triggers `stable-tag.yml` (Docker builds for nitronode, faucet-app, playground). `mcp-v1.3.0` tag triggers MCP publish. ## Test plan - [ ] CI green - [ ] Tag `v1.3.0` on stable HEAD post-merge - [ ] Tag `mcp-v1.3.0` for MCP publish - [ ] Verify Docker images pushed to ghcr.io - [ ] Verify NPM packages published 🤖 Generated with [Claude Code](https://claude.com/claude-code)
- Bump @yellow-org/sdk, @yellow-org/sdk-compat, @yellow-org/sdk-mcp to 1.3.1 - Add prepublishOnly to @yellow-org/sdk-compat (clean + build:prod) - Tighten @yellow-org/sdk-mcp prepublishOnly to clean dist/content first (1.3.0 sdk-compat shipped a stale dist; prevents recurrence) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The MCP package depends on @yellow-org/sdk and @yellow-org/sdk-compat being on npm before its preflight passes. Until those two packages also have automated publishing, MCP is published manually and the CI publish jobs would race against (or fail before) the manual sdk/sdk-compat publish. Disable the auto-trigger and gate the publish jobs behind `if: false` so re-enabling is a one-line revert. Keep PR validation running. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
Warning Review limit reached
More reviews will be available in 54 minutes and 45 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 ignored due to path filters (3)
📒 Files selected for processing (5)
✨ 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 |
1 participant
Summary
Sibling of `release/v1.3.1 → stable` PR. Carries the version bumps and the `prepublishOnly` hardening into main so future development sees them.
Changes
🤖 Generated with Claude Code