fix: incorrect ironclaw version in staging

[think-in-universe]

Summary

• Aligns the package version metadata with the latest release by updating ironclaw from 0.25.0 to 0.26.0 in both Cargo.toml and Cargo.lock.
• Fixes version mismatch that caused downstream consumers (for example ironclaw-dind CI summary/version detection) to report stale 0.25.0.
• Keeps release metadata consistent across manifests so builds and --version reporting match the intended release line.
• Fixes the ironclaw version in ironclaw-dind build, e.g. https://github.com/nearai/ironclaw-dind/actions/runs/24979607787

Change Type

• Bug fix
• New feature
• Refactor
• Documentation
• CI/Infrastructure
• Security
• Dependencies

Linked Issue

Related: version mismatch between released IronClaw line and workspace manifest version (no formal issue linked).

Validation

• cargo fmt --all -- --check
• cargo clippy --all --benches --tests --examples --all-features -- -D warnings
• cargo build
• Relevant tests pass: N/A (metadata/version-only change)
• cargo test --features integration if database-backed or integration behavior changed
• Manual testing: verified diff updates version = "0.26.0" in both Cargo.toml and Cargo.lock
• If a coding agent was used and supports it, review-pr or pr-shepherd --fix was run before requesting review

Security Impact

None.

Database Impact

None.

Blast Radius

Low. Touches only release/version metadata for the root ironclaw package. Main risk is release automation or version-gating logic that depends on this value (intended behavior).

Rollback Plan

Revert this commit to restore 0.25.0 in Cargo.toml and Cargo.lock if any downstream release process unexpectedly depends on the previous value.

Review Follow-Through

Please confirm this aligns with the expected release source of truth (v0.26.0) and that downstream image/version pipelines should consume this updated manifest version.

---

Review track: A

[Copilot]

Pull request overview

Updates the workspace’s root ironclaw package version metadata to match the intended release line so downstream consumers (e.g., image/version detection in ironclaw-dind) report the correct version.

Changes:

• Bump root package version from 0.25.0 → 0.26.0 in Cargo.toml.
• Reflect the root package version bump in Cargo.lock.

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated 1 comment.

File	Description
Cargo.toml	Updates the root package version to 0.26.0 for consistent build/--version reporting.
Cargo.lock	Updates the lockfile entry for the root ironclaw package to 0.26.0.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

PR description says this aligns to the latest release line (v0.26.0), but the repo changelog currently only lists releases up through 0.25.0. If 0.26.0 is intended, consider updating CHANGELOG/release notes (or clarifying in the PR description why the changelog is intentionally unchanged) to avoid conflicting release metadata for downstream consumers.

[think-in-universe]

@serrrfirat @henrypark133 Can we make sure the version in staging branch is always up-to-date? Or maybe we can get rid of staging branch completely if we switch the default branch to main.

[gemini-code-assist]

Code Review

This pull request updates the ironclaw package version from 0.25.0 to 0.26.0 in both Cargo.toml and Cargo.lock. Feedback was provided regarding the missing update to the CHANGELOG.md file, which should be updated to include a new section for this version to maintain an accurate release history.

[gemini-code-assist]

The package version has been updated to 0.26.0, but the CHANGELOG.md does not contain an entry for this version. It is important to update the changelog to reflect the new version and move any relevant changes from the [Unreleased] section to a new [0.26.0] section to maintain a clear and accurate release history.