fix: add lowercase repository name output for Docker image tagging

[freinold]

Summary by CodeRabbit

• Chores
  • Updated Docker image tagging to consistently use a lowercase repository name in the release workflow.

[coderabbitai]

Walkthrough

The GitHub Actions workflow was updated to output a lowercase version of the repository name and to use this lowercase value for Docker image tagging. The Docker build-and-push steps now consistently reference the lowercase repository name for image tags. No other logic or public entity declarations were changed.

Changes

File(s)	Change Summary
.github/workflows/docker-release.yml	Added output for lowercase repository name; updated Docker image tags to use the lowercase output.

Suggested labels

enhancement

Poem

A bunny hopped through workflows bright,
Lowercasing names to make things right.
Docker tags now neat and clear,
No more cases to fear!
With every push, the images gleam—
A lowercase hop in the CI stream.
🐇✨

---

🪧 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? Create a ticket on our support page 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 docstrings to generate docstrings for this 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.github/workflows/docker-release.yml (1)

57-57: Prefer bash parameter-expansion over spawning a subshell

tr + subshell is unnecessary and slower. Bash ≥ 4 (the default on Ubuntu runners) supports lowercase conversion natively:

-echo "repo_lowercase=$(echo '${{ github.repository }}' | tr '[:upper:]' '[:lower:]')" >> $GITHUB_OUTPUT
+echo "repo_lowercase=${GITHUB_REPOSITORY,,}" >> "$GITHUB_OUTPUT"

Benefits: fewer processes, simpler quoting, and no risk of accidentally retaining single quotes.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 670a600 and bb5f6b6.

📒 Files selected for processing (1)

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

🔇 Additional comments (1)

.github/workflows/docker-release.yml (1)

74-75: Echo step still references the mixed-case repo – verify consistency

You correctly switched the tags: lines to repo_lowercase, but the later “Image digest” step (80-82) still echoes
ghcr.io/${{ github.repository }}.
If the registry entry is now entirely lowercase, that log line will point to a tag that was never pushed.

Either:

1. Update the echo to use steps.vars.outputs.repo_lowercase, or
2. Keep both variants pushed to GHCR.

Please double-check which behaviour you want.