Added version flag compatibility on the root command

[sanjog-lama]

Description

1. Added version flag compatibility on the root command awsctl --version or awsctl -v. The version will be automatically handled with go releaser.
2. Changed the release workflow automatic PR creation for the changelog reviewer to sarose sir.

Summary by CodeRabbit

• New Features
  • Added version information display to the command-line tool, showing the version as " version ".
• Chores
  • Updated the tool to use version "0.2.0".
  • Updated release workflow with a new pull request reviewer assignment.

[coderabbitai]

Walkthrough

A new versioning mechanism was introduced by adding a Version field to the root command dependencies and wiring it through the initialization of the root command. The version string is now displayed using a custom template when requested, and a global Version variable was added to the main entry point. Additionally, the GitHub Actions workflow for releases was updated to change the assigned reviewer on the release pull request.

Changes

File(s)	Summary of Changes
cmd/root/root.go, main.go	Added Version field and global variable; updated root command initialization to set version and custom version template.
.github/workflows/releaser.yaml	Changed assigned PR reviewer from "mousamdahal" to "sarosejoshi" in release workflow.

Poem

A version hops in, not hiding its name,
"0.2.0" now enters the game.
With a template so neat,
The output’s a treat—
This bunny’s proud of the versioning fame!
🐇✨

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between f94bc10 and f45af40.

📒 Files selected for processing (1)

• .github/workflows/releaser.yaml (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• .github/workflows/releaser.yaml

---

Note

🎁 Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login.

🪧 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.
  • @coderabbitai modularize this function.
• 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.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Join our Discord community for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

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 sequence diagram to generate a sequence diagram of the changes in 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.

[sarosejoshi]

@sanjog-lama Never hardcode versions in source code, Use semantic versioning (major.minor.patch)

I recommend auto version bumping based on commit messages

Few tools will help you

• go-releaser
• semantic-release

[sanjog-lama]

@sarosejoshi sir, I have added that hardcoded version just for testing purpose. That version gets overwritten during build. I have used go-releaser and sematic-release versioning. The code can be found on workflows/releaser.yaml file.
So, should I replace the version with something like dev?