Fix issue with release channel publish action

[mateo-di]

Description

Fix this issue with release channel publish action.

Root Cause

Replicated CLI v0.123.0 (released December 11, 2025) introduced a breaking change in PR #657:

"uses the replicated file to assemble the release, instead of everyone creating staging dirs and moving stuff around"

What changed

When no --yaml, --yaml-dir, or --chart flags are provided, the CLI now expects a .replicated config file in the repo root. The --auto flag alone now triggers this new "config-based flow".

Errors encountered

1. no charts or manifests configured in .replicated config file - Fixed by using --yaml-dir manifests/ instead of --auto
2. No channel "branch_name" - Fixed by adding --ensure-channel to auto-create feature branch channels

References

• Breaking change PR: Use replicated config to create release replicatedhq/replicated#657
• Release v0.123.0: https://github.com/replicatedhq/replicated/releases/tag/v0.123.0

Type of change

• Fix

[gemini-code-assist]

Summary of Changes

Hello @mateo-di, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request resolves a critical issue in the release channel publishing workflow by adjusting the replicated release create command within the GitHub Action. The change ensures that the Replicated CLI correctly identifies and processes the release manifests, thereby fixing the previously encountered publishing failures.

Highlights

• GitHub Action Fix: Corrected an issue within the publish-release GitHub Action that was preventing successful release channel publishing.
• Replicated CLI Command Update: Modified the replicated release create command to explicitly specify the manifest directory using --yaml-dir manifests/ instead of relying on the --auto flag.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request correctly fixes an issue in the release publishing GitHub Action. The change replaces the deprecated and malfunctioning --auto flag with --yaml-dir manifests/, which explicitly specifies the directory containing the KOTS manifests. This resolves the failure in the release creation process. I have one suggestion to further refine the release process by ensuring that development-specific configuration files are not included in the final release package.

[github-actions]

Changes release to Replicated on channel fix_replicated_publish_action! Check the Replicated Dashboard for more details.
If you need to test the changes, you can assign the channel to your customer and download the latest version from the Admin Console.