-
-
Notifications
You must be signed in to change notification settings - Fork 35
chore: release v11.3.0 #574
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #574 +/- ##
=======================================
Coverage 93.74% 93.74%
=======================================
Files 14 14
Lines 2943 2943
=======================================
Hits 2759 2759
Misses 184 184 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
6ff14eb to
aa61ade
Compare
CodSpeed Performance ReportMerging #574 will not alter performanceComparing Summary
|
b23ec10 to
5df270e
Compare
5df270e to
447a166
Compare
| [package] | ||
| name = "oxc_resolver" | ||
| version = "11.2.1" | ||
| version = "11.3.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
According to the PR description, there are breaking API changes in both oxc_resolver and oxc_resolver_napi. The semver check failures indicate that:
ResolveOptionsstruct has new required fields- A field was removed from
ResolveOptions ResolveResulthas a new required field
Following semantic versioning principles, these breaking changes require a major version bump to 12.0.0 rather than the minor version bump to 11.3.0 shown here. This ensures downstream consumers are properly notified of the incompatible API changes.
| version = "11.3.0" | |
| version = "12.0.0" |
Spotted by Diamond
Is this helpful? React 👍 or 👎 to let us know.
No description provided.