Skip Hex API key validation in CI workflow#6
Merged
lupodevelop merged 1 commit intomainfrom Nov 16, 2025
Merged
Conversation
Remove the HTTP check against the Hex API for the HEX_API_KEY in the publish-gleam workflow. Now, the workflow only checks for the presence of the secret, avoiding issues with unexpected API responses in some environments and reducing the risk of leaking sensitive information.
There was a problem hiding this comment.
Pull Request Overview
This PR simplifies the HEX_API_KEY validation in the publish-gleam workflow by removing the HTTP API check and only verifying the secret's presence. This change addresses issues with unexpected API responses (404s) in some environments and reduces the risk of information leakage.
- Removes the HTTP call to Hex API
/api/meendpoint for key validation - Retains the check for secret presence to prevent accidental publishing without credentials
- Adds clear comments explaining the rationale for skipping API validation
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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
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.
Remove the HTTP check against the Hex API for the HEX_API_KEY in the publish-gleam workflow. Now, the workflow only checks for the presence of the secret, avoiding issues with unexpected API responses in some environments and reducing the risk of leaking sensitive information.