[deploy] fix docker image version output

[capcom6]

Summary by CodeRabbit

• Chores
  • Updated the deployment pipeline to ensure that version information is handled more reliably between build stages. This adjustment streamlines the workflow, contributing to a more robust and consistent release process that enhances overall update stability for end users.

[coderabbitai]

Walkthrough

This pull request updates the GitHub Actions workflow in .github/workflows/docker-build.yml by shifting the responsibility for propagating the app-version output from the build job to the merge job. The build job’s output declaration for app-version is removed, and the merge job now includes an output declaration for app-version. Additionally, the merge job is configured to depend on the build job, ensuring the proper execution order within the workflow.

Changes

File	Change Summary
.github/workflows/docker-build.yml	- Removed app-version output from the build job. - Added app-version output to the merge job. - Configured merge job to depend on build.

Sequence Diagram(s)

sequenceDiagram
    participant R as Repository/Workflow
    participant B as Build Job
    participant M as Merge Job

    R->>B: Trigger build job
    B-->>M: Build job completes
    M->>M: Generate app-version output via meta step
    M-->>R: Return app-version output

Loading

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 3c9d6ad and a03708a.

📒 Files selected for processing (1)

• .github/workflows/docker-build.yml (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (4)

• GitHub Check: Test
• GitHub Check: E2E
• GitHub Check: lint
• GitHub Check: Analyze (go)

🔇 Additional comments (2)

.github/workflows/docker-build.yml (2)

14-16: Shift Workflow Output Reference to Merge Job

The top-level workflow output for "app-version" now correctly references the merge job output via:

value: ${{ jobs.merge.outputs.app-version }}

This adjustment ensures that the final version information originates from the merge job (which aggregates the metadata) rather than the build job.

---

102-108: Declare Merge Job Output and Set Dependency

In the merge job, adding the needs: [build] dependency guarantees that the build job completes before the merge job runs. Moreover, the outputs section now defines:

outputs:
  app-version: ${{ steps.meta.outputs.version }}

This change correctly propagates the Docker image version from the meta step executed within the merge job. Verify that the docker/metadata-action (used with the id meta) produces the expected version output.

---

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>, please review it.
  • 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 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 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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.