Skip to content
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

Open
danielcdz opened this issue Jan 21, 2025 · 11 comments · May be fixed by #113
Open

[FEAT]: Standardize the versions of scarb and snforge used across all contracts #99

danielcdz opened this issue Jan 21, 2025 · 11 comments · May be fixed by #113
Assignees
Labels
difficult: easy enhancement New feature or request ODBoost This issue will be available ONLY during the ODBoost

Comments

@danielcdz
Copy link
Member

danielcdz commented Jan 21, 2025

📘 Description

To ensure consistency and compatibility across all contracts, we need to standardize the versions of cairo, scarb, and snforge. 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

  • All contracts use the same version of cairo, scarb, and snforge.
  • Any discrepancies in tool versions are resolved and updated to the agreed standard.

📜 Additional Notes

  • Do not apply until the ODBoost begins.
  • Read our contribution guidelines before applying.
  • Leave a comment when finished in this issue with the versions you set for the contracts, to define the .tool-versions file in another issue.
@danielcdz danielcdz added enhancement New feature or request difficult: easy ODBoost This issue will be available ONLY during the ODBoost labels Jan 21, 2025
@danielcdz danielcdz changed the title [FEAT]: Standardize the versions of scarb and snforge used across all contracts. [FEAT]: Standardize the versions of scarb and snforge used across all contracts Jan 21, 2025
@GideonBature
Copy link
Contributor

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.

@SoarinSkySagar
Copy link
Contributor

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

@Nityam573
Copy link

Can I get assigned to this task @danielcdz
I am proficient in cairo projects
View my Profile:
https://app.onlydust.com/u/Nityam573

@Jagadeeshftw
Copy link
Contributor

Proposal to Work on the Issue

I would be delighted to contribute to this issue, as I have extensive experience with Cairo programming and developing decentralized applications on StarkNet.

Estimated Timeline

I 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,
Jagadeesh B

@caxtonacollins
Copy link

I’m interested in this one.

@GideonBature
Copy link
Contributor

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.

@savagechucks
Copy link

savagechucks commented Jan 22, 2025

Hi...
Mind if I try this one?

@ShantelPeters
Copy link
Contributor

Would love to tackle this!

@ryzen-xp
Copy link

I’m interested in this one.

@wheval
Copy link
Contributor

wheval commented Jan 22, 2025

Could I be assigned to this?
ETA is 5 hours

@Wendyalbert
Copy link

Can I take care of this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
difficult: easy enhancement New feature or request ODBoost This issue will be available ONLY during the ODBoost
Projects
None yet
Development

Successfully merging a pull request may close this issue.