Use immutable github releases

Following the trivy scanner compromise, it has become relevant to ask that any GitHub Actions used across the industry switch to using immutable GitHub Actions releases to guard against supply chain compromises. See: https://www.aquasec.com/blog/trivy-supply-chain-attack-what-you-need-to-know/.

Can you switch this repository to using immutable releases, and stop publishing "v1" on a regular basis to reduce the impact of a potential supply chain compromise?

Inspect the repository's GitHub Actions workflow and release or publishing configuration first; the issue does not name specific files. Verify how action references are currently pinned and how the v1 tag is published, then confirm that releases use immutable references and no longer update v1 regularly.

Written by the indexing model from the issue text.