Add panther_codebase_version to docker image build payload

[pawelirh]

Description

• Added panther_codebase_version argument to payloads while invoking the build docker image action

Requirements

• Code style guidelines followed
• Documentation updated

Tests 🧪

• Robot
• Container
• Simulation

Summary by CodeRabbit

• New Features
  • Enhanced GitHub Actions workflows to include the codebase version in the payload, improving traceability and version management during build processes.

[coderabbitai]

Walkthrough

The changes involve the addition of a new key-value pair, "panther_codebase_version", to the client_payload section in two GitHub Actions workflow YAML files. In the release-candidate.yaml, this field references the environment variable ${{ env.RC_BRANCH_NAME }}, while in the release-project.yaml, it retrieves its value from the GitHub event input version. These modifications enhance the payloads with versioning information relevant to the build process.

Changes

Files	Change Summary
.github/workflows/release-candidate.yaml	Added "panther_codebase_version": "${{ env.RC_BRANCH_NAME }}" in client_payload.
.github/workflows/release-project.yaml	Added "panther_codebase_version": "${{ github.event.inputs.version }}" in client_payload.

---

Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 54a27e1 and 52d9e8d.

Files selected for processing (2)

• .github/workflows/release-candidate.yaml (1 hunks)
• .github/workflows/release-project.yaml (1 hunks)

Additional comments not posted (2)

.github/workflows/release-candidate.yaml (1)

82-82: LGTM!

The addition of the panther_codebase_version field to the client_payload section is a valuable enhancement. It improves the traceability and context for the build process by including the version of the codebase associated with the release candidate.

The value is dynamically set using the RC_BRANCH_NAME environment variable, which is correctly defined at the beginning of the workflow using the inputs provided when triggering the workflow.

The change is consistent with the PR summary and the AI-generated summary.

.github/workflows/release-project.yaml (1)

96-96: LGTM!

The code change is approved for the following reasons:

• It enhances the payload by including versioning information, which could be crucial for tracking the specific version of the codebase being built or deployed.
• It is consistent with the PR summary and the AI-generated summary of changes.
• It is well-integrated within the existing structure and logic of the workflow.
• It does not introduce any correctness, security, or performance issues.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

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>.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @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.

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 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.

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.