grafana/alloy (github.com/grafana/alloy/operations/alloy-mixin)
### [`v1.1.0`](https://togithub.com/grafana/alloy/blob/HEAD/CHANGELOG.md#v110)
[Compare Source](https://togithub.com/grafana/alloy/compare/v1.0.0...v1.1.0)
##### Features
- (*Public preview*) Add support for setting GOMEMLIMIT based on cgroup setting. ([@mattdurham](https://togithub.com/mattdurham))
- (*Public preview*) Introduce BoringCrypto Docker images.
The BoringCrypto image is tagged with the `-boringcrypto` suffix and
is only available on AMD64 and ARM64 Linux containers.
([@rfratto](https://togithub.com/rfratto), [@mattdurham](https://togithub.com/mattdurham))
- (*Public preview*) Introduce `boringcrypto` release assets. BoringCrypto
builds are publshed for Linux on AMD64 and ARM64 platforms. ([@rfratto](https://togithub.com/rfratto),
[@mattdurham](https://togithub.com/mattdurham))
- `otelcol.exporter.loadbalancing`: Add a new `aws_cloud_map` resolver. ([@ptodev](https://togithub.com/ptodev))
- Introduce a `otelcol.receiver.file_stats` component from the upstream
OpenTelemetry `filestatsreceiver` component. ([@rfratto](https://togithub.com/rfratto))
##### Enhancements
- Update `prometheus.exporter.kafka` with the following functionalities ([@wildum](https://togithub.com/wildum)):
- GSSAPI config
- enable/disable PA_FX_FAST
- set a TLS server name
- show the offset/lag for all consumer group or only the connected ones
- set the minimum number of topics to monitor
- enable/disable auto-creation of requested topics if they don't already exist
- regex to exclude topics / groups
- added metric kafka_broker_info
- In `prometheus.exporter.kafka`, the interpolation table used to compute estimated lag metrics is now pruned
on `metadata_refresh_interval` instead of `prune_interval_seconds`. ([@wildum](https://togithub.com/wildum))
- Don't restart tailers in `loki.source.kubernetes` component by above-average
time deltas if K8s version is >= 1.29.1 ([@hainenber](https://togithub.com/hainenber))
- In `mimir.rules.kubernetes`, add support for running in a cluster of Alloy instances
by electing a single instance as the leader for the `mimir.rules.kubernetes` component
to avoid conflicts when making calls to the Mimir API. ([@56quarters](https://togithub.com/56quarters))
##### Bugfixes
- Fixed issue with defaults for Beyla component not being applied correctly. (marctc)
- Fix an issue on Windows where uninstalling Alloy did not remove it from the
Add/Remove programs list. ([@rfratto](https://togithub.com/rfratto))
- Fixed issue where text labels displayed outside of component node's boundary. ([@hainenber](https://togithub.com/hainenber))
- Fix a bug where a topic was claimed by the wrong consumer type in `otelcol.receiver.kafka`. ([@wildum](https://togithub.com/wildum))
- Fix an issue where nested import.git config blocks could conflict if they had the same labels. ([@wildum](https://togithub.com/wildum))
- In `mimir.rules.kubernetes`, fix an issue where unrecoverable errors from the Mimir API were retried. ([@56quarters](https://togithub.com/56quarters))
- Fix an issue where `faro.receiver`'s `extra_log_labels` with empty value
don't map existing value in log line. ([@hainenber](https://togithub.com/hainenber))
- Fix an issue where `prometheus.remote_write` only queued data for sending
every 15 seconds instead of as soon as data was written to the WAL.
([@rfratto](https://togithub.com/rfratto))
- Imported code using `slog` logging will now not panic and replay correctly when logged before the logging
config block is initialized. ([@mattdurham](https://togithub.com/mattdurham))
- Fix a bug where custom components would not shadow the stdlib. If you have a module whose name conflicts with an stdlib function
and if you use this exact function in your config, then you will need to rename your module. ([@wildum](https://togithub.com/wildum))
- Fix an issue where `loki.source.docker` stops collecting logs after a container restart. ([@wildum](https://togithub.com/wildum))
- Upgrading `pyroscope/ebpf` from 0.4.6 to 0.4.7 ([@korniltsev](https://togithub.com/korniltsev)):
- detect libc version properly when libc file name is libc-2.31.so and not libc.so.6
- treat elf files with short build id (8 bytes) properly
##### Other changes
- Update `alloy-mixin` to use more specific alert group names (for example,
`alloy_clustering` instead of `clustering`) to avoid collision with installs
of `agent-flow-mixin`. ([@rfratto](https://togithub.com/rfratto))
- Upgrade Beyla from v1.4.1 to v1.5.1. ([@marctc](https://togithub.com/marctc))
- Add a description to Alloy DEB and RPM packages. ([@rfratto](https://togithub.com/rfratto))
- Allow `pyroscope.scrape` to scrape `alloy.internal:12345`. ([@hainenber](https://togithub.com/hainenber))
- The latest Windows Docker image is now pushed as `nanoserver-1809` instead of
`latest-nanoserver-1809`. The old tag will no longer be updated, and will be
removed in a future release. ([@rfratto](https://togithub.com/rfratto))
- The log level of `finished node evaluation` log lines has been decreased to
'debug'. ([@tpaschalis](https://togithub.com/tpaschalis))
- Update post-installation scripts for DEB/RPM packages to ensure
`/var/lib/alloy` exists before configuring its permissions and ownership.
([@rfratto](https://togithub.com/rfratto))
- Remove setcap for `cap_net_bind_service` to allow alloy to run in restricted environments.
Modern container runtimes allow binding to unprivileged ports as non-root. ([@BlackDex](https://togithub.com/BlackDex))
- Upgrading from OpenTelemetry v0.96.0 to v0.99.0.
- `otelcol.processor.batch`: Prevent starting unnecessary goroutines.
[https://github.com/open-telemetry/opentelemetry-collector/issues/9739](https://togithub.com/open-telemetry/opentelemetry-collector/issues/9739)ues/9739
- `otelcol.exporter.otlp`: Checks for port in the config validation for the otlpexporter.
[https://github.com/open-telemetry/opentelemetry-collector/issues/9505](https://togithub.com/open-telemetry/opentelemetry-collector/issues/9505)ues/9505
- `otelcol.receiver.otlp`: Fix bug where the otlp receiver did not properly respond
with a retryable error code when possible fo[https://github.com/open-telemetry/opentelemetry-collector/pull/9357](https://togithub.com/open-telemetry/opentelemetry-collector/pull/9357)lector/pull/9357
- `otelcol.receiver.vcenter`: Fixed the resource attribute model to more accurately support multi-cluster deployments.
[https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/30879](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/30879)es/30879
For more information on impacts p[https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/31113](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/pull/31113)ector-contrib/pull/31113
The main impact is that `vcenter.resource_pool.name`, `vcenter.resource_pool.inventory_path`,
and `vcenter.cluster.name` are reported with more accuracy on VM metrics.
- `otelcol.receiver.vcenter`: Remove the `vcenter.cluster.name` resource attribute from Host resources if the Host is standalone (no cluster).
[https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/32548](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32548)es/32548
- `otelcol.receiver.vcenter`: Changes process for collecting VMs & VM perf metrics to be more efficient (one call now for all VMs).
[https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/31837](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31837)es/31837
- `otelcol.connector.servicegraph`: Added a new `database_name_attribute` config argument to allow users to
specify a custom attribute name for identifying the database name in span attr[https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/30726](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/pull/30726)ntrib/pull/30726
- `otelcol.connector.servicegraph`: Fix 'failed to find dimensions for key' error from race condition in metrics cleanup.
[https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/31701](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31701)es/31701
- `otelcol.connector.spanmetrics`: Add `metrics_expiration` option to enable expiration of metrics if spans are not received within a certain time frame.
By default, the expiration is disabled (set[https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/30559](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/30559)rib/issues/30559
- `otelcol.connector.spanmetrics`: Change default value of `metrics_flush_interval` from 15s to 60s.
[https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/31776](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31776)es/31776
- `otelcol.connector.spanmetrics`: Discard counter span metric exemplars after each flush interval to avoid unbounded memory growth.
This aligns exemplar discarding for counter span metrics with the existing logic for histogram span m[https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/31683](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31683)rib/issues/31683
- `otelcol.exporter.loadbalancing`: Fix panic when a sub-exporter is shut down while still handling requests.
[https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/31410](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31410)es/31410
- `otelcol.exporter.loadbalancing`: Fix memory leaks on shutdown.
[https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/31050](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/pull/31050)ll/31050
- `otelcol.exporter.loadbalancing`: Support the timeout period of k8s resolver list watch can be configured.
[https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/31757](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31757)es/31757
- `otelcol.processor.transform`: Change metric unit for metrics extracted with `extract_count_metric()` to be the default unit (`1`).
[https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/31575](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31575)es/31575
- `otelcol.receiver.opencensus`: Refactor the receiver to pass lifecycle tests and avoid leaking gRPC connections.
[https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/31643](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31643)es/31643
- `otelcol.extension.jaeger_remote_sampling`: Fix leaking goroutine on shutdown.
[https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/31157](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31157)es/31157
- `otelcol.receiver.kafka`: Fix panic on shutdown.
[https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/31926](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31926)es/31926
- `otelcol.processor.resourcedetection`: Only attempt to detect Kubernetes node resource attributes when they're enabled.
[https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/31941](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31941)es/31941
- `otelcol.processor.resourcedetection`: Fix memory leak on AKS.
[https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/32574](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/pull/32574)ll/32574
- `otelcol.processor.resourcedetection`: Update to ec2 scraper so that core attributes are not dropped if describeTags returns an error (likely due to permissions).
[https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/30672](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/pull/30672)ll/30672
- Use Go 1.22.3 for builds. ([@kminehart](https://togithub.com/kminehart))
Configuration
📅 Schedule: 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 becomes conflicted, 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
This PR has been generated by Mend Renovate. View repository job log here.
This PR contains the following updates:
v1.0.0->v1.1.0Release Notes
grafana/alloy (github.com/grafana/alloy/operations/alloy-mixin)
### [`v1.1.0`](https://togithub.com/grafana/alloy/blob/HEAD/CHANGELOG.md#v110) [Compare Source](https://togithub.com/grafana/alloy/compare/v1.0.0...v1.1.0) ##### Features - (*Public preview*) Add support for setting GOMEMLIMIT based on cgroup setting. ([@mattdurham](https://togithub.com/mattdurham)) - (*Public preview*) Introduce BoringCrypto Docker images. The BoringCrypto image is tagged with the `-boringcrypto` suffix and is only available on AMD64 and ARM64 Linux containers. ([@rfratto](https://togithub.com/rfratto), [@mattdurham](https://togithub.com/mattdurham)) - (*Public preview*) Introduce `boringcrypto` release assets. BoringCrypto builds are publshed for Linux on AMD64 and ARM64 platforms. ([@rfratto](https://togithub.com/rfratto), [@mattdurham](https://togithub.com/mattdurham)) - `otelcol.exporter.loadbalancing`: Add a new `aws_cloud_map` resolver. ([@ptodev](https://togithub.com/ptodev)) - Introduce a `otelcol.receiver.file_stats` component from the upstream OpenTelemetry `filestatsreceiver` component. ([@rfratto](https://togithub.com/rfratto)) ##### Enhancements - Update `prometheus.exporter.kafka` with the following functionalities ([@wildum](https://togithub.com/wildum)): - GSSAPI config - enable/disable PA_FX_FAST - set a TLS server name - show the offset/lag for all consumer group or only the connected ones - set the minimum number of topics to monitor - enable/disable auto-creation of requested topics if they don't already exist - regex to exclude topics / groups - added metric kafka_broker_info - In `prometheus.exporter.kafka`, the interpolation table used to compute estimated lag metrics is now pruned on `metadata_refresh_interval` instead of `prune_interval_seconds`. ([@wildum](https://togithub.com/wildum)) - Don't restart tailers in `loki.source.kubernetes` component by above-average time deltas if K8s version is >= 1.29.1 ([@hainenber](https://togithub.com/hainenber)) - In `mimir.rules.kubernetes`, add support for running in a cluster of Alloy instances by electing a single instance as the leader for the `mimir.rules.kubernetes` component to avoid conflicts when making calls to the Mimir API. ([@56quarters](https://togithub.com/56quarters)) ##### Bugfixes - Fixed issue with defaults for Beyla component not being applied correctly. (marctc) - Fix an issue on Windows where uninstalling Alloy did not remove it from the Add/Remove programs list. ([@rfratto](https://togithub.com/rfratto)) - Fixed issue where text labels displayed outside of component node's boundary. ([@hainenber](https://togithub.com/hainenber)) - Fix a bug where a topic was claimed by the wrong consumer type in `otelcol.receiver.kafka`. ([@wildum](https://togithub.com/wildum)) - Fix an issue where nested import.git config blocks could conflict if they had the same labels. ([@wildum](https://togithub.com/wildum)) - In `mimir.rules.kubernetes`, fix an issue where unrecoverable errors from the Mimir API were retried. ([@56quarters](https://togithub.com/56quarters)) - Fix an issue where `faro.receiver`'s `extra_log_labels` with empty value don't map existing value in log line. ([@hainenber](https://togithub.com/hainenber)) - Fix an issue where `prometheus.remote_write` only queued data for sending every 15 seconds instead of as soon as data was written to the WAL. ([@rfratto](https://togithub.com/rfratto)) - Imported code using `slog` logging will now not panic and replay correctly when logged before the logging config block is initialized. ([@mattdurham](https://togithub.com/mattdurham)) - Fix a bug where custom components would not shadow the stdlib. If you have a module whose name conflicts with an stdlib function and if you use this exact function in your config, then you will need to rename your module. ([@wildum](https://togithub.com/wildum)) - Fix an issue where `loki.source.docker` stops collecting logs after a container restart. ([@wildum](https://togithub.com/wildum)) - Upgrading `pyroscope/ebpf` from 0.4.6 to 0.4.7 ([@korniltsev](https://togithub.com/korniltsev)): - detect libc version properly when libc file name is libc-2.31.so and not libc.so.6 - treat elf files with short build id (8 bytes) properly ##### Other changes - Update `alloy-mixin` to use more specific alert group names (for example, `alloy_clustering` instead of `clustering`) to avoid collision with installs of `agent-flow-mixin`. ([@rfratto](https://togithub.com/rfratto)) - Upgrade Beyla from v1.4.1 to v1.5.1. ([@marctc](https://togithub.com/marctc)) - Add a description to Alloy DEB and RPM packages. ([@rfratto](https://togithub.com/rfratto)) - Allow `pyroscope.scrape` to scrape `alloy.internal:12345`. ([@hainenber](https://togithub.com/hainenber)) - The latest Windows Docker image is now pushed as `nanoserver-1809` instead of `latest-nanoserver-1809`. The old tag will no longer be updated, and will be removed in a future release. ([@rfratto](https://togithub.com/rfratto)) - The log level of `finished node evaluation` log lines has been decreased to 'debug'. ([@tpaschalis](https://togithub.com/tpaschalis)) - Update post-installation scripts for DEB/RPM packages to ensure `/var/lib/alloy` exists before configuring its permissions and ownership. ([@rfratto](https://togithub.com/rfratto)) - Remove setcap for `cap_net_bind_service` to allow alloy to run in restricted environments. Modern container runtimes allow binding to unprivileged ports as non-root. ([@BlackDex](https://togithub.com/BlackDex)) - Upgrading from OpenTelemetry v0.96.0 to v0.99.0. - `otelcol.processor.batch`: Prevent starting unnecessary goroutines. [https://github.com/open-telemetry/opentelemetry-collector/issues/9739](https://togithub.com/open-telemetry/opentelemetry-collector/issues/9739)ues/9739 - `otelcol.exporter.otlp`: Checks for port in the config validation for the otlpexporter. [https://github.com/open-telemetry/opentelemetry-collector/issues/9505](https://togithub.com/open-telemetry/opentelemetry-collector/issues/9505)ues/9505 - `otelcol.receiver.otlp`: Fix bug where the otlp receiver did not properly respond with a retryable error code when possible fo[https://github.com/open-telemetry/opentelemetry-collector/pull/9357](https://togithub.com/open-telemetry/opentelemetry-collector/pull/9357)lector/pull/9357 - `otelcol.receiver.vcenter`: Fixed the resource attribute model to more accurately support multi-cluster deployments. [https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/30879](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/30879)es/30879 For more information on impacts p[https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/31113](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/pull/31113)ector-contrib/pull/31113 The main impact is that `vcenter.resource_pool.name`, `vcenter.resource_pool.inventory_path`, and `vcenter.cluster.name` are reported with more accuracy on VM metrics. - `otelcol.receiver.vcenter`: Remove the `vcenter.cluster.name` resource attribute from Host resources if the Host is standalone (no cluster). [https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/32548](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32548)es/32548 - `otelcol.receiver.vcenter`: Changes process for collecting VMs & VM perf metrics to be more efficient (one call now for all VMs). [https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/31837](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31837)es/31837 - `otelcol.connector.servicegraph`: Added a new `database_name_attribute` config argument to allow users to specify a custom attribute name for identifying the database name in span attr[https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/30726](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/pull/30726)ntrib/pull/30726 - `otelcol.connector.servicegraph`: Fix 'failed to find dimensions for key' error from race condition in metrics cleanup. [https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/31701](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31701)es/31701 - `otelcol.connector.spanmetrics`: Add `metrics_expiration` option to enable expiration of metrics if spans are not received within a certain time frame. By default, the expiration is disabled (set[https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/30559](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/30559)rib/issues/30559 - `otelcol.connector.spanmetrics`: Change default value of `metrics_flush_interval` from 15s to 60s. [https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/31776](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31776)es/31776 - `otelcol.connector.spanmetrics`: Discard counter span metric exemplars after each flush interval to avoid unbounded memory growth. This aligns exemplar discarding for counter span metrics with the existing logic for histogram span m[https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/31683](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31683)rib/issues/31683 - `otelcol.exporter.loadbalancing`: Fix panic when a sub-exporter is shut down while still handling requests. [https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/31410](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31410)es/31410 - `otelcol.exporter.loadbalancing`: Fix memory leaks on shutdown. [https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/31050](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/pull/31050)ll/31050 - `otelcol.exporter.loadbalancing`: Support the timeout period of k8s resolver list watch can be configured. [https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/31757](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31757)es/31757 - `otelcol.processor.transform`: Change metric unit for metrics extracted with `extract_count_metric()` to be the default unit (`1`). [https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/31575](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31575)es/31575 - `otelcol.receiver.opencensus`: Refactor the receiver to pass lifecycle tests and avoid leaking gRPC connections. [https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/31643](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31643)es/31643 - `otelcol.extension.jaeger_remote_sampling`: Fix leaking goroutine on shutdown. [https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/31157](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31157)es/31157 - `otelcol.receiver.kafka`: Fix panic on shutdown. [https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/31926](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31926)es/31926 - `otelcol.processor.resourcedetection`: Only attempt to detect Kubernetes node resource attributes when they're enabled. [https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/31941](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31941)es/31941 - `otelcol.processor.resourcedetection`: Fix memory leak on AKS. [https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/32574](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/pull/32574)ll/32574 - `otelcol.processor.resourcedetection`: Update to ec2 scraper so that core attributes are not dropped if describeTags returns an error (likely due to permissions). [https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/30672](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/pull/30672)ll/30672 - Use Go 1.22.3 for builds. ([@kminehart](https://togithub.com/kminehart))Configuration
📅 Schedule: 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 becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.