chore(deps): pin grafana/k6 action to fb30dcf

[renovate-sh-app]

This PR contains the following updates:

Package	Type	Update	Change
grafana/k6	action	pinDigest	→ fb30dcf

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

Need help?

You can ask for more help in the following Slack channel: #proj-renovate-self-hosted. In that channel you can also find ADR and FAQ docs in the Resources section.

[cla-assistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[joanlopez]

@mstoykov was your suggestion to not pin this? I agree that it might help reducing the noise, although it's algo a good example of the type of Renovate PR that could be easily automerged - I guess in practice is more or less the same but perhaps slightly better as it leave the reference of what concrete build is used when? 🤔

Do you know if there's any way to configure such thing in Renovate? cc/ @codebien

[codebien]

Do you know if there's any way to configure such thing in Renovate? cc/ @codebien

@joanlopez yes, it should be possible to have a rule for matchPackageNames where the path is under grafana then set automerge equals to true.

https://docs.renovatebot.com/key-concepts/automerge/

[oleiade]

LGTM