Skip to content

fix: allow Twingate step to fail without blocking chart release#276

Open
TavoDave wants to merge 1 commit into
masterfrom
fix/twingate-continue-on-error
Open

fix: allow Twingate step to fail without blocking chart release#276
TavoDave wants to merge 1 commit into
masterfrom
fix/twingate-continue-on-error

Conversation

@TavoDave

@TavoDave TavoDave commented May 7, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Adds continue-on-error: true to the Twingate VPN step in release.yml
  • The Release Charts workflow was failing on every merge because Twingate cannot connect in the CI runner, blocking helm/chart-releaser-action from publishing charts
  • cloudarmor v0.1.1 was never published to https://dave-inc.github.io/charts due to this — this fix unblocks it

Test plan

  • Merge this PR → confirm Release Charts CI completes and cloudarmor v0.1.1 appears in the Helm repo

🤖 Generated with Claude Code

continue-on-error: true so chart-releaser runs even if VPN is unavailable in CI

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings May 7, 2026 17:46
@TavoDave TavoDave requested a review from a team as a code owner May 7, 2026 17:46

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

Updates the chart release GitHub Actions workflow to avoid failing the entire release job when the Twingate VPN connection step cannot be established in CI, unblocking helm/chart-releaser-action from publishing charts to the Helm repository.

Changes:

  • Mark the “Connect to Twingate” step as non-blocking by adding continue-on-error: true in .github/workflows/release.yml.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants