Delete .circleci directory

[Dargon789]

Motivation

Solution

PR Checklist

• Added Tests
• Added Documentation
• Breaking changes

Summary by Sourcery

Remove legacy CircleCI configuration from the repository.

Build:

• Delete obsolete CircleCI configuration files and related build definitions.

CI:

• Remove all CircleCI workflows and configuration files under the .circleci directory as they are no longer used.

Chores:

• Clean up repository by dropping unused CI configuration directory.

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Removes legacy CircleCI configuration by deleting all files under the .circleci directory, fully decommissioning CircleCI from the project.

File-Level Changes

Change	Details	Files
Remove obsolete CircleCI CI/CD configuration from the repository.	Delete the primary CircleCI configuration file that defined workflows and jobs. Remove environment- or pipeline-specific CircleCI YAML files for cargo, web3/gamefi, deployment, and v1 flows. Eliminate all remaining CI-related YAMLs under the .circleci directory to prevent CircleCI from running on this repo.	.circleci/config.yml .circleci/cargo.yml .circleci/ci-web3-gamefi.yml .circleci/ci.yml .circleci/ci_cargo.yml .circleci/ci_deploy.yml .circleci/ci_v1.yml .circleci/dev_stage.yml .circleci/web3_defi_gamefi.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[sourcery-ai]

Hey - I've left some high level feedback:

• Since all CircleCI configs are being removed, double‑check there are no remaining references to CircleCI workflows or contexts in other config files (e.g., Makefiles, release scripts, or GitHub Actions) that would now be dead paths.
• Scan the repo for CircleCI status badges or links (e.g., in README or CONTRIBUTING) that may need to be removed or updated to reflect the current CI system.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Since all CircleCI configs are being removed, double‑check there are no remaining references to CircleCI workflows or contexts in other config files (e.g., Makefiles, release scripts, or GitHub Actions) that would now be dead paths.
- Scan the repo for CircleCI status badges or links (e.g., in README or CONTRIBUTING) that may need to be removed or updated to reflect the current CI system.

Fix all in Cursor

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[gemini-code-assist]

Code Review

This pull request removes the entire .circleci directory and all associated configuration files, which results in the immediate cessation of all automated build, test, and deployment workflows. While the deleted files showed signs of being unmaintained or containing syntax errors, this is a high-impact change that leaves the repository without automated validation. This change should only be finalized if a replacement CI system is already active.

I am having trouble creating individual review comments. Click here to see my feedback.

.circleci/config.yml (1-3)

Deleting the .circleci directory and its config.yml file results in the immediate cessation of all CircleCI-managed workflows. Although the files being removed show signs of being unmaintained or containing syntax errors (such as the invalid workflow definitions in dev_stage.yml and the malformed steps in ci_deploy.yml), this is a high-impact change that removes the repository's automated build and test validation. This change is only appropriate if a replacement CI system is already active.