Repository navigation
Advance master to 2.0.2-preview - #4741
Conversation
There was a problem hiding this comment.
🟡 Changes recommended
Master should advance to 2.1.0-preview.{height}; 2.0.2-preview.{height} belongs on release/2.0.
1 open finding
What changed in this PR
Advances the repository’s preview package version after the 2.0.1 release.
Changes:
- Updates the root version from
2.0.1-previewto2.0.2-preview.
| File | Description |
|---|---|
version.json |
Advances the preview version. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Code coverage✅ Coverage gate passed.
Coverage is above the recorded baseline - consider ratcheting Thresholds live in |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #4741 +/- ##
==========================================
+ Coverage 82.84% 82.85% +0.01%
==========================================
Files 2268 2268
Lines 346153 346153
Branches 60358 60358
==========================================
+ Hits 286783 286818 +35
+ Misses 39271 39241 -30
+ Partials 20099 20094 -5
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|

Description
#4740 makes
release/2.0the stable2.0.1release. This PR movesmasterfrom2.0.1-preview.{height}to2.0.2-preview.{height}, so its builds sort above the2.0.1release and stay on the preview channel.version.json:"version"2.0.1-preview.{height}→2.0.2-preview.{height}.versionHeightOffsetstays0.preview-version.props: unchanged.PreviewPackageBuildNumberonly applies when the root version is stable, so it has no effect onmaster.🤖 Generated with Claude Code