Skip to content

ci: should now be able to publish helm from release workflow#2212

Merged
bosbaber merged 2 commits into
mainfrom
stephan/20260619-publis-helm-on-tag
Jun 19, 2026
Merged

ci: should now be able to publish helm from release workflow#2212
bosbaber merged 2 commits into
mainfrom
stephan/20260619-publis-helm-on-tag

Conversation

@bosbaber

@bosbaber bosbaber commented Jun 19, 2026

Copy link
Copy Markdown
Contributor

Github prevents firing of workflow events if the release is created using the normal GITHUB_TOKEN mechanism. This is an anti-loop protection mechanism which now preveted our helm chart releases from publishing.

This PR attempts to resolve this issue with a workaround calling the helm publishing workflow directly during release process.


Auto generated

This pull request updates the Helm chart publishing workflow to support both manual and automated triggers, and improves flexibility in how release information is passed between workflows. The main changes add support for workflow calls, allow dynamic tag and repository name handling, and integrate the Helm publish workflow into the main release process.

Workflow enhancements and integration:

  • Added support for triggering the helm-publish workflow via workflow_call with required tag_name input and HELM_PUBLISH_TOKEN secret, enabling reuse and manual invocation.
  • Integrated the helm-publish workflow into the main release.yml pipeline, so Helm charts are published automatically after a new release is published. The workflow is triggered with the new release version as the tag.

Parameter and flexibility improvements:

  • Updated the tag selection logic in the Helm publish workflow to use the inputs.tag_name if provided, falling back to github.event.release.tag_name for backward compatibility.
  • Modified the Helm repo index URL to use a fallback value ('testnet') if github.event.repository.name is not set, improving robustness for different invocation contexts.

@bosbaber bosbaber self-assigned this Jun 19, 2026
@github-actions github-actions Bot added the type: ci Changes to CI workflows label Jun 19, 2026
@bosbaber bosbaber requested a review from Copilot June 19, 2026 10:23
@bosbaber bosbaber requested a review from dragosp1011 June 19, 2026 10:25

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the GitHub Actions release pipeline so Helm chart publishing can be invoked as a reusable workflow (via workflow_call) and chained from the Create Release workflow, while keeping existing release: published triggering behavior.

Changes:

  • Added a helm-publish job to release.yml that calls the helm-publish.yml reusable workflow after a successful semantic-release.
  • Enhanced helm-publish.yml with workflow_call inputs/secrets and tag selection logic to support reuse.
  • Added a fallback for the GitHub Pages repo index URL construction.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File Description
.github/workflows/release.yml Calls the Helm publish workflow after semantic-release when a new release is published.
.github/workflows/helm-publish.yml Adds workflow_call support and makes tag/url selection more flexible for different invocation contexts.

Comment thread .github/workflows/helm-publish.yml
Comment thread .github/workflows/release.yml Outdated
@bosbaber bosbaber merged commit 1c6aca6 into main Jun 19, 2026
13 checks passed
@bosbaber bosbaber deleted the stephan/20260619-publis-helm-on-tag branch June 19, 2026 10:39
@github-actions

Copy link
Copy Markdown

🎉 This PR is included in version 0.4.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

released type: ci Changes to CI workflows

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants