lfglabs-dev / lfglabs-dev/resolver_ccip

Update to last cairo version

Open
#6 23 comments 0 reactions 1 assignee View on GitHub

@saimeunt is already working on this.

Since Dec 7, 2024.

OD Boost Open for contribution
Dominant language
Cairo
Stars
0
Forks
3
PR merge metrics
No merged PRs in 30d

Description

Description 📹

Update the project to the latest version of Cairo.
Ensure compatibility with all components and update dependencies accordingly.

Proposed Actions 🛠️

Here’s a checklist of actions to follow for resolving this issue:

  1. Fork and Create Branch:
    Fork the repository and create a new branch using the issue number:
   git checkout -b fix-[issue-number]
  1. Implement Changes:
  • Update the Cairo version in the project configuration.
  • Modify any breaking changes introduced by the new version of Cairo in the codebase.
  • Update relevant documentation to reflect the changes in the new Cairo version.
  • If any migrations or specific setup steps are required for the update, include them in the project setup documentation.
  1. Run Tests and Commit Changes:
    Make sure your changes don't break existing functionality and commit with a clear message:
   git commit -m "Fix: Update to the latest Cairo version"

Required 📋

To keep our workflow smooth, please make sure you follow these guidelines:

  • Assignment: Don't create a pull request if you weren’t assigned to this issue.
  • Timeframe: Complete the task within 3 business days.
  • Closing the Issue: In your PR description, close the issue by writing Close #[issue_id].
  • Review Process:
    • Once you've submitted your PR, change the label to "ready for review".
    • If changes are requested, address them and then update the label back to "ready for review" once done.
  • Testing: Test your PR locally before pushing, and verify that tests and build are working after pushing.

Thank you for your contribution 🙏

⚠️ WARNING: Failure to follow the requirements above may result in being added to the OnlyDust blacklist, affecting your ability to receive future rewards.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.