Bump convictional/trigger-workflow-and-wait action to v1.6.5

[manny-yes]

This change addresses the following GitHub Actions warning observed during the image build workflow execution:

Warning: The set-output command is deprecated and will be disabled soon. Please upgrade to using Environment Files.

The warning is emitted by the convictional/trigger-workflow-and-wait@v1.6.1 action, which still uses the deprecated ::set-output command internally. GitHub has announced that set-output will be fully disabled, which would cause this workflow to break in the future.

We bump the action to v1.6.5, which replaces set-output with the supported GITHUB_OUTPUT environment file mechanism, fully complying with GitHub Actions’ current requirements and eliminating the warning.

Relevant notes (explicitly mentioning the fix):

• https://github.com/convictional/trigger-workflow-and-wait/releases/tag/v1.6.5

This is a no-behavior-change update to ensure long-term workflow stability.

Closes https://github.com/onflow/ff-sre-infrastructure/issues/1015.

Summary by CodeRabbit

• Chores
  • Updated build workflow automation action to a newer version for improved stability and maintenance.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

Package	Version	Score	Details
actions/convictional/trigger-workflow-and-wait	1.6.5	🟢 4.4	Details Check Score Reason Code-Review 🟢 6 Found 17/25 approved changesets -- score normalized to 6 Maintained ⚠️ 0 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 Binary-Artifacts 🟢 10 no binaries found in the repo Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions CII-Best-Practices ⚠️ 0 no effort to earn an OpenSSF best practices badge detected Vulnerabilities 🟢 10 0 existing vulnerabilities detected Security-Policy ⚠️ 0 security policy file not detected Packaging ⚠️ -1 packaging workflow not detected Pinned-Dependencies ⚠️ 0 dependency not pinned by hash detected -- score normalized to 0 License 🟢 10 license file detected Fuzzing ⚠️ 0 project is not fuzzed Signed-Releases ⚠️ -1 no releases found Branch-Protection ⚠️ -1 internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md SAST ⚠️ 0 SAST tool is not run on all commits -- score normalized to 0

Scanned Files

• .github/workflows/image_builds.yml

[coderabbitai]

📝 Walkthrough

Walkthrough

A GitHub Actions workflow file is updated to use a newer version of the convictional/trigger-workflow-and-wait action, upgrading from v1.6.1 to v1.6.5 in the secure-build job. No other logic or control flow is altered.

Changes

Cohort / File(s)	Summary
Workflow Dependency Update \.github/workflows/image_builds\.yml	Updated convictional/trigger-workflow-and-wait action version from v1.6.1 to v1.6.5 in the secure-build job

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A hop and a skip through versions we go,
From 1.6.1 to 1.6.5's glow,
The workflow now faster, more sturdy, more bright,
Our GitHub Actions now running just right! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately and specifically describes the main change: bumping a GitHub Actions action version from v1.6.1 to v1.6.5.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

✨ Finishing touches

• 📝 Generate docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!