-
Notifications
You must be signed in to change notification settings - Fork 23
release: v0.3.0 #673
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
release: v0.3.0 #673
Conversation
📝 WalkthroughWalkthroughThis PR updates the package version from 0.2.4 to 0.3.0 across the repository. The changes include updating the main package.json file in Possibly related PRs
Suggested reviewers
✨ 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 |
Manual Deploy AvailableYou can trigger a manual deploy of this PR branch to testnet: Alternative: Comment
Comment updated automatically when the PR is synchronized. |
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.
Actionable comments posted: 1
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
⛔ Files ignored due to path filters (1)
Cargo.lockis excluded by!**/*.lock
📒 Files selected for processing (3)
.github/packages/npm-package/package.json(2 hunks).github/packages/npm-package/package.json.tmpl(1 hunks)Cargo.toml(1 hunks)
🧰 Additional context used
🧠 Learnings (1)
📓 Common learnings
Learnt from: thlorenz
Repo: magicblock-labs/magicblock-validator PR: 650
File: magicblock-chainlink/src/submux/subscription_task.rs:13-99
Timestamp: 2025-11-20T08:57:07.217Z
Learning: In the magicblock-validator repository, avoid posting review comments that merely confirm code is correct or matches intended behavior without providing actionable feedback, suggestions for improvement, or identifying potential issues. Such confirmatory comments are considered unhelpful noise by the maintainers.
Learnt from: thlorenz
Repo: magicblock-labs/magicblock-validator PR: 664
File: magicblock-chainlink/src/testing/mod.rs:342-370
Timestamp: 2025-11-21T11:03:26.756Z
Learning: In the magicblock-validator codebase, avoid leaving review comments that merely acknowledge code is correct or well-structured when there is no actionable suggestion, improvement, or issue to flag. Only comment when there is something specific to recommend, fix, or clarify.
Learnt from: thlorenz
Repo: magicblock-labs/magicblock-validator PR: 587
File: test-manual/Cargo.toml:0-0
Timestamp: 2025-10-26T16:54:39.084Z
Learning: In the magicblock-validator repository, use git branch references (not commit hashes or tags) for the helius-laserstream dependency to allow automatic updates when the branch is pushed to.
| [workspace.package] | ||
| # Solana Version (2.2.x) | ||
| version = "0.2.4" | ||
| version = "0.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.
🧩 Analysis chain
Verify version mismatch: PR title indicates v3.0.0 but changes show 0.3.0.
The PR title states "release: v3.0.0" but all version changes across the repository (Cargo.toml, package.json, and package.json.tmpl) update to "0.3.0". These are semantically different versions (major version 3 vs. minor version 3 in pre-1.0). Please confirm which version is correct before merging.
🏁 Script executed:
#!/bin/bash
# Verify PR title and version changes across repo
# 1. Get PR title from GitHub
# 2. Find all version strings in config files
echo "=== PR Details ==="
gh pr view --json title,body -q '.title'
echo -e "\n=== Cargo.toml version ==="
fd -e "Cargo.toml" --exec grep -H 'version' {} \;
echo -e "\n=== package.json versions ==="
fd -e "package.json" --exec grep -H '"version"' {} \;
echo -e "\n=== package.json.tmpl versions ==="
fd -e "package.json.tmpl" --exec grep -H '"version"' {} \;
echo -e "\n=== Other version references ==="
rg -n '(version|VERSION)\s*=\s*["\']?[0-9]+\.[0-9]+\.[0-9]+' --type=toml --type=jsonLength of output: 268
🏁 Script executed:
#!/bin/bash
# Broader search for version files without relying on GitHub CLI
echo "=== Repository structure (top level) ==="
ls -la | head -20
echo -e "\n=== All TOML files ==="
find . -name "*.toml" -type f 2>/dev/null
echo -e "\n=== All JSON files ==="
find . -name "*.json" -o -name "*.json.tmpl" 2>/dev/null
echo -e "\n=== Version strings in TOML files ==="
find . -name "*.toml" -type f 2>/dev/null -exec grep -H "version" {} \;
echo -e "\n=== Version strings in JSON files ==="
find . -name "*.json" -type f 2>/dev/null -exec grep -H "version" {} \;
echo -e "\n=== Version strings in JSON.tmpl files ==="
find . -name "*.json.tmpl" -type f 2>/dev/null -exec grep -H "version" {} \;Length of output: 14382
🏁 Script executed:
#!/bin/bash
# Search for git and documentation clues about version intent
echo "=== Recent commits mentioning version ==="
git log --oneline -20 2>/dev/null | head -20
echo -e "\n=== Commit message details for HEAD ==="
git log -1 --format="%B" 2>/dev/null
echo -e "\n=== Search for CHANGELOG or release notes ==="
find . -iname "*CHANGE*" -o -iname "*RELEASE*" -o -iname "*NEWS*" 2>/dev/null | head -10
echo -e "\n=== Check .git for branch/ref info ==="
git branch -a 2>/dev/null | head -10
git symbolic-ref HEAD 2>/dev/null || echo "Detached HEAD"
echo -e "\n=== Current git status ==="
git status 2>/dev/null | head -10Length of output: 2009
Fix version mismatch in commit message or code: "v3.0.0" vs "0.3.0".
The commit message states "release: v3.0.0", but Cargo.toml and package.json both specify "0.3.0". Given the previous release was v0.2.4, the intended version is likely 0.3.0, suggesting the commit message contains a typo. Update the commit message to "release: v0.3.0" to align with the actual version changes, or update all version strings to 3.0.0 if that was the intended major release bump.
🤖 Prompt for AI Agents
In Cargo.toml around lines 43 to 43 the version is set to "0.3.0" while the
commit message reads "release: v3.0.0"; fix the mismatch by either (A) updating
the commit message to "release: v0.3.0" to match Cargo.toml and package.json, or
(B) if the intent was a major bump to 3.0.0, update Cargo.toml and package.json
to "3.0.0" and ensure changelog/commit message and any CI/release metadata are
updated consistently.
GabrielePicco
left a comment
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.
LGTM!
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.