Skip to content

ci: use RELEASE_PAT for tag push to allow release-package-helm to tri…#107

Merged
kupratyu-splunk merged 4 commits into
mainfrom
make_customers_exp_better
Jun 15, 2026
Merged

ci: use RELEASE_PAT for tag push to allow release-package-helm to tri…#107
kupratyu-splunk merged 4 commits into
mainfrom
make_customers_exp_better

Conversation

@kupratyu-splunk

Copy link
Copy Markdown
Collaborator

…gger

GitHub Actions blocks downstream workflow triggers when GITHUB_TOKEN is used to push. Switching checkout to use RELEASE_PAT so the tag push fires the release-package-helm workflow automatically.

Requires RELEASE_PAT secret with repo scope to be set in repository settings.

Description

Related Issues

  • Related to #

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update
  • Refactoring (no functional changes)
  • Performance improvement
  • Test improvement
  • CI/CD improvement
  • Chore (dependency updates, etc.)

Changes Made

Testing Performed

  • Unit tests pass (make test)
  • Linting passes (make lint)
  • Integration tests pass (if applicable)
  • E2E tests pass (if applicable)
  • Manual testing performed

Test Environment

  • Kubernetes Version:
  • Cloud Provider:
  • Deployment Method:

Test Steps

Documentation

  • Updated inline code comments
  • Updated README.md (if adding features)
  • Updated API documentation
  • Updated deployment guides
  • Updated CHANGELOG.md
  • No documentation needed

Checklist

  • My code follows the project's style guidelines
  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published
  • I have updated the Helm chart version (if applicable)
  • I have updated CRD schemas (if applicable)

Breaking Changes

Impact:

Migration Path:

Screenshots/Recordings

Additional Notes

Reviewer Notes

Please pay special attention to:


Commit Message Convention: This PR follows Conventional Commits

…gger

GitHub Actions blocks downstream workflow triggers when GITHUB_TOKEN is used
to push. Switching checkout to use RELEASE_PAT so the tag push fires the
release-package-helm workflow automatically.

Requires RELEASE_PAT secret with repo scope to be set in repository settings.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

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 release-tag creation workflow so that tags are pushed using a PAT instead of GITHUB_TOKEN, allowing the downstream release-package-helm.yml workflow (triggered by tag pushes) to run automatically.

Changes:

  • Configure actions/checkout to authenticate with ${{ secrets.RELEASE_PAT }} in the create-release-tag workflow.

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

Comment thread .github/workflows/create-release-tag.yml
kupratyu-splunk and others added 3 commits June 15, 2026 19:57
Allows manually running the release packaging workflow from the Actions UI,
needed for re-running releases when the tag already exists (e.g. v0.2.0).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Without this check, actions/checkout receives an empty token and fails with
an opaque auth error. The pre-check exits immediately with an actionable
message pointing to where the secret needs to be configured.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@kupratyu-splunk kupratyu-splunk merged commit a945823 into main Jun 15, 2026
10 checks passed
@kupratyu-splunk kupratyu-splunk deleted the make_customers_exp_better branch June 15, 2026 14:37
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.

3 participants