-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): update all dependencies #76
Conversation
7c2f7eb
to
4417064
Compare
61e2514
to
a18fb2b
Compare
0a8f29a
to
1cd9607
Compare
115cadc
to
33de24d
Compare
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
2eddaa5
to
7187fe1
Compare
a97a28e
to
2e671a4
Compare
db09013
to
99d03b1
Compare
99d03b1
to
2014313
Compare
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
Signed-off-by: Bence Csati <bence.csati@axoflow.com>
084f1b6
to
264e2ef
Compare
Signed-off-by: Bence Csati <bence.csati@axoflow.com>
Signed-off-by: Bence Csati <bence.csati@axoflow.com>
Signed-off-by: Bence Csati <bence.csati@axoflow.com>
264e2ef
to
5dc61dc
Compare
Signed-off-by: Bence Csati <bence.csati@axoflow.com>
This PR contains the following updates:
0.28.0
->0.29.0
v5
->v6
v2.2.0
->v3.3.0
v3.1.0
->v3.3.0
v0.34.0
->v0.37.0
v2.17.3
->v2.22.0
v1.33.1
->v1.36.0
v0.103.0
->v0.114.0
v0.2.0
->v0.4.0
v0.12.0
->v0.13.0
v1.9.0
->v1.10.0
v2.22.8
->v3.27.5
v3.25.5
->v3.27.5
1.22.3
->1.23.3
v0.113.0
->v0.114.0
v0.113.0
->v0.114.0
v1.19.0
->v1.20.0
v1.19.0
->v1.20.0
v0.113.0
->v0.114.0
v0.113.0
->v0.114.0
v0.113.0
->v0.114.0
v0.113.0
->v0.114.0
1.22
->1.23
9bf2ced
->2d47ceb
v0.30.2
->v0.31.3
v0.30.2
->v0.31.3
v0.30.2
->v0.31.3
0.71.2
->0.74.3
v0.18.4
->v0.19.2
Release Notes
aquasecurity/trivy-action (aquasecurity/trivy-action)
v0.29.0
Compare Source
What's Changed
setup-trivy
by @DmitriyLewen in https://github.com/aquasecurity/trivy-action/pull/421setup-trivy
and add newcontrib
directory path info by @DmitriyLewen in https://github.com/aquasecurity/trivy-action/pull/424New Contributors
Full Changelog: aquasecurity/trivy-action@0.28.0...0.29.0
docker/build-push-action (docker/build-push-action)
v6
Compare Source
docker/login-action (docker/login-action)
v3.3.0
Compare Source
Full Changelog: docker/login-action@v3.2.0...v3.3.0
v3.2.0
Compare Source
Full Changelog: docker/login-action@v3.1.0...v3.2.0
v3.1.0
Compare Source
Full Changelog: docker/login-action@v3.0.0...v3.1.0
v3.0.0
Compare Source
Full Changelog: docker/login-action@v2.2.0...v3.0.0
cisco-open/operator-tools (github.com/cisco-open/operator-tools)
v0.37.0
Compare Source
What's Changed
New Contributors
Full Changelog: cisco-open/operator-tools@v0.36.0...v0.37.0
v0.36.0
Compare Source
What's Changed
New Contributors
Full Changelog: cisco-open/operator-tools@v0.35.0...v0.36.0
v0.35.0
Compare Source
What's Changed
New Contributors
Full Changelog: cisco-open/operator-tools@v0.34.0...v0.35.0
onsi/ginkgo (github.com/onsi/ginkgo/v2)
v2.22.0
Compare Source
2.22.0
Features
0fcaa08
]This allows serial tests to be filtered using the
label-filter
Maintenance
Various doc fixes
v2.21.0
Compare Source
2.21.0
Features
a69eb39
]bcab9c8
]Fixes
e548367
]SpecsThatWillBeRun
withSpecsThatWillRun
[
c2c4d3c
]Maintenance
7e65a00
]v2.20.2
Compare Source
2.20.2
Require Go 1.22+
Maintenance
a671816
]v2.20.1
Compare Source
2.20.1
Fixes
d6f9640
]v2.20.0
Compare Source
2.20.0
Features
be5ab95
]Maintenance
d303d14
]7a50221
]v2.19.1
Compare Source
2.19.1
Fixes
63c8c30
]ff41e27
]Maintenance
76f4e0c
]b69c00d
]f097741
]v2.19.0
Compare Source
2.19.0
Features
Label Sets allow for more expressive and flexible label filtering.
v2.18.0
Compare Source
2.18.0
Features
f010b65
]d80eebe
]Fixes
42013d6
]Maintenance
fcf1fd7
]8bb14fd
]04bfad7
]onsi/gomega (github.com/onsi/gomega)
v1.36.0
Compare Source
1.36.0
Features
4c964c6
]Maintenance
ece6872
]8e924d7
]v1.35.1
Compare Source
1.35.1
Fixes
ca36da1
]v1.35.0
Compare Source
1.35.0
Features
EnforceDefaultTimeoutsWhenUsingContexts()
to haveEventually
honor the default timeout when passed a context. (prior to this you had to expclility add a timeout) [e4c4265
]StopTrying(message).Successfully()
to abort aConsistently
early without failure [eeca931
]Fixes
HaveField
to avoid unexpected errors when used with async assertions. [3bdbc4e
]Maintenance
a05a416
]v1.34.2
Compare Source
1.34.2
Require Go 1.22+
Maintenance
c59c6dc
]8158b99
]v1.34.1
Compare Source
1.34.1
Maintenance
5e71dcd
]v1.34.0
Compare Source
1.34.0
Features
c549e0d
]Fixes
878940c
]ebadb67
]Maintenance
8af2ece
]123a071
]0e69083
]2675796
]4160c0f
]892c303
]open-telemetry/opentelemetry-operator (github.com/open-telemetry/opentelemetry-operator)
v0.114.0
Compare Source
0.114.0
💡 Enhancements 💡
collector
: Create RBAC rules for the k8s_cluster receiver automatically. (#3427)collector
: Create RBAC rules for the k8sobjects receiver automatically. (#3429)collector
: Add a warning message when one created collector needs extra RBAC permissions and the service account doesn't have them. (#3432)target allocator
: Added allocation_fallback_strategy option as fallback strategy for per-node allocation strategy, can be enabled with feature flag operator.targetallocator.fallbackstrategy (#3477)If using per-node allocation strategy, targets that are not attached to a node will not
be allocated. As the per-node strategy is required when running as a daemonset, it is
not possible to assign some targets under a daemonset deployment.
Feature flag operator.targetallocator.fallbackstrategy has been added and results in consistent-hashing
being used as the fallback allocation strategy for "per-node" only at this time.
auto-instrumentation
: updated node auto-instrumentation dependencies to the latest version (#3476)operator
: Replace references to gcr.io/kubebuilder/kube-rbac-proxy with quay.io/brancz/kube-rbac-proxy (#3485)🧰 Bug fixes 🧰
operator
: Operator pod crashed if the Service Monitor for the operator metrics was created before by another operator pod. (#3446)Operator fails when the pod is restarted and the Service Monitor for operator metrics was already created by another operator pod.
To fix this, the operator now sets the owner reference on the Service Monitor to itself and checks if the Service Monitor already exists.
auto-instrumentation
: Bump base memory requirements for python and go (#3479)Components
v0.113.1
Compare Source
0.113.1
This release fixes an important bug that caused the operator to crash when prometheus-operator CRDs were present in the cluster. See #3446 for details. This fix is also present in v0.114.0.
🧰 Bug fixes 🧰
operator
: Operator pod crashed if the Service Monitor for the operator metrics was created before by another operator pod. (#3446)Operator fails when the pod is restarted and the Service Monitor for operator metrics was already created by another operator pod.
To fix this, the operator now sets the owner reference on the Service Monitor to itself and checks if the Service Monitor already exists.
Components
v0.113.0
Compare Source
0.113.0
💡 Enhancements 💡
operator
: Programmatically create theServiceMonitor
for the operator metrics endpoint, ensuring correct namespace handling and dynamic configuration. (#3370)Previously, the
ServiceMonitor
was created statically from a manifest file, causing failures when theoperator was deployed in a non-default namespace. This enhancement ensures automatic adjustment of the
serverName
and seamless metrics scraping.collector
: Create RBAC rules for the k8s_events receiver automatically. (#3420)collector
: Inject environment K8S_NODE_NAME environment variable for the Kubelet Stats Receiver. (#2779)auto-instrumentation
: add config for installing musl based auto-instrumentation for Python (#2264)auto-instrumentation
: Supporthttp/json
andhttp/protobuf
via OTEL_EXPORTER_OTLP_PROTOCOL environment variable in addition to defaultgrpc
for exporting traces (#3412)target allocator
: enables support for pulling scrape config and probe CRDs in the target allocator (#1842)🧰 Bug fixes 🧰
collector
: Fix mutation of deployments, statefulsets, and daemonsets allowing to remove fields on update (#2947)Components
v0.112.0
Compare Source
0.112.0
💡 Enhancements 💡
auto-instrumentation
: Support configuring Java auto-instrumentation when runtime configuration is provided from configmap or secret. (#1814)This change allows users to configure JAVA_TOOL_OPTIONS in config map or secret when the name of the variable is defined in the pod spec.
The operator in this case set another JAVA_TOOL_OPTIONS that references the original value
e.g.
JAVA_TOOL_OPTIONS=$(JAVA_TOOL_OPTIONS) -javaagent:/otel-auto-instrumentation-java/javaagent.jar
.auto-instrumentation
: Adds VolumeClaimTemplate field to Instrumentation spec to enable user-definable ephemeral volumes for auto-instrumentation. (#3267)collector
: Add support for persistentVolumeClaimRetentionPolicy field (#3305)auto-instrumentation
: build musl based auto-instrumentation in Python docker image ([#2264](https://redirect.github.com/open-telemetry/opeConfiguration
📅 Schedule: Branch creation - "before 4am" (UTC), 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.