Skip to content

ci: follow-up fixes from install-action migration review [skip changelog] - #527

Merged
avifenesh merged 2 commits into
mainfrom
fix/ci-workflow-followups
Feb 20, 2026
Merged

ci: follow-up fixes from install-action migration review [skip changelog]#527
avifenesh merged 2 commits into
mainfrom
fix/ci-workflow-followups

Conversation

@avifenesh

Copy link
Copy Markdown
Collaborator

Summary

Follow-up fixes identified during review of #526.

  • Accurate version comments: Update all taiki-e/install-action SHA comments from # v2 to # v2.67.30 - the SHA 288875dd resolves to v2.67.30, not the current v2 floating tag
  • Pin cargo-nextest: Pin to @0.9.128 in both test and coverage jobs - was the only unpinned tool, inconsistent with all others
  • cargo-fuzz fallback: Add fallback: cargo-install to skip the cargo-binstall intermediary since cargo-fuzz has no prebuilt binary in the taiki-e manifest
  • iai-callgrind-runner guard: Add if: runner.os == 'Linux' since the taiki-e manifest only supports Linux platforms
  • README accuracy: Update version label from @v2 to @v2.67.30

Test plan

  • CI passes with pinned cargo-nextest version
  • Fuzz workflow installs cargo-fuzz via cargo-install fallback (no cargo-binstall intermediary)
  • benchmark-iai job respects Linux-only guard

- Update taiki-e/install-action SHA comments from '# v2' to '# v2.67.30'
  to accurately reflect the pinned version across all 11 references
- Pin cargo-nextest to @0.9.128 in test and coverage jobs for
  reproducible builds (was unpinned, inconsistent with all other tools)
- Add fallback: cargo-install to cargo-fuzz step in fuzz.yml to bypass
  the cargo-binstall intermediary, matching original install behavior
- Add if: runner.os == 'Linux' guard to iai-callgrind-runner install
  step since the taiki-e manifest only supports Linux platforms
- Update .github/workflows/README.md version label to v2.67.30
Copilot AI review requested due to automatic review settings February 20, 2026 18:55
@gemini-code-assist

Copy link
Copy Markdown
Contributor

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

Follow-up CI workflow adjustments after the taiki-e/install-action migration in #526, aiming to make action-version annotations accurate and tool installs fully pinned/reliable.

Changes:

  • Update taiki-e/install-action inline SHA comments from # v2 to # v2.67.30 across workflows and the workflow README.
  • Pin cargo-nextest to 0.9.128 in CI test and coverage jobs.
  • Adjust tool installation behavior/guards: cargo-fuzz uses fallback: cargo-install, and iai-callgrind-runner install is guarded to Linux.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.

Show a summary per file
File Description
.github/workflows/security.yml Updates install-action version comment for cargo-audit step.
.github/workflows/release.yml Updates install-action version comment for cross install step.
.github/workflows/fuzz.yml Updates install-action version comment; adds fallback: cargo-install for cargo-fuzz.
.github/workflows/docs-site.yml Updates install-action version comment for wasm-pack install step.
.github/workflows/ci.yml Updates install-action version comments; pins cargo-nextest; adds Linux-only guard for iai-callgrind-runner install.
.github/workflows/README.md Updates the install-action reference label to v2.67.30.

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

Comment thread .github/workflows/README.md
@avifenesh
avifenesh merged commit d829bf7 into main Feb 20, 2026
23 checks passed
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