fix(ci): updates existing ci job to work with new docker publishing.

[tankerkiller125]

Updates the CI/CD pipeline on tagging to also publish binaries automatically using goreleaser by removing the legacy docker publishing references.

Fixes: #24

Summary by CodeRabbit

• Chores
  • Renamed GitHub workflow from "Publish Release" to "Publish Release Binaries" and updated the trigger pattern.
  • Removed steps related to publishing tags and deploying docs in the binaries publish workflow.
  • Modified Docker publish workflow to exclude the Docker image digest signing step except on pull requests.

[coderabbitai]

Walkthrough

Walkthrough

The GitHub workflows have been streamlined. The existing "Publish Release" workflow has been renamed to "Publish Release Binaries," focusing on tags matching the pattern 'v*..'. The workflow related to publishing tags and deploying docs has been removed. Additionally, the Docker image signing step has been simplified by excluding it from pull requests, making these processes more targeted and efficient.

Changes

File Path	Change Summary
.github/workflows/binaries-publish.yaml	Renamed workflow to "Publish Release Binaries" and adjusted trigger to tags 'v*..'. Removed steps for publishing tags and deploying docs.
.github/workflows/docker-publish-rootless.yaml	Removed Docker image digest signing step except on pull requests, along with related environment variable setup.

Poem

Changes flow like binary breeze,
Simplified steps, like gentle seas.
No tags to push, docs to scheme,
Focused code, a streamlined dream.
Docker signs not on PR day,
Efficient paths now lead the way. 🚀

---

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

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between b4f7d21 and 105e04a.

Files selected for processing (3)

• .github/workflows/binaries-publish.yaml (2 hunks)
• .github/workflows/docker-publish-rootless.yaml (1 hunks)
• .github/workflows/docker-publish.yaml (1 hunks)

Files skipped from review due to trivial changes (3)

• .github/workflows/binaries-publish.yaml
• .github/workflows/docker-publish-rootless.yaml
• .github/workflows/docker-publish.yaml