fix: action image-release

[gitworkflows]

User description

Notes for Reviewers

This PR fixes #

Signed commits

• [*] Yes, I signed my commits.

---

PR Type

enhancement, configuration changes

---

Description

• Updated the Docker image release workflow to use GitHub Container Registry (ghcr.io) instead of quay.io.
• Introduced environment variables for registry and image name to streamline configuration.
• Changed authentication method to use GitHub actor and token for logging into the registry.
• Updated image tag references to reflect the new registry.

---

Changes walkthrough 📝

	Relevant files
Configuration changes	image-release.yaml Update Docker image release workflow to use GitHub Container Registry .github/workflows/image-release.yaml Added environment variables for registry and image name. Changed login registry from quay.io to ghcr.io. Updated image tags to use ghcr.io. Modified authentication to use GitHub actor and token. +13/-7

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

Summary by Sourcery

CI:

• Update the image-release workflow to use GitHub Container Registry (ghcr.io) instead of Quay.io for Docker image management.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request modifies the image release workflow to use GitHub Container Registry (ghcr.io) instead of Quay.io for storing Docker images. It updates the authentication process and image tagging to reflect this change.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Switch from Quay.io to GitHub Container Registry (ghcr.io)	Add environment variables for registry and image name Update login action to use ghcr.io instead of quay.io Change authentication to use GitHub actor and token instead of Quay.io credentials Update image tagging to use ghcr.io instead of quay.io	.github/workflows/image-release.yaml
Update image digest output	Modify the image digest output to reflect the new ghcr.io registry	.github/workflows/image-release.yaml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[codiumai-pr-agent-free]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Configuration Change Verify that the switch from quay.io to ghcr.io is intentional and aligns with the project's infrastructure strategy. Ensure that all necessary permissions and secrets are properly set up in the GitHub repository settings for ghcr.io. Authentication Method Review the new authentication method using GitHub actor and token. Confirm that this approach provides the necessary level of security and access control for the project's needs. Image Tagging Examine the updated image tagging to ensure it follows the project's versioning and tagging conventions. Verify that the new tags using ghcr.io are correct and consistent.

[codiumai-pr-agent-free]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Best practice	Use the built-in GitHub token for improved security and maintainability Consider using the GITHUB_TOKEN secret directly instead of secrets.GITHUB_TOKEN. This is a built-in secret automatically provided by GitHub Actions, ensuring better security and easier maintenance. .github/workflows/image-release.yaml [30-35] - name: Login to ghcr.io uses: docker/login-action@9780b0c442fbb1117ed29e0efdff1e18412f7567 with: registry: ${{ env.REGISTRY }} username: ${{ github.actor }} - password: ${{ secrets.GITHUB_TOKEN }} + password: ${{ github.token }} Apply this suggestion Suggestion importance[1-10]: 8 Why: The suggestion to use the built-in ${{ github.token }} instead of ${{ secrets.GITHUB_TOKEN }} improves security and maintainability by leveraging GitHub's automatic token management, reducing the risk of misconfiguration.	8
Enhancement	Utilize predefined environment variables for image naming to improve consistency and maintainability Consider using the ${{ env.IMAGE_NAME }} variable instead of ${{ github.repository_owner }}/${{ matrix.name }} when specifying the image name. This ensures consistency with the environment variable defined earlier and improves maintainability. .github/workflows/image-release.yaml [53-55] tags: | - ghcr.io/${{ github.repository_owner }}/${{ matrix.name }}:${{ steps.tag.outputs.tag }} - ghcr.io/${{ github.repository_owner }}/${{ matrix.name }}-ci:${{ github.sha }} + ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}:${{ steps.tag.outputs.tag }} + ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}-ci:${{ github.sha }} Apply this suggestion Suggestion importance[1-10]: 7 Why: Using ${{ env.IMAGE_NAME }} instead of hardcoding the repository owner and matrix name enhances consistency and maintainability by aligning with the environment variables defined earlier in the workflow.	7
	Use environment variables for registry and image name in digest output for consistency and maintainability Consider using the ${{ env.REGISTRY }} variable instead of hardcoding ghcr.io when specifying the image digest. This ensures consistency with the environment variable defined earlier and improves maintainability. .github/workflows/image-release.yaml [68] -echo "\`ghcr.io/${{ github.repository_owner }}/${{ matrix.name }}:${{ steps.tag.outputs.tag }}@${{ steps.docker_build_release.outputs.digest }}\`" >> image-digest/${{ matrix.name }}.txt +echo "\`${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}:${{ steps.tag.outputs.tag }}@${{ steps.docker_build_release.outputs.digest }}\`" >> image-digest/${{ matrix.name }}.txt Apply this suggestion Suggestion importance[1-10]: 7 Why: The suggestion to use ${{ env.REGISTRY }} and ${{ env.IMAGE_NAME }} for the image digest output promotes consistency and maintainability by utilizing predefined environment variables, reducing hardcoded values.	7

💡 Need additional feedback ? start a PR chat

[sourcery-ai]

Hey @gitworkflows - I've reviewed your changes - here's some feedback:

Overall Comments:

• Consider updating the PR description to explain the motivation behind switching from Quay.io to GitHub Container Registry. This context would be helpful for reviewers and future contributors.

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}