Skip to content

Revert SignPath CI until the integration is finished - #400

Merged
thcp merged 1 commit into
mainfrom
revert-signpath-ci-until-ready
Aug 20, 2026
Merged

Revert SignPath CI until the integration is finished#400
thcp merged 1 commit into
mainfrom
revert-signpath-ci-until-ready

Conversation

@thcp

@thcp thcp commented Aug 20, 2026

Copy link
Copy Markdown
Collaborator

SIGNPATH_API_TOKEN and SIGNPATH_ORGANIZATION_ID aren't configured in the repo yet, so a release-triggered run of the sign-exe job added in #394 fails on main today, not just waits on approval. That blocks cutting any release directly from main until SignPath is finished.

This reverts #394 so main goes back to the pre-SignPath, working Windows release path. That's what let v0.11.2 skip the blocker (cut from a branch off the v0.11.1 tag) instead of going through main; with this reverted, main itself is unblocked for normal direct-to-main work and future patch releases.

Re-apply when picking SignPath back up: git revert this commit (or cherry-pick 7eba634 again) once the secrets/variable are set and the SignPath project/policy is approved, then cut v0.12.0.

Test plan

@thcp
thcp merged commit 81a96cf into main Aug 20, 2026
10 checks passed
@thcp
thcp deleted the revert-signpath-ci-until-ready branch August 21, 2026 22:24
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.

1 participant