Skip to content

Conversation

@mrz1836
Copy link
Contributor

@mrz1836 mrz1836 commented Jan 30, 2026

What Changed

  • Updated actions/cache action from version v5.0.2 (commit 8b402f58fbc84540c8b491a91e594a4576fec3d7) to v5.0.3 (commit cdf6c1fa76f9f475f3d7449005a359c84ca0f306) across multiple workflow files
  • Enhanced error message in fortress-benchmarks.yml to include a title and more detailed explanation: changed from "::error::Benchmark execution failed or contained errors" to "::error title=Benchmark Failed::Benchmark execution failed or contained errors (panic, fatal, or timeout) - see job summary for details"
  • Applied the cache action update to golangci-lint binary cache, golangci-lint build cache, golangci-lint analysis cache, and go-coverage binary cache steps across 9 workflow files

Why It Was Necessary

  • Ensures all workflows use the latest patch version of the cache action, which may include bug fixes and security improvements
  • Improves developer experience by providing more actionable error messages when benchmarks fail, including specific failure types and directing users to the job summary
  • Maintains consistency across all CI/CD workflows by standardizing on a single cache action version

Testing Performed

  • Verify that all workflow files parse correctly and GitHub Actions syntax validation passes
  • Confirm cache restoration and saving operations work as expected with the updated action version
  • Test benchmark failure scenarios to validate the enhanced error message displays correctly with the title and detailed information

Impact / Risk

  • Low Risk: Patch version update to the cache action is expected to be backwards compatible with no breaking changes
  • Improved Observability: Enhanced error message provides better context for debugging benchmark failures, reducing time to resolution
  • No Breaking Changes: The cache action API remains unchanged, all existing cache keys and paths continue to work as before

@mrz1836 mrz1836 self-assigned this Jan 30, 2026
@mrz1836 mrz1836 added automated-sync Automated sync PR, e.g. from a fork or external repo automerge Label to automatically merge pull requests that meet all required conditions chore Simple dependency updates or version bumps labels Jan 30, 2026
@sonarqubecloud
Copy link

@github-actions github-actions bot added size/XL Very large change (>500 lines) update General updates labels Jan 30, 2026
@mrz1836
Copy link
Contributor Author

mrz1836 commented Jan 30, 2026

LGTM!

@mrz1836 mrz1836 merged commit 952a633 into main Jan 30, 2026
44 checks passed
@github-actions github-actions bot deleted the chore/sync-files-bsv-blockchain-spv-20260130-130610-425438b branch January 30, 2026 18:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automated-sync Automated sync PR, e.g. from a fork or external repo automerge Label to automatically merge pull requests that meet all required conditions chore Simple dependency updates or version bumps size/XL Very large change (>500 lines) update General updates

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants