feat: INFRA-5050 BSC image upgrade v1.5.19

[Spich3000]

BSC image upgrade v1.5.19

INFRA-5050 Bsc v1.5.19 Upgrades across clusters

Summary by CodeRabbit

• Chores
  • Updated the application to use a newer version of the BNB Chain geth binary.

[coderabbitai]

Walkthrough

The Dockerfile has been updated to download version v1.5.19 of the geth_linux binary from the BNB Chain GitHub releases, replacing the previous version v1.5.17. All other aspects of the Dockerfile remain unchanged.

Changes

Cohort / File(s)	Change Summary
Geth Binary Version Update Dockerfile	Updated the geth_linux binary download URL to use version v1.5.19 instead of v1.5.17. No other changes made.

Sequence Diagram(s)

Not applicable: The change is limited to updating a version number in a Dockerfile and does not affect control flow or introduce new features.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• OPS-4819 v1.5.9 #84: Updates the Dockerfile to a newer geth_linux binary, similar to this PR.
• BSC testnet image upgrade v1.5.13 #88: Also updates the Dockerfile for a newer geth_linux version, differing in the specific version.
• BSC image upgrade v1.5.12 #87: Updates the Dockerfile for a geth_linux version bump, similar in scope to this change.

Suggested reviewers

• agrevtsev

Poem

A hop and a jump, a version anew,
Geth hops forward—v1.5.19, how do you do?
Docker’s the burrow, binaries the seed,
Upgrading the chain for rabbits in need.
🐇✨

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches

🧪 Generate unit tests

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

---

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.
  • Explain this complex logic.
  • 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 explain this code block.
• 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 explain its main purpose.
  • @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 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.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this 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.

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (2)

Dockerfile (2)

4-4: Parameterise the version for painless future upgrades

Hard-coding v1.5.19 within the RUN line requires manual editing each bump. Using an ARG BSC_VERSION (see diff above) decouples the version from the command and simplifies CI-driven upgrades.

---

3-3: Shrink image size by cleaning apt cache

The current apt-get invocation leaves /var/lib/apt/lists in the layer (~20 MB). Add rm -rf /var/lib/apt/lists/* (already shown in the diff) or combine with --no-install-recommends to keep the image lean.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 253ed8f and c861540.

📒 Files selected for processing (1)

• Dockerfile (1 hunks)

🧰 Additional context used

🪛 Checkov (3.2.334)

Dockerfile

[HIGH] 4-4: Ensure that certificate validation isn't disabled with wget

(CKV2_DOCKER_3)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: guardrails/scan