feat: revert "update arbitrum dependencies (#1087)"

[cjorge-graphops]

Summary by CodeRabbit

• New Features

  • Enhanced flexibility in the OpenAPI schema by removing restrictive enum definitions for features, allowing a broader range of values.
  • Improved templating capabilities through a new mechanism for managing annotations and labels.

• Bug Fixes

  • Adjusted versioning for arbitrum-classic from 0.2.2-canary.1 to 0.2.1 to ensure consistency across releases.

• Documentation

  • Updated descriptions and URLs in the repositories section to reflect the latest repository structures.

[coderabbitai]

Walkthrough

The pull request introduces significant modifications to the Helmfile configuration for Arbitrum and updates to the OpenAPI schema and Cue schema files. Key changes include the addition of default settings in arbitrum/helmfile.yaml, removal of enum definitions in schema.json, and a version update for arbitrum-classic from 0.2.2-canary.1 to 0.2.1 across multiple files. The changes aim to enhance the maintainability and flexibility of the configurations while preserving the overall structure and integrity of the schemas.

Changes

File	Change Summary
arbitrum/helmfile.yaml	- Added default settings for features and scaling. - Refined logic for default flavor and deployments. - Adjusted release definitions, downgrading arbitrum-classic version from 0.2.2-canary.1 to 0.2.1. - Introduced a mechanism for managing annotations and labels through transformers.
schema.json	- Removed enum definitions for features in namespaces.arbitrum.defaults and namespaces.celo.defaults. - Updated repositories section for consistency in chart descriptions and URLs.
src/schemas/arbitrum.cue	- Updated version for arbitrum-classic from 0.2.2-canary.1 to 0.2.1 in the _template field.

Possibly related PRs

• feat: support hyphen (-) in flavor names #918: The changes in arbitrum/helmfile.yaml regarding the processing of the flavor value are directly related to the modifications in the same file in this PR, which also addresses the handling of the flavor string by replacing hyphens with underscores.
• chore: rollback ReadWriteOncePod chart releases #1039: The rollback of the version for arbitrum-classic from 0.2.2-canary.1 to 0.2.1 in the main PR is relevant to the version updates in the arbitrum/helmfile.yaml file in this PR, which also involves version adjustments for various releases.

Suggested reviewers

• i0n
• calinah

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 02c5cb6 and 62e8c9e.

📒 Files selected for processing (3)

• arbitrum/helmfile.yaml (1 hunks)
• schema.json (0 hunks)
• src/schemas/arbitrum.cue (1 hunks)

💤 Files with no reviewable changes (1)

• schema.json

🔇 Additional comments (4)

src/schemas/arbitrum.cue (1)

122-122: LGTM! Version downgrade aligns with revert intention.

The version downgrade from 0.2.2-canary.1 to 0.2.1 for arbitrum-classic is consistent with the PR's objective to revert dependency updates.

Let's verify if this version is referenced elsewhere in the codebase:

✅ Verification successful

Version downgrade is safe and isolated to arbitrum-classic template

The version change from 0.2.2-canary.1 to 0.2.1 in the arbitrum-classic template is self-contained and doesn't affect other components:

• The version is only referenced in src/schemas/arbitrum.cue for the arbitrum-classic template
• Other services using version 0.2.x (like graph) have their own independent versioning
• The arbitrum-classic chart reference in arbitrum/helmfile.yaml is dynamically configured and doesn't hardcode the version

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for any other references to the arbitrum-classic versions
# to ensure consistency across the codebase

echo "Checking for references to the previous version (0.2.2-canary.1)..."
rg "0\.2\.2-canary\.1"

echo "Checking for references to the new version (0.2.1)..."
rg "0\.2\.1"

echo "Checking for any arbitrum-classic version references..."
rg -A 2 "arbitrum-classic.*version"

Length of output: 1071

---

Script:

#!/bin/bash
# Let's try a different approach to find version references in arbitrum-classic templates
# and any potential dependencies

# Check for arbitrum-classic template definitions
echo "Checking arbitrum-classic template definitions..."
rg -B 2 -A 2 "arbitrum-classic.*_template"

# Look for any references to arbitrum versions in yaml/json files
echo "Checking version references in yaml/json files..."
fd -e yaml -e json -e yml | xargs rg -l "version.*0\.2\."

# Check for any arbitrum package or chart references
echo "Checking arbitrum package/chart references..."
rg -B 2 -A 2 "chart:.*arbitrum"

Length of output: 1972

arbitrum/helmfile.yaml (3)

186-190: Template logic for version selection is robust.

The version fallback mechanism is well-structured:

1. Allows override via custom chartUrl
2. Allows override via custom chartVersion
3. Uses the stable version 0.2.1 as a safe default

🧰 Tools

🪛 yamllint (1.29.0-1)

[error] 190-190: trailing spaces

(trailing-spaces)

---

188-188: Version downgrade from canary to stable looks appropriate.

The change from 0.2.2-canary.1 to 0.2.1 moves away from a pre-release version to a stable version, which is generally safer for production environments.

Let's verify the compatibility with other components:

✅ Verification successful

Based on the search results, I can see that the version 0.2.1 appears in both the schema definition (src/schemas/arbitrum.cue) and the helmfile configuration (arbitrum/helmfile.yaml), suggesting this is a consistent version across the configuration. Let me verify if there are any other arbitrum-related files or version constraints that might be affected.

---

Version downgrade is consistent with schema and configuration

The version change from 0.2.2-canary.1 to 0.2.1 is properly aligned across the codebase:

• The schema in src/schemas/arbitrum.cue defines version 0.2.1
• The helmfile configuration in arbitrum/helmfile.yaml sets version 0.2.1
• This version is specifically for the arbitrum-classic component, while other components (nitro, proxyd) maintain their respective versions

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check version compatibility between arbitrum components
# Look for any version constraints or dependencies between arbitrum-classic and other components

# Check for version references in values files
fd -t f "values.*ya?ml" | xargs rg "0\.2\.(1|2)"

# Check for any dependency declarations
rg -A 5 "dependencies:|requires:" 

Length of output: 23072

---

Script:

#!/bin/bash
# Check for any arbitrum-related files and their version references
fd arbitrum | xargs rg "version:|image:"

# Check for any dependency relationships in arbitrum configs
fd "arbitrum.*ya?ml" | xargs rg "dependencies:|requires:|chart:"

Length of output: 897

---

188-188: Please document the reason for reverting to stable version.

While moving from 0.2.2-canary.1 to stable 0.2.1 is generally safer, it would be helpful to document:

1. What issues were encountered with the canary version?
2. Are there any breaking changes to consider during this downgrade?

Let's check for any related issues or discussions:

---

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 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.