You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
StorageResult.last_update_block is now non-optional: When INCLUDE_LAST_UPDATE_BLOCK response flag is set on starknet_getStorageAt, the last_update_block field is always returned as a u64 (defaulting to 0 for never-modified slots) instead of Option<u64>. This aligns with the RPC spec STORAGE_RESULT schema.
Development related changes
Bumped all crate versions from 0.8.0-rc.2 to 0.8.0-rc.3.
Versioned website docs for 0.8.0-rc.3.
Added get_storage_with_response_flags integration test covering INCLUDE_LAST_UPDATE_BLOCK flag behavior across multiple storage updates and block advancements.
Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 20f07f6b-4368-4ca2-94d5-cdbcdbb3f8ca
You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.
Use the checkbox below for a quick retry:
🔍 Trigger review
Note
.coderabbit.yaml has unrecognized properties
CodeRabbit is using all valid settings from your configuration. Unrecognized properties (listed below) have been ignored and may indicate typos or deprecated fields that can be removed.
⚠️ Parsing warnings (1)
Validation error: Unrecognized key(s) in object: 'auto_resolve_threads'
If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json
✨ Finishing Touches🧪 Generate unit tests (beta)
Create PR with unit tests
Commit unit tests in branch release-0.8.0-rc.3
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Usage related changes
StorageResult.last_update_blockis now non-optional: WhenINCLUDE_LAST_UPDATE_BLOCKresponse flag is set onstarknet_getStorageAt, thelast_update_blockfield is always returned as au64(defaulting to0for never-modified slots) instead ofOption<u64>. This aligns with the RPC specSTORAGE_RESULTschema.Development related changes
0.8.0-rc.2to0.8.0-rc.3.0.8.0-rc.3.get_storage_with_response_flagsintegration test coveringINCLUDE_LAST_UPDATE_BLOCKflag behavior across multiple storage updates and block advancements.Checklist:
./scripts/format.sh./scripts/clippy_check.sh./scripts/check_unused_deps.sh./scripts/check_spelling.sh./website/README.md