pin gosec to v2.23.0 version - try to fix weird behaviour

[wollomatic]

Summary by CodeRabbit

• Chores
  • Updated continuous integration security scanning actions to reference semantic version tags instead of commit hashes across deployment and testing pipelines.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

GitHub Actions workflow files are updated to reference the Gosec security scanner action using a semantic version tag instead of a pinned commit hash. Both release and testing workflows now consistently use the v2.23.0 tag for action resolution.

Changes

Cohort / File(s)	Summary
GitHub Actions Workflow Updates .github/workflows/docker-image-release.yaml, .github/workflows/docker-image-testing.yaml	Updated Gosec security scanner action reference from commit hash to semantic version tag (v2.23.0), changing action resolution method.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• pin gosec to v2.23.0 #94: Updates Gosec action reference in GitHub workflows by changing from commit hash pinning to semantic version tagging.

Poem

🐰 A version tag hops where hashes did dwell,
From commit to v2—a cleaner spell!
Workflows now skip the hash's long dance,
Semantic versions get their bright chance! 📦✨

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch edit-actions

---

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.}