chore: dependabot config

[claytonneal]

Description

Add dependabot config for 1.0.0 branch

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• [] New feature (non-breaking change which adds functionality)
• [] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [] This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Local testing

Checklist:

• My code follows the coding standards of this project
• I have performed a self-review of my code
• I have commented on my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• New and existing integration tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have not added any vulnerable dependencies to my code

Summary by CodeRabbit

• Chores
  • Updated Dependabot configuration to add a new entry for npm package updates targeting the "1.0.0" branch
  • Simplified Dependabot configuration settings

[coderabbitai]

Walkthrough

The changes involve modifications to the Dependabot configuration file located in the .github directory. A new entry for the npm package ecosystem is added with a specific target branch of "1.0.0", while simultaneously removing the previous dependabot.yml file. This appears to be a reconfiguration of the dependency update strategy, potentially adjusting how automated dependency updates are managed across different branches.

Changes

File	Change Summary
.github/dependabot.yml	New configuration added with npm ecosystem, weekly updates, and target branch "1.0.0"
dependabot.yml	Existing configuration file removed

Poem

🐰 Dependabot's dance, a weekly delight,
Branches shifting, updates taking flight
One config gone, another takes its place
Npm packages update with rabbit-like grace
Code maintenance, a technological art! 🔧

Finishing Touches

• 📝 Generate Docstrings

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.github/dependabot.yml (1)

21-28: Consider adding version constraints and staggering updates.

To improve the stability and manageability of dependency updates:

1. Consider adding version constraints to control major version bumps
2. Consider staggering the update schedule between branches to avoid overwhelming CI

Example configuration with versioning and staggered updates:

  - package-ecosystem: "npm"
    directory: "/"
    schedule:
      interval: "weekly"
      day: "monday"
    target-branch: "main"
    versioning-strategy: increase-if-necessary
    pull-request-branch-name:
      separator: "-"
    ignore:
      - dependency-name: "*"
        update-types: ["version-update:semver-major"]

  - package-ecosystem: "npm"
    directory: "/"
    schedule:
      interval: "weekly"
      day: "wednesday"
    target-branch: "1.0.0"
    versioning-strategy: increase-if-necessary
    pull-request-branch-name:
      separator: "-"
    ignore:
      - dependency-name: "*"
        update-types: ["version-update:semver-major"]

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3d0571d and 27e76bd.

📒 Files selected for processing (2)

• .github/dependabot.yml (1 hunks)
• dependabot.yml (0 hunks)

💤 Files with no reviewable changes (1)

• dependabot.yml

⏰ Context from checks skipped due to timeout of 90000ms (12)

• GitHub Check: rpc-proxy / test / test
• GitHub Check: rpc-proxy / docker / docker
• GitHub Check: unit-integration-test / Build & Lint (latest)
• GitHub Check: unit-integration-test-browser / Build & Lint (latest)
• GitHub Check: unit-integration-test / Build & Lint (lts/*)
• GitHub Check: unit-integration-test-browser / Build & Lint (lts/*)
• GitHub Check: unit-integration-test / Build & Lint (18)
• GitHub Check: unit-integration-test-browser / Build & Lint (18)
• GitHub Check: test-apps / Install and test example apps
• GitHub Check: install-build / Build & Lint
• GitHub Check: Execute doc examples
• GitHub Check: Analyze (javascript-typescript)

🔇 Additional comments (2)

.github/dependabot.yml (2)

21-28: 🛠️ Refactor suggestion

Consolidate duplicate npm configurations.

The file contains two nearly identical npm configurations that differ only in the target branch. This could lead to maintenance overhead and potential confusion.

Consider consolidating the npm configurations using the target-branch field:

  - package-ecosystem: "npm"
    directory: "/"
    schedule:
      interval: "weekly"
      day: "wednesday"
    pull-request-branch-name:
      separator: "-"
+   target-branch: "main"
-  - package-ecosystem: "npm"
-    directory: "/"
-    schedule:
-      interval: "weekly"
-      day: "wednesday"
-    target-branch: "1.0.0"
-    pull-request-branch-name:
-      separator: "-"

Likely invalid or redundant comment.

---

21-28: Verify package.json files and current dependencies.

Let's ensure the configuration aligns with the project structure.

✅ Verification successful

NPM configuration aligns with monorepo structure

The root-level npm configuration is appropriate for managing dependencies across all workspaces in the monorepo. The weekly schedule and branch naming convention are well-defined.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify package.json files and current dependencies

# Check for package.json files
echo "Checking for package.json files..."
fd package.json

# Check if we're dealing with a monorepo
echo "Checking for potential workspaces..."
fd package.json -x jq -r '.workspaces // empty'

# Check current dependency ranges
echo "Checking current dependency ranges..."
fd package.json -x jq -r '.dependencies, .devDependencies'

Length of output: 6671

[github-actions]

Test Coverage

Summary

Lines	Statements	Branches	Functions
	99% (4370/4414)	97.55% (1399/1434)	99.01% (906/915)

Title	Tests	Skipped	Failures	Errors	Time
core	836	0 💤	0 ❌	0 🔥	2m 33s ⏱️
network	729	0 💤	0 ❌	0 🔥	5m 0s ⏱️
errors	40	0 💤	0 ❌	0 🔥	18.288s ⏱️
logging	3	0 💤	0 ❌	0 🔥	19.986s ⏱️
hardhat-plugin	19	0 💤	0 ❌	0 🔥	1m 2s ⏱️
aws-kms-adapter	23	0 💤	0 ❌	0 🔥	1m 41s ⏱️
ethers-adapter	5	0 💤	0 ❌	0 🔥	1m 19s ⏱️
rpc-proxy	37	0 💤	0 ❌	0 🔥	1m 7s ⏱️