#### Description
As part of the security slam, we've been working to pin digests in
GitHub actions. There's some tools that can run through and pin
everything, but without the notes and comments of every versioned, it
can be difficult to understand what is actually being pinned. Thus, I'm
opting to add the [renovate
helper](https://docs.renovatebot.com/modules/manager/github-actions/#digest-pinning-and-updating)
for this in GitHub actions which should automatically manage version
pinning.
#### Link to tracking issue
Related to
[#86](https://github.com/open-telemetry/sig-security/issues/87#issuecomment-2776660785)
#### Testing
Ran `npx --yes --package renovate -- renovate-config-validator
renovate.json` after updating the config.
The Renovate config in this repository needs migrating. Typically this
is because one or more configuration options you are using have been
renamed.
You don't need to merge this PR right away, because Renovate will
continue to migrate these fields internally each time it runs. But later
some of these fields may be fully deprecated and the migrations removed.
So it's a good idea to merge this migration PR soon.
🔕 **Ignore**: Close this PR and you won't be reminded about config
migration again, but one day your current config may no longer be valid.
❓ Got questions? Does something look wrong to you? Please don't hesitate
to [request help
here](https://redirect.github.com/renovatebot/renovate/discussions).
---
This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/open-telemetry/opentelemetry-collector).
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
The previous change didn't work because opentelemetrybot doesn't have
write permissions to push changes to the renovatebot branch. Reverting
to using the standard github token, and testing triggering CI by
removing the renovatebot label after the change has been pushed.
Signed-off-by: Alex Boten <aboten@lightstep.com>