Fix image tagging in CI

[nbenmoody]

This should be a quick fix to the way CI patches the image version in the kubernetes manifests, to fix the empty string that was showing up there.

Summary by CodeRabbit

• Chores
  • Updated workflow dependencies for improved process clarity.
  • Added version logging during deployment to enhance transparency.

[coderabbitai]

Walkthrough

The workflow configuration file for publishing and releasing was updated. The merge_to_release job now depends on both the push_to_registry and get_version jobs. Additionally, the job includes new echo commands to log the image tag version before updating deployment manifest fields with yq. No changes were made to exported or public entity declarations.

Changes

File(s)	Change Summary
.github/workflows/publish-and-release.yml	Updated merge_to_release job to depend on push_to_registry and get_version; added echo statements to log image tag version before patching deployment manifests.

Poem

A bunny hops through workflow code,
Logging versions as they go,
Dependencies now clear and bright,
Echoes ring in YAML light.
With every patch and tidy line,
Release day comes—how fine, how fine!

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)

• We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.

---

📜 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 7395935 and 2fcdc4a.

📒 Files selected for processing (1)

• .github/workflows/publish-and-release.yml (2 hunks)

🔇 Additional comments (2)

.github/workflows/publish-and-release.yml (2)

98-98: Correct dependency update for job sequencing.

Changing needs to include both push_to_registry and get_version ensures that the version output is always available before patching manifests. This is a necessary and correct fix for the CI workflow.

---

121-122: Helpful logging for version patching.

Adding echo statements to log the image tag version before patching manifests improves traceability and debugging in the CI process. This is a good practice for visibility.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
• @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.