Skip to content

Conversation

suchapalaver
Copy link
Collaborator

This PR updates the CI release workflow to use a RELEASE_TOKEN secret instead of the default GITHUB_TOKEN. The default token cannot trigger workflows that are defined as reusable or that call other actions due to GitHub’s security restrictions. The RELEASE_TOKEN is a personal access token with appropriate scopes, enabling the release workflow to trigger dependent workflows such as Docker image publishing or changelog generation.

@suchapalaver suchapalaver marked this pull request as ready for review June 17, 2025 19:29
@suchapalaver suchapalaver enabled auto-merge (squash) June 17, 2025 20:20
@coveralls
Copy link

coveralls commented Jun 17, 2025

Pull Request Test Coverage Report for Build 15834879720

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.03%) to 72.411%

Totals Coverage Status
Change from base Build 15834855960: 0.03%
Covered Lines: 8811
Relevant Lines: 12168

💛 - Coveralls

@suchapalaver suchapalaver force-pushed the suchapalaver/ci/use-release-token-for-releases branch from e7440bb to feddccd Compare June 23, 2025 18:48
@suchapalaver suchapalaver force-pushed the suchapalaver/ci/use-release-token-for-releases branch from feddccd to ed0c1ee Compare June 23, 2025 20:52
@suchapalaver suchapalaver merged commit 3f65dc7 into main Jun 23, 2025
12 checks passed
@suchapalaver suchapalaver deleted the suchapalaver/ci/use-release-token-for-releases branch June 23, 2025 20:59
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