chore(deps): bump docker workflow version

[MSevey]

Overview

Brings in a patch fix for the docker workflow

[coderabbitai]

📝 Walkthrough

Walkthrough

The changes involve updating the version of a reusable workflow file in the GitHub Actions configuration. Specifically, the version of the reusable_dockerfile_pipeline.yml workflow is changed from v0.4.4 to v0.4.5 in two job definitions within the .github/workflows/docker-build-publish.yml file, affecting jobs that utilize different Dockerfiles.

Changes

File Path	Change Summary
.github/workflows/docker-build-publish.yml	Updated workflow version from v0.4.4 to v0.4.5 in two job definitions for different Dockerfiles.

Possibly related PRs

• feat: build on network tags and manual dispatch #3905: This PR updates the version of the reusable Dockerfile pipeline in the same workflow file and involves changes to job definitions related to the workflow versioning.
• chore: ci regex matching clean up and docker workflow update #3908: This PR modifies the .github/workflows/docker-build-publish.yml file, including updates to job configurations and input parameters relevant to the workflow version changes.

Suggested labels

external

Suggested reviewers

• evan-forbes
• rootulp
• staheri14

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 32fc690 and 18e9306.

📒 Files selected for processing (1)

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

🔇 Additional comments (2)

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

34-34: Consistent workflow version update.

The update to v0.4.5 is consistently applied to both the docker-security-build and docker-txsim-build jobs. This ensures that both Docker builds use the same version of the workflow, which is a good practice for maintaining consistency across the CI/CD pipeline.

---

24-24: Workflow version update looks good.

The update from v0.4.4 to v0.4.5 for the reusable workflow is a minor version change, which is generally a good practice for keeping dependencies up-to-date. This aligns with the PR objective of implementing a patch fix for the docker workflow.

To ensure the update doesn't introduce any unexpected changes, please verify the changelog or release notes for version 0.4.5 of the celestiaorg/.github repository. You can use the following command to check for any recent tags or releases:

✅ Verification successful

Workflow version update verified successfully.

The reusable workflow has been updated to v0.4.5, which is the latest release as of 2024-09-26. This ensures that the Docker build and publish process utilizes the most recent and stable version of the workflow.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for recent tags or releases in the celestiaorg/.github repository

gh repo view celestiaorg/.github --json releases -q '.releases[:5][] | {tagName: .tagName, publishedAt: .publishedAt}'

Length of output: 1246

---

Script:

#!/bin/bash
# Description: Retrieve the latest release information from the celestiaorg/.github repository

gh repo view celestiaorg/.github --json latestRelease -q '{tagName: .latestRelease.tagName, publishedAt: .latestRelease.publishedAt}'

Length of output: 193

---

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:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

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

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.