chore: bump thornode image: update to 1.0.26-23761879 (main)

[tiljrd]

User description

Automated: bump image to tiljordan/thornode-forking:1.0.26-23761879 on base main. Automated weekly bump.

---

PR Type

Other

---

Description

• Update thornode-forking image from 1.0.25 to 1.0.26

• Bump applied across configuration files and examples

• Update default image reference in toolchain Dockerfile

---

Diagram Walkthrough

flowchart LR
  A["thornode-forking<br/>1.0.25-23761879"] -- "upgrade to" --> B["thornode-forking<br/>1.0.26-23761879"]
  B --> C["Configuration Files"]
  B --> D["Example Files"]
  B --> E["Dockerfile"]

Loading

File Walkthrough

	Relevant files
Configuration changes	README.md Update README documentation image versions                              README.md Update forking image reference from 1.0.25 to 1.0.26 Update participants image reference from 1.0.25 to 1.0.26 +2/-2      cli-with-network.yaml Update CLI example image version                                                  examples/cli-with-network.yaml Update participant image from 1.0.25 to 1.0.26 +1/-1      forking-1.0.10.yaml Update forking example image version                                          examples/forking-1.0.10.yaml Update participant image from 1.0.25 to 1.0.26 +1/-1      forking-genesis.yaml Update forking genesis example images                                        examples/forking-genesis.yaml Update forking image from 1.0.25 to 1.0.26 Update participant image from 1.0.25 to 1.0.26 +2/-2      faucet_launcher.star Update faucet launcher image version                                          src/faucet/faucet_launcher.star Update faucet_image variable from 1.0.25 to 1.0.26 +1/-1      single_node_launcher.star Update single node launcher default image                                src/network_launcher/single_node_launcher.star Update default forking_image from 1.0.25 to 1.0.26 +1/-1      thorchain_defaults.json Update thorchain defaults image references                              src/package_io/thorchain_defaults.json Update participant image from 1.0.25 to 1.0.26 Update forking image from 1.0.25 to 1.0.26 +2/-2
Dependencies	Dockerfile Update toolchain CLI base image version                                    src/toolchain-cli/Dockerfile Update base image FROM clause from 1.0.25 to 1.0.26 +1/-1

---

Summary by CodeRabbit

• Chores
  • Updated Thornode forking component image version across configuration files and Docker setup for improved compatibility and service stability.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

This PR bumps the thornode-forking Docker image version from 1.0.25-23761879 to 1.0.26-23761879 across documentation, configuration examples, package defaults, launcher scripts, and containerization files. No logic or control flow changes are introduced.

Changes

Cohort / File(s)	Summary
YAML Configuration & Examples README.md, examples/cli-with-network.yaml, examples/forking-1.0.10.yaml, examples/forking-genesis.yaml	Updated forking image tag from 1.0.25-23761879 to 1.0.26-23761879 in forking block references and participant configurations.
Launcher Scripts src/faucet/faucet_launcher.star, src/network_launcher/single_node_launcher.star	Bumped default thornode-forking image tag in faucet service and single node launcher defaults.
Package Defaults src/package_io/thorchain_defaults.json	Updated image references in participants[0].image and forking.image fields to 1.0.26-23761879.
Docker Configuration src/toolchain-cli/Dockerfile	Updated base image tag from 1.0.25-23761879 to 1.0.26-23761879.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

This consists of homogeneous, repetitive version bump changes across multiple files following the same pattern. The changes are purely configuration-level updates with no functional or logic modifications.

Possibly related PRs

• #79: Subsequent thornode-forking image version bump (1.0.22→1.0.25) in the same set of files.
• #73: Identical change pattern applying the same image tag update across README, examples, launchers, and defaults.
• #56: Same code-level change pattern bumping thornode-forking image references across all configuration and source files.

Suggested labels

review-effort-1/5

Poem

🐰 A whisker-twitch, a version call,
From 25 to 26, we rise so tall!
Files align in harmony's way,
Thornode updates see the light of day! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically identifies the main change: bumping the thornode Docker image to version 1.0.26-23761879. All file modifications involve updating this single image tag across multiple configuration and source files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch bump-thornode-1.0.26-23761879-main

---

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 414ef54 and 4798583.

📒 Files selected for processing (8)

• README.md (1 hunks)
• examples/cli-with-network.yaml (1 hunks)
• examples/forking-1.0.10.yaml (1 hunks)
• examples/forking-genesis.yaml (1 hunks)
• src/faucet/faucet_launcher.star (1 hunks)
• src/network_launcher/single_node_launcher.star (1 hunks)
• src/package_io/thorchain_defaults.json (2 hunks)
• src/toolchain-cli/Dockerfile (1 hunks)

🔇 Additional comments (8)

examples/cli-with-network.yaml (1)

10-10: LGTM! Image version bump is consistent.

The participant image reference has been correctly updated to the new version.

src/faucet/faucet_launcher.star (1)

33-33: LGTM! Faucet image version updated correctly.

The faucet service will use the updated thornode-forking image.

examples/forking-1.0.10.yaml (1)

5-5: LGTM! Forking example configuration updated.

The participant image in the forking configuration is now using the new version.

src/toolchain-cli/Dockerfile (1)

1-1: LGTM! Dockerfile base image updated.

The CLI toolchain Dockerfile now uses the updated thornode-forking base image.

examples/forking-genesis.yaml (1)

10-10: LGTM! Forking and participant images updated consistently.

Both the forking configuration and participant references now use the new image version.

Also applies to: 16-16

README.md (1)

264-264: LGTM! Documentation examples updated.

The README examples now reference the new image version, keeping documentation in sync with the actual configuration.

Also applies to: 267-267

src/network_launcher/single_node_launcher.star (1)

12-12: LGTM! Default forking image updated.

The fallback default for the forking image has been updated, ensuring consistency when users don't explicitly specify an image version in their configuration.

src/package_io/thorchain_defaults.json (1)

57-57: Verify the new image tiljordan/thornode-forking:1.0.26-23761879 is accessible in the registry.

Both the participant (line 57) and forking (line 71) image references have been updated consistently. Since this is an automated bump, ensure the new image has been successfully built and pushed to the registry before merging.

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[qodo-code-review]

You are nearing your monthly Qodo Merge usage quota. For more information, please visit here.

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
⚪	Unpinned container image Description: The PR updates multiple places to pull the Docker image tiljordan/thornode-forking:1.0.26-23761879 by tag (not a pinned digest), which creates a supply-chain risk because tags can be overwritten and the build/runtime could silently consume different (potentially malicious) image content; consider pinning by digest (e.g., @sha256:...) and/or using a trusted registry/signature verification. Dockerfile [1-1] Referred Code FROM tiljordan/thornode-forking:1.0.26-23761879
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

You are nearing your monthly Qodo Merge usage quota. For more information, please visit here.

PR Code Suggestions ✨

No code suggestions found for the PR.