Release v19.0.2 with observable migration progress - #836
Conversation
|
Warning Review limit reached
Next review available in: 45 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. 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: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughSummary by CodeRabbit
WalkthroughThe release is bumped from v19.0.1 to v19.0.2 across manifests and documentation. Retained-v18 migration guidance now specifies the v19.0.2 migrator and its observability details, with unit tests updated to verify the revised documentation markers and commands. ChangesRelease and migration documentation
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related issues
Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (3 passed)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
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 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 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 `@test/unit/scripts/v19-migration-guidance.test.ts`:
- Around line 30-31: Update the assertions in the migration guidance test,
including the checks for both documents, to match the package version together
with the `git-warp-v18-to-v19` invocation. Ensure the expected command
specifically uses `@git-stunts/git-warp@19.0.2`, rather than asserting the
version appears elsewhere independently.
🪄 Autofix (Beta)
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: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 72657eac-1c1e-4cb0-a00e-17ffde5bc361
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (14)
ARCHITECTURE.mdCHANGELOG.mdREADME.mddocs/migrations/v19/README.mddocs/operations/README.mddocs/topics/README.mddocs/topics/api/README.mdjsr.jsonpackage.jsonpackages/warp-adapters/package.jsonpackages/warp-kernel/package.jsonpackages/warp-orset/package.jsonscripts/v18-to-v19/README.mdtest/unit/scripts/v19-migration-guidance.test.ts
📜 Review details
⏰ Context from checks skipped due to timeout. (15)
- GitHub Check: type-firewall-docs
- GitHub Check: type-firewall-surface
- GitHub Check: type-firewall-quarantine
- GitHub Check: v19 base/head performance
- GitHub Check: test-bun
- GitHub Check: type-firewall-audit-advisory
- GitHub Check: typecheck-test-advisory
- GitHub Check: test-node (22)
- GitHub Check: type-firewall-semgrep
- GitHub Check: test-deno
- GitHub Check: coverage-threshold
- GitHub Check: type-firewall-lint
- GitHub Check: type-firewall-types
- GitHub Check: type-firewall-generated-sdk
- GitHub Check: preflight
🧰 Additional context used
📓 Path-based instructions (1)
**/*.{ts,tsx,js,jsx}
📄 CodeRabbit inference engine (AGENTS.md)
**/*.{ts,tsx,js,jsx}: Do not use direct imports fromsrc/infrastructure/**insrc/domain/**orsrc/ports/**; depend on a port instead.
Do not use direct Node built-ins insrc/domain/**orsrc/ports/**; use a port instead.
Files:
test/unit/scripts/v19-migration-guidance.test.ts
🧠 Learnings (2)
📚 Learning: 2026-03-04T12:08:30.347Z
Learnt from: flyingrobots
Repo: git-stunts/git-warp PR: 63
File: package.json:126-126
Timestamp: 2026-03-04T12:08:30.347Z
Learning: Vitest 4 removes vite-node as a dependency and rewrites its pool system. Do not flag the absence of vite-node in package.json or lockfiles as an error for Vitest 4 projects. Use this as a general guideline: if a project uses Vitest 4, missing vite-node is expected and correct; only flag issues if there is evidence the project is not using Vitest 4 or if vite-node is explicitly required by the project.
Applied to files:
package.jsonpackages/warp-kernel/package.jsonpackages/warp-orset/package.jsonpackages/warp-adapters/package.json
📚 Learning: 2026-03-08T19:50:17.519Z
Learnt from: flyingrobots
Repo: git-stunts/git-warp PR: 65
File: CHANGELOG.md:88-88
Timestamp: 2026-03-08T19:50:17.519Z
Learning: Follow the Keep a Changelog convention for CHANGELOG.md. Allow duplicate subheadings across versions (e.g., '### Added', '### Fixed'). Configure markdownlint MD024 with {"siblings_only": true} to avoid cross-version false positives.
Applied to files:
CHANGELOG.md
🔇 Additional comments (13)
jsr.json (1)
3-3: LGTM!package.json (1)
3-3: LGTM!packages/warp-adapters/package.json (1)
3-3: LGTM!packages/warp-kernel/package.json (1)
3-3: LGTM!packages/warp-orset/package.json (1)
3-3: LGTM!CHANGELOG.md (1)
10-39: LGTM!ARCHITECTURE.md (1)
13-18: LGTM!docs/topics/README.md (1)
8-14: LGTM!docs/topics/api/README.md (1)
3-3: LGTM!README.md (1)
49-63: LGTM!Also applies to: 78-82
docs/migrations/v19/README.md (1)
4-5: LGTM!Also applies to: 30-30, 226-226, 370-370, 469-469
docs/operations/README.md (1)
19-21: LGTM!Also applies to: 41-45
scripts/v18-to-v19/README.md (1)
28-30: LGTM!Also applies to: 75-78
Release Preflight
If this PR is from a |
Release Preflight
If this PR is from a |
1 participant
Summary
Refs #835.