feat: INFRA-5312 Cronos mainnet image upgrade v1.4.10

[Spich3000]

Cronos mainnet image upgrade v1.4.10

INFRA-5312 Cronos v1.4.10 Upgrades across clusters

Summary by CodeRabbit

• Chores
  • Container image now uses the production Cronos 1.4.10 binary, replacing the previous testnet download.
  • Updated download, extraction, cleanup, and placement steps to match the new artifact.
  • Other build steps and the entrypoint remain unchanged.
  • Users pulling the latest image will run the production binary by default.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Updated the Dockerfile to download and install the Cronos v1.4.10 production Linux x86_64 tarball instead of the testnet variant. Adjusted the wget URL, tar extraction, cleanup, and move commands to reference cronos_1.4.10_Linux_x86_64.tar.gz. No other build steps were modified.

Changes

Cohort / File(s)	Summary of changes
Dockerfile update Dockerfile	Switched Cronos binary source from testnet to production v1.4.10 tarball; updated wget URL, tar extraction, file cleanup, and move paths accordingly.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• feat: INFRA-5312 Cronos testnet image bump v1.4.10 #79 — Similar Dockerfile change to v1.4.10; uses testnet tarball vs this PR’s production tarball.
• Cronos mainnet image upgrade v1.4.7 #72 — Prior switch in Dockerfile from testnet to mainnet archive (different version).
• chore:1.4.9-mainnet #77 — Dockerfile URL and extraction updates around Cronos 1.4.10/1.4.9 variants.

Poem

I nudge the build with gentle paws,
From testnet trails to mainnet laws.
A tarball hops to v1.4.10,
I tidy paths and leap again.
In Docker burrow, bytes align—
Carrots cached, the chain divine. 🥕✨

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 677f093 and 985d909.

⛔ Files ignored due to path filters (1)

• .DS_Store is excluded by !**/.DS_Store

📒 Files selected for processing (1)

• Dockerfile (1 hunks)

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feature/INFRA-5312

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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.