fix(3197): fix youki version command Part of Enhancing Compatibility with runc

[tommady]

Description

Fix Youki version command
This is Part of Enhancing Compatibility with runc

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactoring (no functional changes)
• Performance improvement
• Test updates
• CI/CD related changes
• Other (please describe):

Testing

• Added new unit tests
• Added new integration tests
• Ran existing test suite
• Tested manually (please provide steps)

./target/debug/youki -v                                                                                                                                  
youki version: 0.5.4                                                                                                                                          
commit: 0.5.4-81806f8a9175bbed7cb176cb66f527ff89a187ac    

Related Issues

Fixes #3197

Additional Context

[Copilot]

Pull Request Overview

This PR fixes the youki version command to enhance compatibility with runc by updating the version output format and command-line interface behavior. The changes ensure that youki -v or youki --version produces output in a Moby-compatible format.

• Modified CLI argument parsing to handle version flag separately instead of using a macro
• Updated version output format to match Moby/runc compatibility requirements
• Changed subcommand handling to be optional and display help when no subcommand is provided

Reviewed Changes

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

File	Description
crates/youki/src/main.rs	Updated CLI parsing to add explicit version flag handling and made subcommands optional
crates/youki/src/commands/info.rs	Modified version output format to be Moby-compatible

[Copilot]

Making subcmd optional changes the CLI behavior significantly. Consider if this is the intended breaking change, as users who previously relied on subcommands being required may experience different behavior.

Suggested change

	subcmd: Option<SubCommand>,
	subcmd: SubCommand,

[Copilot]

The error message format ":{e}" has an unusual leading colon. Consider using a more descriptive format like "Failed to print help: {e}".

Suggested change

	.map_err(|e| anyhow::anyhow!(":{e}")),
	.map_err(|e| anyhow::anyhow!("Failed to print help: {e}")),

[utam0k]

@saku3 May I ask you to review this P?

[saku3]

Sure!

[saku3]

Suggested change

	None => Opts::command()
	None => app.print_help().map_err(|e| anyhow::anyhow!(":{e}"))

[saku3]

Thanks. I think this modification looks good.