-
Notifications
You must be signed in to change notification settings - Fork 23
Update go module minor/patch updates #245
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
Merged
openshift-merge-bot
merged 1 commit into
main
from
konflux/mintmaker/main/go-module-minorpatch-updates
Aug 10, 2026
+65
−65
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: openshift-hyperfleet/hyperfleet-sentinel
Length of output: 178
🏁 Script executed:
Repository: openshift-hyperfleet/hyperfleet-sentinel
Length of output: 13044
🏁 Script executed:
Repository: openshift-hyperfleet/hyperfleet-api
Length of output: 4009
🏁 Script executed:
Repository: openshift-hyperfleet/hyperfleet-adapter
Length of output: 4518
🏁 Script executed:
Repository: openshift-hyperfleet/hyperfleet-broker
Length of output: 2764
🌐 Web query:
OpenTelemetry Go v1.45.0 release notes log API Kind Value KeyValue constructors conversion helpers WithEndpointURL OTLP endpoint path behavior💡 Result:
In OpenTelemetry Go v1.45.0, several significant updates were introduced regarding log APIs, attribute handling, and OTLP exporter behavior [1]. API Changes for Logs A major breaking change in v1.45.0 mandates the use of go.opentelemetry.io/otel/attribute.Value and go.opentelemetry.io/otel/attribute.KeyValue for log bodies and attributes [1]. This affects the go.opentelemetry.io/otel/log, go.opentelemetry.io/otel/log/logtest, go.opentelemetry.io/otel/sdk/log, and go.opentelemetry.io/otel/sdk/log/logtest packages [1]. To facilitate this, the go.opentelemetry.io/otel/log package provides conversion helpers such as ValueFromAttribute and KeyValueFromAttribute, which allow for the conversion of standard attribute.Value and attribute.KeyValue types into their corresponding log-specific structures [2]. The attribute package includes standard constructors (e.g., Bool, Int64, String, Slice) to create KeyValue pairs [3]. OTLP Endpoint Path Behavior In v1.45.0, a breaking change was introduced for the WithEndpointURL option in the OTLP/HTTP exporters (e.g., otlpmetrichttp, otlptracehttp) [1][4]. When WithEndpointURL is used with a URL that lacks a path component, the exporter no longer automatically appends the default signal path (such as /v1/traces or /v1/metrics) [5][4]. Instead, it now normalizes such URLs to the root path ("/") [4]. This change ensures consistency across OTLP signals and compliance with the OpenTelemetry specification, which requires that OTLP/HTTP endpoint URLs be used as-is, with the exception that pathless URLs must default to the root path [4].
Citations:
🏁 Script executed:
Repository: openshift-hyperfleet/hyperfleet-sentinel
Length of output: 2673
🏁 Script executed:
Repository: openshift-hyperfleet/hyperfleet-api
Length of output: 15278
🏁 Script executed:
Repository: openshift-hyperfleet/hyperfleet-adapter
Length of output: 3711
🏁 Script executed:
Repository: openshift-hyperfleet/hyperfleet-broker
Length of output: 723
🏁 Script executed:
Repository: openshift-hyperfleet/hyperfleet-sentinel
Length of output: 35753
🏁 Script executed:
Repository: openshift-hyperfleet/hyperfleet-api
Length of output: 17729
🏁 Script executed:
Repository: openshift-hyperfleet/hyperfleet-adapter
Length of output: 16696
🏁 Script executed (no clone):
Length of output: 785
🏁 Script executed:
Repository: openshift-hyperfleet/hyperfleet-sentinel
Length of output: 26817
🏁 Script executed (no clone):
Length of output: 825
🌐 Web query:
OpenTelemetry Go v1.45.0 OTEL_EXPORTER_OTLP_ENDPOINT no path /v1/traces environment variable behavior💡 Result:
In OpenTelemetry Go v1.45.0, a breaking change was introduced regarding how OTLP HTTP exporters handle paths in endpoint URLs [1]. 1. Previous Behavior: Historically, if an endpoint URL was configured without a path, the exporter would automatically append the default signal path (e.g., /v1/traces for traces) [1]. 2. v1.45.0 Behavior: The exporter no longer automatically appends the default signal path if the configured endpoint URL lacks a path [1]. Instead, if no path is provided in the URL, the exporter will use the root path (/) [1]. 3. Impact on Configuration: - If you set OTEL_EXPORTER_OTLP_ENDPOINT (the base variable) without a specific path, the exporter will attempt to send signals to the root path (/) of the target host [1]. - To maintain the previous behavior (sending traces to /v1/traces), you must explicitly include the path in your configuration [1]. 4. Recommended Adjustments: - When using code-based configuration (e.g., WithEndpointURL), you should use path-aware construction, such as: WithEndpointURL(url.JoinPath(endpoint, "/v1/traces")) [1]. - When using environment variables, ensure the provided URL explicitly includes the required path if the target server expects it, such as setting OTEL_EXPORTER_OTLP_TRACES_ENDPOINT=https://example.com:4318/v1/traces [1][2]. This change aligns the behavior of the trace and metric exporters with the logs exporter and ensures consistency across different configuration methods (environment variables vs. programmatic options) [1].
Citations:
Make the OTLP/HTTP trace endpoint path explicit.
OpenTelemetry v1.45.0 sends a pathless OTLP/HTTP endpoint to
/, not/v1/traces. Require/v1/tracesforhttp/protobufconfiguration and add a request-level test.🤖 Prompt for AI Agents
Sources: Path instructions, MCP tools