feat: revert GEM_HOST_API_KEY secret name for semantic-release#26
Merged
Conversation
Reverts the secret name from RUBYGEMS_API_KEY back to GEM_HOST_API_KEY to fix the "No gem API key specified" error in semantic-release CI. The secret GEM_HOST_API_KEY already exists in the repository and was working correctly before the CI workflow update.
RomKadria
force-pushed
the
feature/romka/revert-ci-change
branch
from
4f903b7 to
f9a0e19
Compare
RomKadria
changed the title
github-actions Bot
pushed a commit
that referenced
this pull request
Oct 26, 2025
# [3.16.0](v3.15.1...v3.16.0) (2025-10-26) ### Features * Add support for Rails 8, Ruby 3, and latest GraphQL gem ([#21](#21)) ([10b1dac](10b1dac)) * improve README formatting for installation instructions ([#25](#25)) ([874e497](874e497)) * publish new version ([#24](#24)) ([b4bbd19](b4bbd19)) * revert GEM_HOST_API_KEY secret name for semantic-release ([#26](#26)) ([0fbfc10](0fbfc10))
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The semantic-release CI job was failing with the error:
This error occurred after commit
874e497when the CI workflow was updated.Root Cause
The
semantic-release-rubygemplugin expects the gem API key to be in theGEM_HOST_API_KEYenvironment variable. The workflow was updated to referencesecrets.RUBYGEMS_API_KEYinstead ofsecrets.GEM_HOST_API_KEY, but this secret doesn't exist in the repository.Solution
This PR reverts the secret name from
RUBYGEMS_API_KEYback toGEM_HOST_API_KEYto restore the working configuration from commit6c86b04.Changes
.github/workflows/ci.ymlto usesecrets.GEM_HOST_API_KEYinstead ofsecrets.RUBYGEMS_API_KEYTesting
This configuration was previously working successfully in commit
6c86b04which triggered release585399a.