fix: correct 0.7 release records and catalog publishing - #64
Conversation
|
Warning Review limit reached
Next review available in: 4 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (9)
📝 WalkthroughWalkthroughThe release workflow now validates comparison provenance and gates catalog publication on successful CI jobs. Release synchronization validates immutable version-tag links. Documentation, changesets, changelogs, consumer checks, and release-status tests now record the 0.7.0 release updates. ChangesRelease hardening
Estimated code review effort: 3 (Moderate) | ~20 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 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 |
|
View your CI Pipeline Execution ↗ for commit 353d2d2
☁️ Nx Cloud last updated this comment at |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.changeset/catalog-case-119.md:
- Around line 5-7: Replace the vague “exact package subpath” wording in
.changeset/catalog-case-119.md with the literal subpath for catalog case 119,
then regenerate the corresponding release entries in CHANGELOG.md and
packages/react-charts-catalog/CHANGELOG.md so all three descriptions match.
In @.github/workflows/chart-library-benchmarks.yml:
- Line 345: Update the publish-catalog job condition to require !cancelled()
after the static and ci success checks, preventing publication when the workflow
is cancelled. Update the corresponding assertion in the CI workflow test to
expect the new condition.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 29f0fb1a-ccd3-43c7-95e3-08ff0438bf4c
📒 Files selected for processing (16)
.changeset/catalog-case-119.md.changeset/native-host-parity.md.changeset/steady-release-links.md.github/workflows/chart-library-benchmarks.ymlAPI-FRICTION.mdCHANGELOG.mdREADME.mddocs/comparison.mddocs/installation.mdpackages/charts-core/docs/comparison.mdpackages/charts-core/docs/installation.mdpackages/react-charts-catalog/CHANGELOG.mdpackages/react-native-charts/CHANGELOG.mdscripts/ci-workflow.test.mjsscripts/sync-release-version.mjsscripts/sync-release-version.test.mjs
![nx-cloud[bot]](https://avatars.githubusercontent.com/in/80458?s=60&v=4){kind=small}
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@scripts/ci-workflow.test.mjs`:
- Around line 76-86: Update the test named “keeps packed-consumer installs
offline without resolving optional peers” to validate both generated offline
install commands, rather than accepting a single match. Assert that the command
pattern occurs twice, or separately verify the install command in each fixture
block while preserving the existing autoInstallPeers assertion.
In `@scripts/release-status.test.mjs`:
- Around line 205-206: Update the revision assertions in the release-status test
by removing the fixed 40-character hexadecimal format check, while retaining the
equality assertion comparing revision with expectedRevision.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: fae14c08-223e-4347-8f53-a8335029c328
📒 Files selected for processing (5)
.github/workflows/chart-library-benchmarks.ymlAPI-FRICTION.mdscripts/check-packed-consumers.mjsscripts/ci-workflow.test.mjsscripts/release-status.test.mjs
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
There was a problem hiding this comment.
Important
At least one additional CI pipeline execution has run since the conclusion below was written and it may no longer be applicable.
Nx Cloud has identified a possible root cause for your failed CI:
We identified that the charts-workspace:package-check failure is an environment issue, not a code regression. The CI pnpm offline mirror is missing metadata for @types/d3-force@>=3.0.10 <4.0.0-0, a peer dependency introduced by the new @tanstack/charts@0.7.0 release. Our offline cache needs to be warmed with this package's metadata before the task can pass.
No code changes were suggested for this issue.
Trigger a rerun:
🎓 Learn more about Self-Healing CI on nx.dev
1 participant
Corrects the release issues found while cutting 0.7.0:
Validated with focused release/workflow tests, docs checks, formatting checks, and Changesets status.
Summary by CodeRabbit
New Features
Documentation
Chores