-
Notifications
You must be signed in to change notification settings - Fork 51
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
[FEAT]: Standardize the versions of scarb
and snforge
used across all contracts
#99
Comments
scarb
and snforge
used across all contracts.scarb
and snforge
used across all contracts
May I take care of this? I am a software engineer with working knowledge of Cairo. I will be able to send my first PR in 48 hours. |
may i take up this issue @danielcdz ? background: cairo dev with 5 months of experience and regular contributor at @keep-starknet-strange eta: 2 days |
Can I get assigned to this task @danielcdz |
Proposal to Work on the IssueI would be delighted to contribute to this issue, as I have extensive experience with Cairo programming and developing decentralized applications on StarkNet. Estimated TimelineI anticipate delivering a working solution within the next 24 hours. Please let me know if I can proceed. Looking forward to contributing and collaborating! Best regards, |
I’m interested in this one. |
May I take care of this? I am a software engineer with working knowledge of Cairo and it's tooling like the scarb and snforge, I will update them to make sure they all are in the latest version, and fix any bug or deprecation that might be introduced to the code base for part of the codes int e codebase that depend on these tools. I will be able to send my first PR in 48 hours. |
Hi... |
Would love to tackle this! |
I’m interested in this one. |
Could I be assigned to this? |
Can I take care of this issue? |
📘 Description
To ensure consistency and compatibility across all contracts, we need to standardize the versions of
cairo
,scarb
, andsnforge
. Currently, these versions differ between contracts in some cases, which can lead to inconsistencies and potential issues. Standardizing these tools will simplify development and ensure a smooth workflow.✅ Acceptance Criteria
cairo
,scarb
, andsnforge
.📜 Additional Notes
The text was updated successfully, but these errors were encountered: