Merge branch 'main' into circleci-project-setup

[Dargon789]

• Because this PR includes a bug fix, relevant tests have been included.
• Because this PR includes a new feature, the change was previously discussed on an Issue or with someone from the team.
• I didn't do anything of this.

---

Summary by Sourcery

Add CircleCI configuration and security policy documentation, and update the Vite dependency version

New Features:

• Configure a CircleCI pipeline for the web3 gamefi project

Enhancements:

• Bump Vite dependency to 5.4.21 in the ignition UI package

Documentation:

• Add SECURITY.md with supported versions and vulnerability reporting guidelines

[vercel]

Deployment failed with the following error:

Resource is limited - try again in 7 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/dargon789-forge?upgradeToPro=build-rate-limit

[sourcery-ai]

Reviewer's Guide

This PR establishes project maintenance and CI infrastructure by adding a CircleCI pipeline, security policy and Dependabot automation, and updates the Vite dependency with a regenerated lockfile.

File-Level Changes

Change	Details	Files
Dependency update	Bump Vite from ^5.4.20 to ^5.4.21 Regenerate pnpm lockfile	packages/hardhat-ignition-ui/package.json pnpm-lock.yaml
CI pipeline setup	Add CircleCI 2.1 pipeline configuration Define custom executor and workflow jobs	.circleci/web3_gamefi.yml
Security policy addition	Add SECURITY.md with supported versions table Document vulnerability reporting process	SECURITY.md
Dependency update automation	Add Dependabot configuration for automated updates	.github/dependabot.yml

Possibly linked issues

• Merge branch 'main-execution' into main (#23) #24: The PR directly implements the dependency updates, CircleCI setup, Dependabot configuration, and security policy described in the issue.
• Create web3_gamefi.yml (#6) #7: The PR adds .circleci/web3_gamefi.yml, implementing the new CircleCI pipeline configuration with executor, job, and workflow as described.

---

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.

[gemini-code-assist]

Summary of Changes

Hello @Dargon789, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on enhancing the project's foundational development and operational infrastructure. It introduces a new CircleCI pipeline for continuous integration, sets up Dependabot for automated dependency updates, and establishes a formal security policy. Additionally, it includes routine minor version bumps for key development dependencies, ensuring the project remains up-to-date and secure.

Highlights

• CI/CD Setup: A new CircleCI configuration file has been added to establish continuous integration for a web3 game project, including a custom Docker executor and a basic setup job.
• Automated Dependency Management: Dependabot has been configured with a new .github/dependabot.yml file to automate weekly dependency updates, enhancing project maintainability.
• Security Policy: A SECURITY.md file has been introduced, outlining supported project versions and providing clear guidelines for reporting security vulnerabilities.
• Dependency Updates: Minor version updates for vite (from 5.4.20 to 5.4.21) and rollup (from 4.52.3 to 4.52.5) have been applied within the hardhat-ignition-ui package and reflected in the pnpm-lock.yaml.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[sourcery-ai]

Hey there - I've reviewed your changes - here's some feedback:

• Rename the CircleCI config file to .circleci/config.yml so CircleCI will pick it up automatically.
• Remove the trailing hyphen from the job name "web3-defi-game-project-" for consistency and to avoid potential naming issues.
• Expand the CI pipeline beyond a placeholder echo to include actual build, lint, and test steps for proper validation.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Rename the CircleCI config file to .circleci/config.yml so CircleCI will pick it up automatically.
- Remove the trailing hyphen from the job name "web3-defi-game-project-" for consistency and to avoid potential naming issues.
- Expand the CI pipeline beyond a placeholder echo to include actual build, lint, and test steps for proper validation.

## Individual Comments

### Comment 1
<location> `SECURITY.md:3-8` </location>
<code_context>
+
+## Supported Versions
+
+Use this section to tell people about which versions of your project are
+currently being supported with security updates.
+
+| Version | Supported          |
</code_context>

<issue_to_address>
**suggestion:** Consider removing template instruction from the Supported Versions section.

The sentence appears to be a template instruction and should be removed if not meant for end users.

```suggestion
## Supported Versions

| Version | Supported          |
```
</issue_to_address>

---

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 introduces several new configuration files for CircleCI and Dependabot, a security policy, and updates the vite dependency. My review focuses on the new configuration files, which appear to be based on templates and contain placeholder or invalid values that need to be corrected.

Specifically:

• The CircleCI configuration has an invalid job name that will cause the pipeline to fail and a hardcoded URL in a comment.
• The Dependabot configuration is missing the required package-ecosystem.
• The SECURITY.md file contains placeholder text and a potentially incorrect version support table.

I've left specific comments with suggestions to fix these issues. Additionally, the pull request title is not very descriptive of all the changes included. Consider updating it to something like 'feat: Add CI, Dependabot, and Security policy' to better reflect the content.