Repository navigation
ci: streamline releases and agent validation - #15
Merged
Merged
Conversation
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.
Summary
Release jobs queue twice for macOS runners. Reuse one runner for building, publishing, and Homebrew validation; keep the tap token in a separate job.
Keep PR CI unchanged. Document waiting for required merge checks, local desktop validation for window behavior changes, and releasing only when requested.
Evidence
After: Two jobs with one macOS allocation; intermediate release artifact transfers removed. Hosted release timing remains unmeasured.
CFLAGS='-O2 -Werror' make all test.Merge Danger
Door: two-way
The workflow can be reverted. No release tag is created by this PR.
Blast Radius: releases
The macOS job now holds release and attestation permissions. Tap credentials remain isolated, and tap sync requires successful Homebrew validation. As before, the release becomes public before installation testing; full release execution has not been tested locally.