Skip to content

Conversation

rustatian
Copy link
Member

@rustatian rustatian commented Aug 18, 2025

Reason for This PR

  • Pre-release branch

Description of Changes

  • DO NOT MERGE. CI section was updated.

License Acceptance

By submitting this pull request, I confirm that my contribution is made under the terms of the MIT license.

PR Checklist

[Author TODO: Meet these criteria.]
[Reviewer TODO: Verify that these criteria are met. Request changes if not]

  • All commits in this PR are signed (git commit -s).
  • The reason for this PR is clearly provided (issue no. or explanation).
  • The description of changes is clear and encompassing.
  • Any required documentation changes (code and docs) are included in this PR.
  • Any user-facing changes are mentioned in CHANGELOG.md.
  • All added/changed functionality is tested.

Summary by CodeRabbit

  • Chores
    • Simplified container image release tagging: now only publishes the beta tag 2025.2-beta.1 to both Docker Hub and GitHub Container Registry.
    • Previously published tags (e.g., latest, versioned, year-based) are not produced by this workflow run.
    • No changes to product functionality; only distribution tags are affected.
    • Use 2025.2-beta.1 when pulling or upgrading images.

Signed-off-by: Valery Piashchynski <[email protected]>
@rustatian rustatian self-assigned this Aug 18, 2025
Copy link

coderabbitai bot commented Aug 18, 2025

Walkthrough

The release workflow was updated to publish a single Docker image tag (2025.2-beta.1) to both Docker Hub and GitHub Container Registry. Previous multiple tags (latest, version, year variants) were removed. No other steps or logic in the workflow were changed.

Changes

Cohort / File(s) Summary of Changes
Release workflow tagging
/.github/workflows/release.yml
Reduced image tagging to a single tag 2025.2-beta.1 for spiralscout/velox and ghcr.io/roadrunner-server/velox; removed previous multiple tags. No other workflow modifications.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

  • release: v2024.3 #192 — Also updates Docker image tagging in .github/workflows/release.yml (version tags to 2024.3), touching the same logic.
  • release: v2024.2 #169 — Modifies published image tags/versions in the same release workflow.

Suggested labels

C-enhancement

Suggested reviewers

  • wolfy-j

Poem

I nudge the tags with gentle paws,
From many names to one because—
A beta blink, 2025.2 sings,
Two registries, a single spring.
Hop, tag, push—release in sight,
🥕 one neat label, tidy and light.

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch pre-release/beta

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
🪧 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.
    • 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.
  • 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • 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.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
.github/workflows/release.yml (2)

148-153: Avoid hardcoding the Docker tag; use the computed release version output.

You already compute steps.values.outputs.version from the release tag, but the Docker tags are hardcoded to 2025.2-beta.1. This risks drift if the release tag changes or for future pre-releases. Use the computed version for both registries.

Apply this diff to parameterize the image tags:

       tags: |
-            spiralscout/velox:2025.2-beta.1
-            ghcr.io/roadrunner-server/velox:2025.2-beta.1
+            spiralscout/velox:${{ steps.values.outputs.version }}
+            ghcr.io/roadrunner-server/velox:${{ steps.values.outputs.version }}

Also applies to: 165-166


165-166: Confirm intent to publish only a single pre-release tag.

Double-check that not publishing auxiliary tags (e.g., 2025.2-beta as a moving channel, or latest) is intentional for this pre-release. If you want a moving beta channel, we can derive it from the version and add it alongside the exact patch tag.

If desired, I can provide a follow-up patch that computes a beta channel tag (e.g., 2025.2-beta) from ${{ steps.values.outputs.version }} and adds it to the tags: list.

📜 Review details

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

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between eb72d37 and 3a78e17.

📒 Files selected for processing (1)
  • .github/workflows/release.yml (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Build docker image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant