Skip to content

fix: use wfctl with runtime verification#4

Merged
intel352 merged 1 commit into
mainfrom
fix/release-runtime-verification
Jun 2, 2026
Merged

fix: use wfctl with runtime verification#4
intel352 merged 1 commit into
mainfrom
fix/release-runtime-verification

Conversation

@intel352
Copy link
Copy Markdown
Contributor

@intel352 intel352 commented Jun 2, 2026

Summary

  • Bump setup-wfctl from v0.63.1 to v0.63.2
  • Use the first wfctl release that exposes plugin verify-capabilities for the existing release truth-check

Verification

  • gh release view v0.63.2 --repo GoCodeAlone/workflow --json tagName,isDraft,isPrerelease,publishedAt,assets
  • wfctl v0.63.2 darwin asset: wfctl plugin verify-capabilities --help
  • ruby -e 'require "yaml"; YAML.load_file(".github/workflows/release.yml"); puts "workflow yaml ok"'\n- git diff --check

Copilot AI review requested due to automatic review settings June 2, 2026 06:23
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the Release GitHub Actions workflow to use wfctl v0.63.2, aligning with the first wfctl release that exposes wfctl plugin verify-capabilities (needed for the existing runtime “truth-check” step in the release pipeline).

Changes:

  • Bump GoCodeAlone/setup-wfctl input version from v0.63.1 to v0.63.2 in the release workflow.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@intel352 intel352 merged commit 84afe5f into main Jun 2, 2026
5 checks passed
@intel352 intel352 deleted the fix/release-runtime-verification branch June 2, 2026 06:27
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.

2 participants