chore(main): release 0.1.40#24
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reached
More reviews will be available in 23 minutes and 12 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 (1)
📒 Files selected for processing (3)
✨ 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 |
There was a problem hiding this comment.
1 issue found across 3 files
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="Cargo.toml">
<violation number="1" location="Cargo.toml:18">
P0: Version regression: workspace version is being decreased from `0.1.42` to `0.1.40`, but tag `v0.1.42` already exists as a release. This would regress the version below a previously released version, breaking semver expectations and version ordering.</violation>
</file>
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
|
|
||
| [workspace.package] | ||
| version = "0.1.42" | ||
| version = "0.1.40" |
There was a problem hiding this comment.
P0: Version regression: workspace version is being decreased from 0.1.42 to 0.1.40, but tag v0.1.42 already exists as a release. This would regress the version below a previously released version, breaking semver expectations and version ordering.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At Cargo.toml, line 18:
<comment>Version regression: workspace version is being decreased from `0.1.42` to `0.1.40`, but tag `v0.1.42` already exists as a release. This would regress the version below a previously released version, breaking semver expectations and version ordering.</comment>
<file context>
@@ -15,7 +15,7 @@ members = [".", "crates/*"]
[workspace.package]
-version = "0.1.42"
+version = "0.1.40"
edition = "2021"
rust-version = "1.88"
</file context>
| version = "0.1.40" | |
| version = "0.1.43" |
2579952 to
4fb6832
Compare
2eeab03 to
7b94d35
Compare
56f167d to
8898031
Compare
3ee791d to
d23edcd
Compare
b5ebab5 to
09ac28c
Compare
48ddab5 to
d62918b
Compare
9128d6f to
082feb9
Compare
0c603fc to
e1b7eb7
Compare
ecd7bf1 to
7d83df9
Compare
7aa26a6 to
69e7cf1
Compare
216c3dd to
49ea758
Compare
ed8d66f to
a2fb160
Compare
73cce5d to
77b4a6b
Compare
c3dc37a to
66d19bc
Compare
38e8a9f to
d901654
Compare
a10a41b to
579603b
Compare
29405eb to
884d57f
Compare
75d3edc to
27438db
Compare
778da9f to
c48a215
Compare
🤖 I have created a release beep boop
0.1.40 (2026-06-11)
Features
Bug Fixes
Refactoring
Documentation
This PR was generated with Release Please. See documentation.