Repository navigation
CI: publish to Hex from the hex environment - #125
Merged
Merged
Conversation
HEX_API_KEY moves from repo secrets to a hex environment that only the publish job declares (v* tags only, required reviewer). The precompile and publish checkouts drop the persisted git token, and the workflow defaults to contents: read. Same setup as nyo16/nous (cbf93f2, 1ae48a7).
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.
Moves the Hex key out of repository secrets, as in nyo16/nous (cbf93f2, 1ae48a7).
publishdeclaresenvironment: hexand is the only job that can readHEX_API_KEY. The environment acceptsv*tags only and needs a reviewer, so a tag push pauses before anything reaches Hex until it is approved.precompileandpublishcheckouts usepersist-credentials: false.publish'sgit fetch origin masteris anonymous; the repository is public.checksumkeeps its token because it pusheschecksum.exstomaster.permissions: contents: read. Every job already set its own.docs/release-guide.mddocuments the approval step, and the change is in the v0.8.68 changelog.Before merging (repo settings, needs admin):
hex. Add yourself as a required reviewer. Turn off admin bypass. Under deployment branches and tags choose Selected, then add a tag rulev*.HEX_API_KEYtohex.HEX_API_KEY.Until step 3 is done, a job in the environment without its own secret falls back to the repository secret. So publishing works at every point of the switch.
actionlintis clean apart from SC2155 on the Metal minos check, which is already on master.